Back to catalog
Static reviewDevelopment

Skill dossier

recovering-from-ransomware-attack

Source declaration

Executes structured ransomware incident recovery following NIST/CISA frameworks: environment isolation, forensic evidence preservation, clean infrastructure rebuild, prioritized restoration from verified backups, credential reset, and Active Directory/database recovery in dependency order. Use when recovering from a ransomware attack, performing post-encryption restoration, or executing disaster recovery after ransomware encryption.

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

Executes structured ransomware incident recovery following NIST/CISA frameworks: environment isolation, forensic evidence preservation, clean infrastructure rebuild, prioritized restoration from verified backups, credential reset, and Active Directory/database recovery in dependency order. Use when recovering from a ransomware attack, performing post-encryption restoration, or executing disaster recovery after ransomware encryption.

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 structured ransomware incident recovery following NIST/CISA frameworks: environment isolation, forensic evidence preservation, clean infrastructure rebuild, prioritized restoration from verified backups, credential reset, and Active Directory/database recovery in dependency order. Use when recovering from a ransomware attack, performing post-encryption restoration, or executing disaster recovery after ransomware encryption. 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/recovering-from-ransomware-attack/SKILL.md:L78]
  • Step 1: Establish Clean Recovery Environment [Source statement; provisional, not tested. Evidence: skills/recovering-from-ransomware-attack/SKILL.md:L80]
  • Step 2: Recover Identity Infrastructure First [Source statement; provisional, not tested. Evidence: skills/recovering-from-ransomware-attack/SKILL.md:L101]
  • Step 3: Validate Backup Integrity Before Restoration [Source statement; provisional, not tested. Evidence: skills/recovering-from-ransomware-attack/SKILL.md:L144]
  • Step 4: Restore Systems in Priority Order [Source statement; provisional, not tested. Evidence: skills/recovering-from-ransomware-attack/SKILL.md:L167]
  • Step 5: Validate Recovered Systems and Harden [Source statement; provisional, not tested. Evidence: skills/recovering-from-ransomware-attack/SKILL.md:L211]
  • Step 6: Phased Network Reconnection [Source statement; provisional, not tested. Evidence: skills/recovering-from-ransomware-attack/SKILL.md:L249]

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/recovering-from-ransomware-attack/SKILL.md:L1-L56]

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
7
Markdown files
4
scripts
2
references
3
Size
45 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/recovering-from-ransomware-attack/LICENSEOther11 KB
skills/recovering-from-ransomware-attack/references/api-reference.mdReference1.7 KB
skills/recovering-from-ransomware-attack/references/standards.mdReference1 KB
skills/recovering-from-ransomware-attack/references/workflows.mdReference1.4 KB
skills/recovering-from-ransomware-attack/scripts/agent.pyScript6.6 KB
skills/recovering-from-ransomware-attack/scripts/process.pyScript10.9 KB
skills/recovering-from-ransomware-attack/SKILL.mdInstruction12.5 KB

SKILL.md frontmatter

{
  "name": "recovering-from-ransomware-attack",
  "description": "Executes structured ransomware incident recovery following NIST/CISA frameworks: environment isolation, forensic evidence preservation, clean infrastructure rebuild, prioritized restoration from verified backups, credential reset, and Active Directory/database recovery in dependency order. Use when recovering from a ransomware attack, performing post-encryption restoration, or executing disaster recovery after ransomware encryption.\n",
  "domain": "cybersecurity",
  "subdomain": "ransomware-defense",
  "tags": [
    "ransomware",
    "recovery",
    "incident-response",
    "backup",
    "defense"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.DS-11",
    "RS.MA-01",
    "RC.RP-01",
    "PR.IR-01"
  ],
  "mitre_attack": [
    "T1078",
    "T1190",
    "T1059",
    "T1003",
    "T1110"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "positioning",
      "monetization",
      "defense-impairment"
    ],
    "techniques": [
      {
        "id": "T1531",
        "name": "Account Access Removal",
        "tactic": "positioning",
        "source": "attack"
      },
      {
        "id": "F1005",
        "name": "Account Manipulation",
        "tactic": "defense-impairment",
        "source": "f3"
      },
      {
        "id": "F1018",
        "name": "Convert to Cryptocurrency",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "T1219",
        "name": "Remote Access Tools",
        "tactic": "positioning",
        "source": "attack"
      }
    ]
  }
}

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: Establish Clean Recovery Environment

    Source-described action candidate under “Step 1: Establish Clean Recovery Environment”; not verified execution.

  4. 04
    Action

    Step 2: Recover Identity Infrastructure First

    Source-described action candidate under “Step 2: Recover Identity Infrastructure First”; not verified execution.

  5. 05
    Action

    Step 3: Validate Backup Integrity Before Restoration

    Source-described action candidate under “Step 3: Validate Backup Integrity Before Restoration”; not verified execution.

  6. 06
    Action

    Step 4: Restore Systems in Priority Order

    Source-described action candidate under “Step 4: Restore Systems in Priority Order”; not verified execution.

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

    Step 5: Validate Recovered Systems and Harden

    Source-described action candidate under “Step 5: Validate Recovered Systems and Harden”; not verified execution.

  2. 08
    Action

    Step 6: Phased Network Reconnection

    Source-described action candidate under “Step 6: Phased Network Reconnection”; not verified execution.

  3. 09
    Action

    Key Concepts

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

  4. 10
    Action

    Tools & Systems

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

  5. 11
    Action

    Common Scenarios

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

  6. 12
    Action

    Establish recovery VLAN (10.99.0.0/24) isolated from compromised network

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; not verified execution.

  7. 13
    Action

    Restore 2 domain controllers from immutable backup using Veeam Instant Recovery (2 hours)

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; not verified execution.

  8. 14
    Action

    Reset krbtgt password twice with 12-hour gap, reset all admin passwords

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; not verified execution.

  9. 15
    Action

    Validate AD with dcdiag, scan for Golden Ticket indicators with DSInternals

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; not verified execution.

  10. 16
    Action

    Restore ERP database (SAP) and verify data consistency (4 hours)

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; not verified execution.

  11. 17
    Action

    Restore MES (Manufacturing Execution System) and SCADA historians (3 hours)

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; not verified execution.

  12. 18
    Action

    Bring production line controllers online in isolated OT network first

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; not verified execution.

  13. 19
    Action

    Phased reconnection over 48 hours with continuous EDR monitoring

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; not verified execution.

  14. 20
    Action

    Total recovery: 72 hours (within 96-hour RTO commitment)

    Source-described action candidate under “Scenario: Manufacturing Company Full Recovery After LockBit Attack”; 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

26 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

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

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

File deletion is described or implemented

3 occurrences

Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. 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.

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/recovering-from-ransomware-attack/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 7 collected file(s), 4 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/recovering-from-ransomware-attack/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/recovering-from-ransomware-attack
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.