Back to catalog
Static reviewDevelopment

Skill dossier

analyzing-ransomware-encryption-mechanisms

Source declaration

Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts. Covers AES, RSA, ChaCha20, and hybrid encryption schemes. Activates for requests involving ransomware cryptanalysis, encryption analysis, key recovery assessment, or ransomware decryption feasibility.

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

Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts. Covers AES, RSA, ChaCha20, and hybrid encryption schemes. Activates for requests involving ransomware cryptanalysis, encryption analysis, key recovery assessment, or ransomware decryption feasibility.

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.

Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts. Covers AES, RSA, ChaCha20, and hybrid encryption schemes. Activates for requests involving ransomware cryptanalysis, encryption analysis, key recovery assessment, or ransomware decryption feasibility. 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/analyzing-ransomware-encryption-mechanisms/SKILL.md:L72]
  • Step 1: Identify the Encryption Algorithm [Source statement; provisional, not tested. Evidence: skills/analyzing-ransomware-encryption-mechanisms/SKILL.md:L74]
  • Step 2: Analyze Key Generation and Management [Source statement; provisional, not tested. Evidence: skills/analyzing-ransomware-encryption-mechanisms/SKILL.md:L114]
  • Step 3: Examine File Encryption Routine [Source statement; provisional, not tested. Evidence: skills/analyzing-ransomware-encryption-mechanisms/SKILL.md:L141]
  • Step 4: Check for Cryptographic Weaknesses [Source statement; provisional, not tested. Evidence: skills/analyzing-ransomware-encryption-mechanisms/SKILL.md:L179]
  • Step 5: Attempt Key Recovery [Source statement; provisional, not tested. Evidence: skills/analyzing-ransomware-encryption-mechanisms/SKILL.md:L235]
  • Step 6: Document Encryption Analysis [Source statement; provisional, not tested. Evidence: skills/analyzing-ransomware-encryption-mechanisms/SKILL.md:L263]

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/analyzing-ransomware-encryption-mechanisms/SKILL.md:L1-L49]

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

File inventory

PathTypeBytes
skills/analyzing-ransomware-encryption-mechanisms/LICENSEOther11 KB
skills/analyzing-ransomware-encryption-mechanisms/references/api-reference.mdReference4 KB
skills/analyzing-ransomware-encryption-mechanisms/scripts/agent.pyScript13.5 KB
skills/analyzing-ransomware-encryption-mechanisms/SKILL.mdInstruction13.9 KB

SKILL.md frontmatter

{
  "name": "analyzing-ransomware-encryption-mechanisms",
  "description": "Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts. Covers AES, RSA, ChaCha20, and hybrid encryption schemes. Activates for requests involving ransomware cryptanalysis, encryption analysis, key recovery assessment, or ransomware decryption feasibility.\n",
  "domain": "cybersecurity",
  "subdomain": "malware-analysis",
  "tags": [
    "malware",
    "ransomware",
    "encryption",
    "cryptanalysis",
    "reverse-engineering"
  ],
  "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": [
    "T1486",
    "T1573.001",
    "T1573.002",
    "T1027"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "monetization",
      "positioning"
    ],
    "techniques": [
      {
        "id": "F1018",
        "name": "Convert to Cryptocurrency",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "F1047",
        "name": "Transfer of funds",
        "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: Identify the Encryption Algorithm

    Source-described action candidate under “Step 1: Identify the Encryption Algorithm”; not verified execution.

  4. 04
    Action

    Step 2: Analyze Key Generation and Management

    Source-described action candidate under “Step 2: Analyze Key Generation and Management”; not verified execution.

  5. 05
    Action

    Step 3: Examine File Encryption Routine

    Source-described action candidate under “Step 3: Examine File Encryption Routine”; not verified execution.

  6. 06
    Action

    Step 4: Check for Cryptographic Weaknesses

    Source-described action candidate under “Step 4: Check for Cryptographic Weaknesses”; not verified execution.

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

    Step 5: Attempt Key Recovery

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

  2. 08
    Action

    Use identified weaknesses for key recovery:

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

  3. 09
    Action

    Step 6: Document Encryption Analysis

    Source-described action candidate under “Step 6: Document Encryption Analysis”; not verified execution.

  4. 10
    Action

    Key Concepts

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

  5. 11
    Action

    Tools & Systems

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

  6. 12
    Action

    Common Scenarios

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

  7. 13
    Action

    Identify the ransomware family from ransom note, file extension, and sample hash (check ID Ransomware)

    Source-described action candidate under “Scenario: Assessing Decryption Feasibility for a Ransomware Incident”; not verified execution.

  8. 14
    Action

    Check NoMoreRansom.org for existing free decryptors for this family

    Source-described action candidate under “Scenario: Assessing Decryption Feasibility for a Ransomware Incident”; not verified execution.

  9. 15
    Action

    Reverse engineer the encryption routine in Ghidra to identify the algorithm and key management

    Source-described action candidate under “Scenario: Assessing Decryption Feasibility for a Ransomware Incident”; not verified execution.

  10. 16
    Action

    Test for implementation weaknesses (key reuse, predictable seeds, ECB mode)

    Source-described action candidate under “Scenario: Assessing Decryption Feasibility for a Ransomware Incident”; not verified execution.

  11. 17
    Decision

    Check if PCAP from the incident captured the key transmission to C2 (if key was sent before encryption)

    Source-described decision candidate under “Scenario: Assessing Decryption Feasibility for a Ransomware Incident”; not verified execution.

  12. 18
    Action

    Scan memory dumps from affected machines for AES key schedules in RAM

    Source-described action candidate under “Scenario: Assessing Decryption Feasibility for a Ransomware Incident”; not verified execution.

  13. 19
    Output

    Report findings: decryption possible/impossible with specific technical justification

    Source-described output candidate under “Scenario: Assessing Decryption Feasibility for a Ransomware Incident”; not verified execution.

  14. 20
    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

34 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

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

29 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 29 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/analyzing-ransomware-encryption-mechanisms/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/analyzing-ransomware-encryption-mechanisms/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/analyzing-ransomware-encryption-mechanisms
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.