-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Anti-Sandbox Check - Known hostnames / usernames #189
Comments
It’s a bit interesting, I need to study it. |
Usernames checked for by Betabot, from [3] (not including ones mentioned above):
[3] https://www.cybereason.com/blog/betabot-banking-trojan-neurevt |
Usernames checked for by Satan, from [4] (not including ones mentioned above):
Hostnames checked for by Shifu, from [5] (not including ones mentioned above):
Combined checks by Emotet, from [6]:
[4] https://cofense.com/satan/ |
Fix #189 - Add known hostname / username checks from malware
Some malware will stop executing if it's running on a machine with certain host names and user names, presumably as an anti-sandbox check. It'd be awesome if al-khaser could have a check for these.
Usernames checked for by Gootkit, from [1]:
Hostnames checked for by Gootkit, from [1]:
Usernames checked for by a Trickbot downloader, from [2]:
Hostnames checked for by a Trickbot downloader, from [2]:
More research will need to be done to know which sandboxes these usernames and hostnames correspond to. For the ones that we can't definitively tie back to a known sandbox, should these be included in al-khaser? It's possible those could be the username/hostname of the malware author's test environment, for instance, and isn't technically an anti-sandbox check.
[1] https://www.sentinelone.com/blog/gootkit-banking-trojan-deep-dive-anti-analysis-features/
[2] https://www.bromium.com/deobfuscating-ostap-trickbots-javascript-downloader/
The text was updated successfully, but these errors were encountered: