Back to catalog
Static reviewDevelopment

Skill dossier

conducting-memory-forensics-with-volatility

Source declaration

Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests involving memory forensics, RAM analysis, Volatility framework, memory dump investigation, volatile evidence analysis, or live memory acquisition.

The author's original description, preserved in English. It describes intent, not verified performance.

Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests involving memory forensics, RAM analysis, Volatility framework, memory dump investigation, volatile evidence analysis, or live memory acquisition.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests involving memory forensics, RAM analysis, Volatility framework, memory dump investigation, volatile evidence analysis, or live memory acquisition. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L56]
  • Step 1: Acquire Memory Image [Source statement; provisional, not tested. Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L58]
  • Step 2: Identify the Operating System and Profile [Source statement; provisional, not tested. Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L98]
  • Step 3: Analyze Running Processes [Source statement; provisional, not tested. Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L113]
  • Step 4: Investigate Network Connections [Source statement; provisional, not tested. Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L138]
  • Step 5: Detect Process Injection and Malware [Source statement; provisional, not tested. Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L156]
  • Step 6: Extract Credentials and Artifacts [Source statement; provisional, not tested. Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L179]
  • Step 7: Generate Forensic Report [Source statement; provisional, not tested. Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L201]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L1-L33]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
30.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/conducting-memory-forensics-with-volatility/LICENSEOther11 KB
skills/conducting-memory-forensics-with-volatility/references/api-reference.mdReference2.3 KB
skills/conducting-memory-forensics-with-volatility/scripts/agent.pyScript6.6 KB
skills/conducting-memory-forensics-with-volatility/SKILL.mdInstruction10.4 KB

SKILL.md frontmatter

{
  "name": "conducting-memory-forensics-with-volatility",
  "description": "Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests involving memory forensics, RAM analysis, Volatility framework, memory dump investigation, volatile evidence analysis, or live memory acquisition.\n",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "memory-forensics",
    "volatility",
    "RAM-analysis",
    "process-injection",
    "DFIR"
  ],
  "mitre_attack": [
    "T1055",
    "T1003.001",
    "T1014",
    "T1059.001",
    "T1620"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Acquire Memory Image

    Source-described action candidate under “Step 1: Acquire Memory Image”; not verified execution.

  4. 04
    Action

    Step 2: Identify the Operating System and Profile

    Source-described action candidate under “Step 2: Identify the Operating System and Profile”; not verified execution.

  5. 05
    Action

    Step 3: Analyze Running Processes

    Source-described action candidate under “Step 3: Analyze Running Processes”; not verified execution.

  6. 06
    Action

    `svchost.exe` running without `-k` parameter or with wrong parent (should be `services.exe`)

    Source-described action candidate under “Step 3: Analyze Running Processes”; not verified execution.

Inspect all extracted workflow candidates (35 candidate steps)
  1. 07
    Action

    `csrss.exe` or `lsass.exe` with abnormal parent process

    Source-described action candidate under “Step 3: Analyze Running Processes”; not verified execution.

  2. 08
    Action

    Processes with misspelled names (`scvhost.exe`, `lssas.exe`)

    Source-described action candidate under “Step 3: Analyze Running Processes”; not verified execution.

  3. 09
    Action

    Unusual processes spawned by `outlook.exe`, `winword.exe`, or `excel.exe`

    Source-described action candidate under “Step 3: Analyze Running Processes”; not verified execution.

  4. 10
    Action

    Multiple instances of processes that should be singletons (`lsass.exe`, `smss.exe`)

    Source-described action candidate under “Step 3: Analyze Running Processes”; not verified execution.

  5. 11
    Action

    Step 4: Investigate Network Connections

    Source-described action candidate under “Step 4: Investigate Network Connections”; not verified execution.

  6. 12
    Action

    Extract active and recently closed network connections:

    Source-described action candidate under “Step 4: Investigate Network Connections”; not verified execution.

  7. 13
    Action

    Connections to external IPs from unexpected processes

    Source-described action candidate under “Step 4: Investigate Network Connections”; not verified execution.

  8. 14
    Action

    High port numbers connecting to port 443/80 from non-browser processes

    Source-described action candidate under “Step 4: Investigate Network Connections”; not verified execution.

  9. 15
    Action

    Connections from `svchost.exe` or system processes to external IPs

    Source-described action candidate under “Step 4: Investigate Network Connections”; not verified execution.

  10. 16
    Action

    Step 5: Detect Process Injection and Malware

    Source-described action candidate under “Step 5: Detect Process Injection and Malware”; not verified execution.

  11. 17
    Action

    Use malfind to identify injected code and memory-resident malware:

    Source-described action candidate under “Step 5: Detect Process Injection and Malware”; not verified execution.

  12. 18
    Action

    Step 6: Extract Credentials and Artifacts

    Source-described action candidate under “Step 6: Extract Credentials and Artifacts”; not verified execution.

  13. 19
    Output

    Step 7: Generate Forensic Report

    Source-described output candidate under “Step 7: Generate Forensic Report”; not verified execution.

  14. 20
    Action

    Process anomalies with PIDs, parent processes, and timestamps

    Source-described action candidate under “Step 7: Generate Forensic Report”; not verified execution.

  15. 21
    Action

    Network connections with associated process context

    Source-described action candidate under “Step 7: Generate Forensic Report”; not verified execution.

  16. 22
    Action

    Injected code regions with memory protection flags

    Source-described action candidate under “Step 7: Generate Forensic Report”; not verified execution.

  17. 23
    Action

    Extracted IOCs (hashes, IPs, domains, mutexes, registry keys)

    Source-described action candidate under “Step 7: Generate Forensic Report”; not verified execution.

  18. 24
    Action

    YARA rule matches with rule names and match offsets

    Source-described action candidate under “Step 7: Generate Forensic Report”; not verified execution.

  19. 25
    Action

    Credential exposure (hashes found, accounts at risk)

    Source-described action candidate under “Step 7: Generate Forensic Report”; not verified execution.

  20. 26
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  21. 27
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  22. 28
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  23. 29
    Action

    Run `windows.pstree` to identify the process hierarchy and spot abnormal parent-child relationships

    Source-described action candidate under “Scenario: Detecting Cobalt Strike Beacon in Memory”; not verified execution.

  24. 30
    Action

    Run `windows.malfind` to detect injected code regions, particularly in `svchost.exe` or `rundll32.exe`

    Source-described action candidate under “Scenario: Detecting Cobalt Strike Beacon in Memory”; not verified execution.

  25. 31
    Action

    Dump the injected memory region and scan with YARA rules for Cobalt Strike beacon signatures

    Source-described action candidate under “Scenario: Detecting Cobalt Strike Beacon in Memory”; not verified execution.

  26. 32
    Action

    Run `windows.netscan` to identify C2 connections and correlate with the injected process PID

    Source-described action candidate under “Scenario: Detecting Cobalt Strike Beacon in Memory”; not verified execution.

  27. 33
    Action

    Extract the beacon configuration (C2 URLs, sleep time, jitter, watermark) using CobaltStrikeParser

    Source-described action candidate under “Scenario: Detecting Cobalt Strike Beacon in Memory”; not verified execution.

  28. 34
    Action

    Run `windows.cmdline` to identify any post-exploitation commands executed

    Source-described action candidate under “Scenario: Detecting Cobalt Strike Beacon in Memory”; not verified execution.

  29. 35
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

7 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

2 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

3 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Downloaded content may be executed

2 occurrences

This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/conducting-memory-forensics-with-volatility/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/conducting-memory-forensics-with-volatility/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/conducting-memory-forensics-with-volatility
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.