meltedinhex/analyst-ai-pack / skills/detecting-sandbox-evasion-behavior
detecting-sandbox-evasion-behavior
VerifiedDetects sandbox and analysis evasion techniques in a sample by scanning static strings, imports, and API traces for VM artifact checks, timing/sleep stalls, anti-debug calls, and environment fingerprinting. Activates for requests to detect sandbox evasion, find anti-VM or anti-debug checks, or explain why a sample did not detonate.
Detecting Sandbox Evasion Behavior
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.bin
Searches 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).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |