Back to catalog
Static reviewDevelopment

Skill dossier

extracting-iocs-from-malware-samples

Source declaration

Extracts indicators of compromise (IOCs) from malware samples, including file hashes, network indicators (IPs, domains, URLs, PCAP indicators), host artifacts (file paths, registry keys, mutexes), and behavioral patterns, using tools like CyberChef, then defangs and exports them in standard threat-intel formats. Use for IOC extraction, threat indicator harvesting, or building detection content from a sample.

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

Extracts indicators of compromise (IOCs) from malware samples, including file hashes, network indicators (IPs, domains, URLs, PCAP indicators), host artifacts (file paths, registry keys, mutexes), and behavioral patterns, using tools like CyberChef, then defangs and exports them in standard threat-intel formats. Use for IOC extraction, threat indicator harvesting, or building detection content from a sample.

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.

Extracts indicators of compromise (IOCs) from malware samples, including file hashes, network indicators (IPs, domains, URLs, PCAP indicators), host artifacts (file paths, registry keys, mutexes), and behavioral patterns, using tools like CyberChef, then defangs and exports them in standard threat-intel formats. Use for IOC extraction, threat indicator harvesting, or building detection content from a sample. 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/extracting-iocs-from-malware-samples/SKILL.md:L53]
  • Step 1: Extract File-Based IOCs [Source statement; provisional, not tested. Evidence: skills/extracting-iocs-from-malware-samples/SKILL.md:L55]
  • Step 2: Extract Network IOCs [Source statement; provisional, not tested. Evidence: skills/extracting-iocs-from-malware-samples/SKILL.md:L106]
  • Step 3: Extract Host-Based IOCs [Source statement; provisional, not tested. Evidence: skills/extracting-iocs-from-malware-samples/SKILL.md:L155]
  • Step 4: Extract Network IOCs from PCAP [Source statement; provisional, not tested. Evidence: skills/extracting-iocs-from-malware-samples/SKILL.md:L192]
  • Step 5: Defang and Validate IOCs [Source statement; provisional, not tested. Evidence: skills/extracting-iocs-from-malware-samples/SKILL.md:L216]
  • Step 6: Export IOCs in Standard Formats [Source statement; provisional, not tested. Evidence: skills/extracting-iocs-from-malware-samples/SKILL.md:L256]

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/extracting-iocs-from-malware-samples/SKILL.md:L1-L30]

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
38.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/extracting-iocs-from-malware-samples/LICENSEOther11 KB
skills/extracting-iocs-from-malware-samples/references/api-reference.mdReference2.6 KB
skills/extracting-iocs-from-malware-samples/scripts/agent.pyScript10.7 KB
skills/extracting-iocs-from-malware-samples/SKILL.mdInstruction13.9 KB

SKILL.md frontmatter

{
  "name": "extracting-iocs-from-malware-samples",
  "description": "Extracts indicators of compromise (IOCs) from malware samples, including file hashes, network indicators (IPs, domains, URLs, PCAP indicators), host artifacts (file paths, registry keys, mutexes), and behavioral patterns, using tools like CyberChef, then defangs and exports them in standard threat-intel formats. Use for IOC extraction, threat indicator harvesting, or building detection content from a sample.",
  "domain": "cybersecurity",
  "subdomain": "malware-analysis",
  "tags": [
    "malware",
    "IOC-extraction",
    "threat-intelligence",
    "indicators",
    "detection"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "DE.AE-02",
    "RS.AN-03",
    "ID.RA-01",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1027",
    "T1055",
    "T1140",
    "T1497"
  ]
}

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: Extract File-Based IOCs

    Source-described action candidate under “Step 1: Extract File-Based IOCs”; not verified execution.

  4. 04
    Action

    Step 2: Extract Network IOCs

    Source-described action candidate under “Step 2: Extract Network IOCs”; not verified execution.

  5. 05
    Action

    Step 3: Extract Host-Based IOCs

    Source-described action candidate under “Step 3: Extract Host-Based IOCs”; not verified execution.

  6. 06
    Action

    Step 4: Extract Network IOCs from PCAP

    Source-described action candidate under “Step 4: Extract Network IOCs from PCAP”; not verified execution.

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

    Parse network captures for additional indicators:

    Source-described action candidate under “Step 4: Extract Network IOCs from PCAP”; not verified execution.

  2. 08
    Action

    Step 5: Defang and Validate IOCs

    Source-described action candidate under “Step 5: Defang and Validate IOCs”; not verified execution.

  3. 09
    Output

    Step 6: Export IOCs in Standard Formats

    Source-described output candidate under “Step 6: Export IOCs in Standard Formats”; not verified execution.

  4. 10
    Action

    Generate structured IOC outputs for sharing and ingestion:

    Source-described action candidate under “Step 6: Export IOCs in Standard Formats”; not verified execution.

  5. 11
    Action

    Key Concepts

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

  6. 12
    Action

    Tools & Systems

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

  7. 13
    Action

    Common Scenarios

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

  8. 14
    Action

    Compute all file hashes (MD5, SHA-1, SHA-256, imphash, ssdeep) for the ransomware binary and any dropped files

    Source-described action candidate under “Scenario: Building a Comprehensive IOC Package from a Ransomware Sample”; not verified execution.

  9. 15
    Action

    Extract network IOCs from strings in the binary (hardcoded C2 addresses)

    Source-described action candidate under “Scenario: Building a Comprehensive IOC Package from a Ransomware Sample”; not verified execution.

  10. 16
    Action

    Parse the PCAP for DNS queries, HTTP requests, and TLS SNI fields

    Source-described action candidate under “Scenario: Building a Comprehensive IOC Package from a Ransomware Sample”; not verified execution.

  11. 17
    Output

    Extract host IOCs from the sandbox report (file paths, registry keys, mutexes, ransom note filenames)

    Source-described output candidate under “Scenario: Building a Comprehensive IOC Package from a Ransomware Sample”; not verified execution.

  12. 18
    Action

    Validate all network IOCs against VirusTotal to confirm malicious status and check for known associations

    Source-described action candidate under “Scenario: Building a Comprehensive IOC Package from a Ransomware Sample”; not verified execution.

  13. 19
    Action

    Defang all indicators and compile into STIX 2.1 format for sharing and CSV for SIEM ingestion

    Source-described action candidate under “Scenario: Building a Comprehensive IOC Package from a Ransomware Sample”; not verified execution.

  14. 20
    Action

    Submit to MISP event for organizational and community sharing

    Source-described action candidate under “Scenario: Building a Comprehensive IOC Package from a Ransomware Sample”; not verified execution.

  15. 21
    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

46 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 useObserved
Medium

Network access is mentioned

8 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 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

36 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 36 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

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. 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/extracting-iocs-from-malware-samples/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/extracting-iocs-from-malware-samples/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/extracting-iocs-from-malware-samples
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.