Back to catalog
Static reviewDevelopment

Skill dossier

performing-ransomware-response

Source declaration

Executes a structured ransomware incident response from detection through containment, forensic analysis, decryption assessment, recovery, and post-incident hardening, covering ransom negotiation, backup integrity verification, and regulatory notification. Use when actively responding to a ransomware outbreak or crypto-ransomware infection, or deciding on ransom payment and containment steps.

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

Executes a structured ransomware incident response from detection through containment, forensic analysis, decryption assessment, recovery, and post-incident hardening, covering ransom negotiation, backup integrity verification, and regulatory notification. Use when actively responding to a ransomware outbreak or crypto-ransomware infection, or deciding on ransom payment and containment steps.

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.

Executes a structured ransomware incident response from detection through containment, forensic analysis, decryption assessment, recovery, and post-incident hardening, covering ransom negotiation, backup integrity verification, and regulatory notification. Use when actively responding to a ransomware outbreak or crypto-ransomware infection, or deciding on ransom payment and containment steps. 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/performing-ransomware-response/SKILL.md:L82]
  • Step 1: Detect and Confirm Ransomware [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-response/SKILL.md:L84]
  • Step 2: Immediate Containment [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-response/SKILL.md:L107]
  • Step 3: Assess Damage and Scope [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-response/SKILL.md:L118]
  • Step 4: Recovery Decision Matrix [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-response/SKILL.md:L140]
  • Step 5: Execute Recovery [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-response/SKILL.md:L151]
  • Step 6: Post-Ransomware Hardening [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-response/SKILL.md:L169]

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/performing-ransomware-response/SKILL.md:L1-L59]

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

File inventory

PathTypeBytes
skills/performing-ransomware-response/LICENSEOther11 KB
skills/performing-ransomware-response/references/api-reference.mdReference2 KB
skills/performing-ransomware-response/scripts/agent.pyScript9.1 KB
skills/performing-ransomware-response/SKILL.mdInstruction11.3 KB

SKILL.md frontmatter

