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/bypassing-anti-vm-and-sandbox-checksMalware and ransomware analysis

bypassing-anti-vm-and-sandbox-checks

⁨Bypasses anti-VM and sandbox checks during analysis by locating the specific detection⁩

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/bypassing-anti-vm-and-sandbox-checks

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

SignatureSigned, ed25519
VjW+Ma3otM…W7E2qkDQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packagef340e5e4…41a90627
f340e5e4417a…559a41a906274 files · ⁦3.1 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/bypassing-anti-vm-and-sandbox-checks@da7600a

When to Use

  • An evasive sample refuses to detonate under analysis and you need to locate and neutralize its anti-VM/sandbox checks (artifact strings, timing stalls, CPUID hypervisor bit, MAC/registry checks).
  • You are planning patches or environment hardening to force execution.

Do not use patching as a shortcut that changes malicious logic — patch only the evasion gate. Run only in an isolated, instrumented VM with snapshots.

Prerequisites

  • The sample and a debugger/disassembler on an isolated VM.

Safety & Handling

  • The sample executes during bypass work; use a disposable, snapshotted, network-controlled VM.

Workflow

Step 1: Locate the evasion checks

bash
python scripts/analyst.py locate sample.bin

Reports offsets of anti-VM artifact strings, timing APIs (GetTickCount, rdtsc), CPUID usage, and environment-fingerprint APIs to point you at the detection routines.

Step 2: Plan the bypass

For each check decide the approach: patch the conditional jump after the check, hook/stub the API to return benign values, or harden the VM (rename adapters, patch registry, add fake processes).

Step 3: Apply and verify

Patch the gate (e.g., force the "not detected" branch) and confirm the sample proceeds past the check.

Step 4: Document

Record each check, its offset, and the bypass applied for reproducibility.

Validation

  • Each located check maps to a real detection primitive (string/timing/CPUID/API).
  • The patched/hooked gate provably lets execution continue.
  • Only the evasion gate is altered, not the payload logic.

Pitfalls

  • Multiple layered checks — bypassing one is not enough.
  • Timing checks needing instruction-accurate handling (rdtsc deltas).
  • Anti-tamper detecting the patch; prefer hooking returns over byte patches when fragile.

References

  • See references/api-reference.md for the locator.
  • ATT&CK T1497 and the CPUID hypervisor bit reference (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, 2026da7600af340e5e4Signed–

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