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.
npx skills add Mikaru0Mystic/sectinel --skill analyzing-malware-sandbox-evasion-techniquesgit clone --depth 1 https://github.com/Mikaru0Mystic/sectinelWrote 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.
[](https://agentmods.dev/skills/mikaru0mystic/sectinel/analyzing-malware-sandbox-evasion-techniques)<a href="https://agentmods.dev/skills/mikaru0mystic/sectinel/analyzing-malware-sandbox-evasion-techniques"><img src="https://agentmods.dev/badge/skills/mikaru0mystic/sectinel/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.
<a href="https://agentmods.dev/skills/mikaru0mystic/sectinel/analyzing-malware-sandbox-evasion-techniques"><img src="https://agentmods.dev/badge/skills/mikaru0mystic/sectinel/analyzing-malware-sandbox-evasion-techniques.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00046 | $0.00558 |
| Opus 5 | $0.00023 | $0.00279 |
| Sonnet 5 | $0.00009 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
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 11d 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.
This is a copy
83% identical to analyzing-malware-sandbox-evasion-techniques — 12 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.
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
- Parse Cuckoo/AnyRun behavioral report JSON files
- Extract API call sequences for timing-related functions
- Identify VM artifact detection via registry queries and WMI calls
- Detect sleep inflation by comparing requested vs actual sleep durations
- Flag user interaction checks (GetCursorPos, GetAsyncKeyState patterns)
- Score evasion sophistication based on technique count and diversity
- 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).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 64 lines · 46 tokens per session scan A 5f7eb5351183
analyzing-malware-sandbox-evasion-techniques is a skill published in the GitHub repository Mikaru0Mystic/sectinel (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 558 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to analyzing-malware-sandbox-evasion-techniques, differing in 12 lines, and is treated as a copy.
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…
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.
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.
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.
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.
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.