{
  "name": "performing-ransomware-response",
  "description": "Executes a structured ransomware incident response from detection through containment, forensic analysis, decryption assessment, recovery, and post-incident hardening, covering ransom negotiation, backup integrity verification, and regulatory notification. Use when actively responding to a ransomware outbreak or crypto-ransomware infection, or deciding on ransom payment and containment steps.\n",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "ransomware",
    "encryption-recovery",
    "backup-restoration",
    "ransom-negotiation",
    "CISA-guidance"
  ],
  "mitre_attack": [
    "T1486",
    "T1490",
    "T1070",
    "T1078",
    "T1489"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "monetization",
      "stealth",
      "initial-access"
    ],
    "techniques": [
      {
        "id": "F1018",
        "name": "Convert to Cryptocurrency",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "F1017",
        "name": "Conversion to Physical Monetary Instruments",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "F1025.003",
        "name": "Electronic Funds Transfer: Wire Transfer",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "T1070",
        "name": "Indicator Removal",
        "tactic": "stealth",
        "source": "attack"
      },
      {
        "id": "F1006",
        "name": "Account Takeover",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  },
  "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: Detect and Confirm Ransomware

    Source-described action candidate under “Step 1: Detect and Confirm Ransomware”; not verified execution.

  4. 04
    Action

    Validate that the incident is ransomware and determine the variant:

    Source-described action candidate under “Step 1: Detect and Confirm Ransomware”; not verified execution.

  5. 05
    Action

    Identify the ransomware by analyzing the ransom note filename, extension appended to encrypted files, and note content

    Source-described action candidate under “Step 1: Detect and Confirm Ransomware”; not verified execution.

  6. 06
    Input

    Upload the ransom note and a sample encrypted file to ID Ransomware (id-ransomware.malwarehunterteam.com)

    Source-described input candidate under “Step 1: Detect and Confirm Ransomware”; not verified execution.

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

    Check NoMoreRansom.org for available free decryptors

    Source-described action candidate under “Step 1: Detect and Confirm Ransomware”; not verified execution.

  2. 08
    Action

    Determine the ransomware deployment method from EDR/SIEM logs

    Source-described action candidate under “Step 1: Detect and Confirm Ransomware”; not verified execution.

  3. 09
    Action

    Identify the ransomware group (e.g., LockBit, BlackCat/ALPHV, Royal, Akira, Play)

    Source-described action candidate under “Step 1: Detect and Confirm Ransomware”; not verified execution.

  4. 10
    Action

    Step 2: Immediate Containment

    Source-described action candidate under “Step 2: Immediate Containment”; not verified execution.

  5. 11
    Action

    Priority 1: Disconnect affected network segments from core infrastructure (pull the network cable, not shutdown)

    Source-described action candidate under “Step 2: Immediate Containment”; not verified execution.

  6. 12
    Decision

    Priority 2: Isolate all domain controllers immediately if GPO-based deployment is suspected

    Source-described decision candidate under “Step 2: Immediate Containment”; not verified execution.

  7. 13
    Action

    Priority 3: Disable the compromised accounts used for deployment

    Source-described action candidate under “Step 2: Immediate Containment”; not verified execution.

  8. 14
    Action

    Priority 4: Block lateral movement protocols (SMB TCP/445, RDP TCP/3389, WinRM TCP/5985-5986)

    Source-described action candidate under “Step 2: Immediate Containment”; not verified execution.

  9. 15
    Action

    Priority 5: Preserve at least one encrypted system live (do not power off) for memory forensics

    Source-described action candidate under “Step 2: Immediate Containment”; not verified execution.

  10. 16
    Action

    Do NOT: Shut down encrypted systems; keep them powered on to preserve encryption keys in memory

    Source-described action candidate under “Step 2: Immediate Containment”; not verified execution.

  11. 17
    Action

    Step 3: Assess Damage and Scope

    Source-described action candidate under “Step 3: Assess Damage and Scope”; not verified execution.

  12. 18
    Action

    Count the number of encrypted systems (workstations, servers, domain controllers)

    Source-described action candidate under “Step 3: Assess Damage and Scope”; not verified execution.

  13. 19
    Action

    Determine which business-critical systems and data are affected

    Source-described action candidate under “Step 3: Assess Damage and Scope”; not verified execution.

  14. 20
    Action

    Verify backup integrity: check that backups were not encrypted, deleted, or corrupted

    Source-described action candidate under “Step 3: Assess Damage and Scope”; not verified execution.

  15. 21
    Decision

    Assess whether data exfiltration occurred (check for rclone, WinSCP, MEGA, cloud storage activity)

    Source-described decision candidate under “Step 3: Assess Damage and Scope”; not verified execution.

  16. 22
    Action

    Determine the ransom demand amount and payment deadline

    Source-described action candidate under “Step 3: Assess Damage and Scope”; not verified execution.

  17. 23
    Action

    Check OFAC sanctions lists to verify the ransomware group is not a sanctioned entity (paying is legally risky)

    Source-described action candidate under “Step 3: Assess Damage and Scope”; not verified execution.

  18. 24
    Action

    Step 4: Recovery Decision Matrix

    Source-described action candidate under “Step 4: Recovery Decision Matrix”; not verified execution.

  19. 25
    Action

    Step 5: Execute Recovery

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  20. 26
    Action

    Build a clean isolated network segment for recovery operations

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  21. 27
    Action

    Rebuild domain controllers first from clean media (do NOT restore DC backups older than the dwell time)

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  22. 28
    Action

    Reset ALL user and service account passwords before joining any system to the new domain

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  23. 29
    Action

    Restore servers in priority order: authentication, DNS, DHCP, then business-critical applications

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  24. 30
    Action

    Restore workstations via reimaging, not file-level restore

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  25. 31
    Action

    Restore data from verified clean backups to rebuilt file servers

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  26. 32
    Action

    Reconnect to production network only after validation

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  27. 33
    Action

    Test the decryptor on a non-critical system first

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  28. 34
    Action

    Decrypt in order of business priority

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  29. 35
    Action

    Scan all decrypted systems for residual malware before reconnection

    Source-described action candidate under “Step 5: Execute Recovery”; not verified execution.

  30. 36
    Action

    Step 6: Post-Ransomware Hardening

    Source-described action candidate under “Step 6: Post-Ransomware Hardening”; not verified execution.

  31. 37
    Action

    Enforce MFA on all remote access (VPN, RDP, cloud portals)

    Source-described action candidate under “Step 6: Post-Ransomware Hardening”; not verified execution.

  32. 38
    Action

    Implement 3-2-1-1-0 backup strategy (3 copies, 2 media types, 1 offsite, 1 immutable, 0 errors)

    Source-described action candidate under “Step 6: Post-Ransomware Hardening”; not verified execution.

  33. 39
    Action

    Deploy application whitelisting on servers

    Source-described action candidate under “Step 6: Post-Ransomware Hardening”; not verified execution.

  34. 40
    Action

    Implement network segmentation between workstation and server VLANs

    Source-described action candidate under “Step 6: Post-Ransomware Hardening”; not verified execution.

  35. 41
    Action

    Enable Protected Users security group for privileged accounts

    Source-described action candidate under “Step 6: Post-Ransomware Hardening”; not verified execution.

  36. 42
    Action

    Disable NTLM authentication where possible

    Source-described action candidate under “Step 6: Post-Ransomware Hardening”; not verified execution.

  37. 43
    Action

    Deploy LAPS (Local Administrator Password Solution) for local admin accounts

    Source-described action candidate under “Step 6: Post-Ransomware Hardening”; not verified execution.

  38. 44
    Action

    Key Concepts

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

  39. 45
    Action

    Tools & Systems

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

  40. 46
    Action

    Common Scenarios

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

  41. 47
    Action

    Disconnect all network segments at the core switch level

    Source-described action candidate under “Scenario: LockBit 3.0 via Compromised VPN”; not verified execution.

  42. 48
    Action

    Verify offline backup integrity (Veeam repository on immutable storage)

    Source-described action candidate under “Scenario: LockBit 3.0 via Compromised VPN”; not verified execution.

  43. 49
    Action

    Preserve two encrypted servers powered on for memory forensics

    Source-described action candidate under “Scenario: LockBit 3.0 via Compromised VPN”; not verified execution.

  44. 50
    Action

    Engage incident response retainer and cyber insurance carrier

    Source-described action candidate under “Scenario: LockBit 3.0 via Compromised VPN”; not verified execution.

  45. 51
    Action

    Begin recovery in isolated network: rebuild DCs, reset all passwords, restore in priority order

    Source-described action candidate under “Scenario: LockBit 3.0 via Compromised VPN”; not verified execution.

  46. 52
    Action

    Conduct forensic investigation in parallel to determine initial access and full adversary activity

    Source-described action candidate under “Scenario: LockBit 3.0 via Compromised VPN”; not verified execution.

  47. 53
    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.

Items warrant review

27 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

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

9 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 9 location(s) in the collected text; 3 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/performing-ransomware-response/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/performing-ransomware-response/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/performing-ransomware-response
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.