Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/detecting-sandbox-evasion-behaviorMalware and ransomware analysis

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-behavior

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
q911DhFuKj…qXPmxzDg==The CLI checks the SHA-256 and the signature before it writes a file.
Package939b08d4…055de280
939b08d48474…c55f055de2804 files · ⁦3.0 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/detecting-sandbox-evasion-behavior@da7600a

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

bash
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.md for the scanner.
  • ATT&CK T1497 and T1622 (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a939b08d4Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login