analyzing-malware-sandbox-evasion-techniques

analyzing-malware-sandbox-evasion-techniques is a skill for Claude Code from plurigrid/asi. It costs 46 tokens per session (501 once invoked), scanned A, a copy of analyzing-malware-sandbox-evasion-techniques, MIT.

A guide to spotting sandbox evasion in malware reports from Cuckoo or AnyRun. Sandbox evasion means malware detects that it is being tested and changes or hides its behaviour.

In plain words
What is it for?
Use it to inspect behavioural reports for timing checks, virtual-machine fingerprints, user-interaction checks, environment tests, and inflated sleep patterns.
Why use it?
Malware may avoid showing its real actions when it detects virtual machines, unusual hardware, missing user activity, or extended sleep periods. Finding these signs prevents false conclusions from incomplete reports.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the asi plugin — 56 skills shipped together

Good fit Use it to inspect behavioural reports for timing checks, virtual-machine fingerprints, user-interaction checks, environment tests, and inflated sleep patterns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/plurigrid/asi/analyzing-malware-sandbox-evasion-techniques
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add plurigrid/asi --skill analyzing-malware-sandbox-evasion-techniques
Clone the repo
git clone --depth 1 https://github.com/plurigrid/asi

Made for: Claude Code.

Or install asi, the plugin that ships this one along with the rest of its 56 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analyzing-malware-sandbox-evasion-techniques

README.md
[![agentmods](https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-malware-sandbox-evasion-techniques/github.svg)](https://agentmods.dev/skills/plurigrid/asi/analyzing-malware-sandbox-evasion-techniques)
Your own site
<a href="https://agentmods.dev/skills/plurigrid/asi/analyzing-malware-sandbox-evasion-techniques"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-malware-sandbox-evasion-techniques/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for analyzing-malware-sandbox-evasion-techniques

Your own site · 80×15
<a href="https://agentmods.dev/skills/plurigrid/asi/analyzing-malware-sandbox-evasion-techniques"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-malware-sandbox-evasion-techniques.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 501 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00501
Opus 5 $0.00023 $0.00251
Sonnet 5 $0.00009 $0.00100
Haiku 4.5 $0.00005 $0.00050

Measured 7d ago against content hash 868477426f57, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

analyzing-malware-sandbox-evasion-techniques scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

88% identical to analyzing-malware-sandbox-evasion-techniques — 38 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/asi/skills/analyzing-malware-sandbox-evasion-techniques/SKILL.md · 52 lines

What it actually says

Analyzing Malware Sandbox Evasion Techniques

Overview

Sandbox evasion (MITRE ATT&CK T1497) allows malware to detect analysis environments and alter behavior to avoid detection. This skill analyzes behavioral reports from Cuckoo Sandbox and AnyRun for evasion indicators including timing-based checks (GetTickCount, QueryPerformanceCounter, sleep inflation), VM artifact detection (registry keys, MAC address prefixes, process names like vmtoolsd.exe), user interaction checks (mouse movement, keyboard input), and environment fingerprinting (disk size, CPU count, RAM). Detection rules flag samples exhibiting these behaviors for deeper manual analysis.

When to Use

  • When investigating security incidents that require analyzing malware sandbox evasion techniques
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Cuckoo Sandbox 2.0+ or AnyRun account for behavioral analysis reports
  • Python 3.8+ with json library for report parsing
  • Behavioral report exports in JSON format

Steps

  1. Parse Cuckoo/AnyRun behavioral report JSON files
  2. Extract API call sequences for timing-related functions
  3. Identify VM artifact detection via registry queries and WMI calls
  4. Detect sleep inflation by comparing requested vs actual sleep durations
  5. Flag user interaction checks (GetCursorPos, GetAsyncKeyState patterns)
  6. Score evasion sophistication based on technique count and diversity
  7. Map detected techniques to MITRE ATT&CK T1497 sub-techniques

Expected Output

JSON report listing detected evasion techniques with MITRE ATT&CK mapping, API call evidence, evasion sophistication score, and classification of evasion categories (timing, VM detection, user interaction, environment fingerprinting).

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 52 lines · 46 tokens per session scan A 868477426f57

Subscribe to this mod's changes

analyzing-malware-sandbox-evasion-techniques is a skill published in the GitHub repository plurigrid/asi (62 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 501 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to analyzing-malware-sandbox-evasion-techniques, differing in 38 lines, and is treated as a copy.

Related

Other skills, from other repositories

analyzing-malware-sandbox-evasion-techniques

Detect sandbox and VM evasion techniques in malware samples by analyzing timing checks, VM/hypervisor artifact queries, user-interaction checks, and sleep-inflation patterns from Cuckoo or AnyRun behavioral reports. Use when a sample shows no or minimal activity in a sandbox, when a behavioral report needs review for…

mukul975/Anthropic-Cybersecurity-Skills · 89 tokens

analyzing-malware-sandbox-evasion-techniques

A malware-analysis procedure for finding signs that a malicious program is trying to detect or avoid a security sandbox. A sandbox is an isolated environment used to run suspicious files safely; Cuckoo Sandbox and AnyRun produce reports about what those files do.

killvxk/cybersecurity-skills-zh · 60 tokens

analyzing-malware-sandbox-evasion-techniques

Detect sandbox evasion techniques in malware samples by analyzing timing checks, VM artifact queries, user interaction detection, and sleep inflation patterns from Cuckoo/AnyRun behavioral reports.

26zl/cybersec-toolkit · 46 tokens

analyzing-malware-sandbox-evasion-techniques

Detect sandbox evasion techniques in malware samples by analyzing timing checks, VM artifact queries, user interaction detection, and sleep inflation patterns from Cuckoo/AnyRun behavioral reports.

autohandai/community-skills · 46 tokens

analyzing-malware-sandbox-evasion-techniques

Detect sandbox evasion techniques in malware samples by analyzing timing checks, VM artifact queries, user interaction detection, and sleep inflation patterns from Cuckoo/AnyRun behavioral reports.

pinkpixel-dev/skills-collection-1 · 46 tokens

analyzing-malware-sandbox-evasion-techniques

Detect sandbox evasion techniques in malware samples by analyzing timing checks, VM artifact queries, user interaction detection, and sleep inflation patterns from Cuckoo/AnyRun behavioral reports.

marysatasselshaped667/skills-collection-1 · 46 tokens