search

manoj-g-nair / droidbox

Automatically exported from code.google.com/p/droidbox
0 stars 0 forks source link

Installs malware on connected physical devices #65

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
So, I infected my personal android phone yesterday... Fun.

What steps will reproduce the problem?
1. put an Android in developer mode
2. authorize the workstation to install to it
3. charge it from your workstation's USB
4. launch droidbox with a malicious APK
5. see your personal phone get infected

What is the expected output? What do you see instead?
I'd expect some sort of double check to make sure installing to a hardware 
phone is something you want to do... Or at least a warning in the readme.

What version of the product are you using? On what operating system?
OSX mavericks, droidbox 4.1.1

Please provide any additional information below.

Dear god, please at least add a warning.

Original issue reported on code.google.com by JohanNes...@gmail.com on 17 Mar 2015 at 4:54

GoogleCodeExporter commented 9 years ago 
Hey there,

Actually what happens is if you launch/attach two or more emulator/device, by 
default(if device id is not specified with '-s' option, which is the case here) 
adb will run the scripts in the first emulator/device to be recognized by the 
system.

Original comment by shiris...@gmail.com on 2 Apr 2015 at 9:44