Skip to content

meltedinhex/analyst-ai-pack / skills/bypassing-anti-vm-and-sandbox-checks

bypassing-anti-vm-and-sandbox-checks

Verified

Bypasses anti-VM and sandbox checks during analysis by locating the specific detection routines (artifact strings, timing, CPUID/hypervisor bit) and planning patches or environment hardening so the sample detonates. Activates for requests to bypass anti-VM checks, defeat sandbox detection, or make an evasive sample run for analysis.

Bypassing Anti-VM and Sandbox Checks

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

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

planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall