Skip to content
Development
Skill

/perform-dynamic-malware-analysis

Observe suspicious content in a disposable environment. Use when execution, process ancestry, file changes, persistence, network behavior, payloads, or user interaction need measurement after static analysis with isolation and teardown.

From plugin
socket
7200 skills5 MCP
Install
$ npx -y skills add gaelic-ghost/socket --skill perform-dynamic-malware-analysis --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/perform-dynamic-malware-analysis

Context preview

The summary Claude sees to decide when to auto-load this skill.

Observe suspicious content in a disposable environment. Use when execution, process ancestry, file changes, persistence, network behavior, payloads, or user interaction need measurement after static analysis with isolation and teardown.

SKILL.md

perform-dynamic-malware-analysis.SKILL.md
name: perform-dynamic-malware-analysis
description: Observe suspicious content in a disposable environment. Use when execution, process ancestry, file changes, persistence, network behavior, payloads, or user interaction need measurement after static analysis with isolation and teardown.

Perform Dynamic Malware Analysis

Overview

Execute only inside an environment chosen by `select-analysis-isolation` and preflighted by `prepare-isolated-analysis-lab`, with an observation plan that can distinguish artifact behavior from baseline noise. Preserve the exact sample, prepared-lab record, and environment identity.

Read [references/dynamic-observation-plan.md](references/dynamic-observation-plan.md) for baseline, stimulus, telemetry, and teardown fields.

Workflow

1. Define the unresolved question and minimum stimulus. 2. Verify isolation.

  • Require the prepared-lab record and verify its guest/platform build, baseline/reset state, accounts, shares, clipboard, devices, credentials, network mode, monitoring, stop controls, export path, and teardown plan are still current.
  • Record virtualization artifacts or anti-VM behavior that may affect the conclusion.

3. Capture a baseline.

  • Record processes, files/registrations, persistence surfaces, network state, services, and relevant logs before execution.

4. Execute one controlled step.

  • Record command/UI action, time, user/privilege, environment variables, arguments, and interactions.
  • Do not improvise additional payloads, credentials, or targets.

5. Observe behavior.

  • Correlate process tree, file/registry or platform state, persistence, permissions, child artifacts, network/DNS, logs, prompts, crashes, and timing.
  • Hash and preserve dropped/modified artifacts as new evidence.

6. Repeat only to answer a named question.

  • Change one variable at a time and revert to the baseline snapshot.

7. Export and tear down.

  • Export only intended evidence, scan it before host use, destroy/revert the environment, and revoke temporary access.

Output

Return the prepared-lab identity, environment/baseline identity, stimulus, observed timeline, artifacts and indicators, absent expected behavior, virtualization/evasion/coverage limits, conclusion, and teardown verification.

Read more
Ships withsocket

Stuff for Agents on macOS Promo audio: Socket Codex Marketplace Promo

Get the whole plugin

Other skills on socket.