Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic Dynamic Analysis #15

Open
jpcarneiro opened this issue Jun 9, 2017 · 1 comment
Open

Automatic Dynamic Analysis #15

jpcarneiro opened this issue Jun 9, 2017 · 1 comment

Comments

@jpcarneiro
Copy link

Hi all,
I want to perform automatic android dynamic malware analysis
I prepared a setup with droidbox where continuously an emulator is launched and an apk installed and run for 50s.

SETUP
Do you have similar setups?
How long do you perform analysis, is 50s enough, any data on optimal run time?

PATTERNS
Do you have yara-rules/patterns to identify malware activity or what is your strategy?
What is your approach to finding new rules? Manually, ML, other? What features are you looking at?

EMULATOR
I have multiple apks that fail to run or the emulator restarts, any ideas?
Following the instructions, I am using arm, Nexus4 android jelly, any problem in using a different AVD?

Sorry for such a big list of questions and thanks in advance.
Chrs,
Joao

@eclipse95
Copy link

Hi @jpcarneiro,
I will try to give you some hints.

  • Concerning the time of analysis, it's depending of your tested app.
  • Droidbox wasn't made for malware analysis. Don't expect find yara-rules or others. Others tools can do it (Cuckoodroid for example).
  • The instrumentation is made by monkeyrunner (Android SDK). I don't if it follows a specific scheme.
  • Each Android API have a specific "mapping". That why you can try to use another Android 4+ but the result may be incorrect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants