detecting-sandbox-evasion-behavior
Detects sandbox and analysis evasion techniques in a sample by scanning static
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/detecting-sandbox-evasion-behaviorWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package939b08d4…055de280
939b08d48474…c55f055de2804 files · 3.0 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/detecting-sandbox-evasion-behavior@da7600a
On this page
When to Use
- A sample ran inertly in a sandbox and you suspect evasion.
- You want to enumerate anti-VM, anti-debug, timing, and environment-fingerprinting checks from static strings/imports and/or an API trace.
Do not use this to conclude a sample is benign — evasion is itself a malicious signal, and absence of detected checks does not prove there are none.
Prerequisites
- The sample (read inertly) and optionally a JSON API trace.
Safety & Handling
- Read bytes statically; never execute the sample to "see if it evades."
Workflow
Step 1: Scan for evasion indicators
python scripts/analyst.py scan sample.binSearches for VM/sandbox artifact strings (VMware, VBOX, vmtoolsd, sbiedll, common
sandbox usernames/hostnames), anti-debug APIs (IsDebuggerPresent, CheckRemoteDebuggerPresent,
NtQueryInformationProcess), timing stalls (Sleep, GetTickCount, rdtsc), and CPUID checks.
Step 2: Categorize techniques
Group hits into anti-VM, anti-debug, anti-sandbox, and timing/stalling categories.
Step 3: Recommend bypass and report
Suggest analysis adjustments (patch sleeps, hardened VM, hooking) and map findings to ATT&CK.
Validation
- Detected indicators are grouped by evasion category.
- Findings distinguish static-string evidence from API-trace evidence when both are provided.
- Each category maps to an ATT&CK technique/subtechnique.
Pitfalls
- False positives from benign software that also queries the environment — corroborate.
- Strings can be obfuscated; absence of plaintext artifacts is not absence of evasion.
- Confusing a hung sample with deliberate stalling without timing evidence.
References
- See
references/api-reference.mdfor the scanner. - ATT&CK T1497 and T1622 (linked in frontmatter).
Files in this version
references/11.3 KB
- api-reference.md1.3 KB
scripts/12.3 KB
- analyst.py2.3 KB
- LICENSE340 B
- SKILL.md2.7 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 939b08d4 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login