Back to catalog
Static reviewDevelopment

Skill dossier

detecting-ransomware-precursors-in-network

Source declaration

Detects early-stage ransomware indicators in network traffic before encryption begins, including initial access broker activity, command-and-control beaconing, credential harvesting, reconnaissance scanning, and staging behavior. Uses network detection tools (Zeek, Suricata, Arkime), SIEM correlation rules, and threat intelligence feeds to identify ransomware precursor patterns such as Cobalt Strike beacons, Mimikatz network signatures, and RDP brute-force attempts. Activates for requests involving pre-ransomware detection, network-based ransomware indicators, or early warning ransomware monitoring.

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

Detects early-stage ransomware indicators in network traffic before encryption begins, including initial access broker activity, command-and-control beaconing, credential harvesting, reconnaissance scanning, and staging behavior. Uses network detection tools (Zeek, Suricata, Arkime), SIEM correlation rules, and threat intelligence feeds to identify ransomware precursor patterns such as Cobalt Strike beacons, Mimikatz network signatures, and RDP brute-force attempts. Activates for requests involving pre-ransomware detection, network-based ransomware indicators, or early warning ransomware monitoring.

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.

Detects early-stage ransomware indicators in network traffic before encryption begins, including initial access broker activity, command-and-control beaconing, credential harvesting, reconnaissance scanning, and staging behavior. Uses network detection tools (Zeek, Suricata, Arkime), SIEM correlation rules, and threat intelligence feeds to identify ransomware precursor patterns such as Cobalt Strike beacons, Mimikatz network signatures, and RDP brute-force attempts. Activates for requests involving pre-ransomware detection, network-based ransomware indicators, or early warning ransomware monitoring. 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/detecting-ransomware-precursors-in-network/SKILL.md:L80]
  • Step 1: Identify Ransomware Kill Chain Phases in Network Traffic [Source statement; provisional, not tested. Evidence: skills/detecting-ransomware-precursors-in-network/SKILL.md:L82]
  • Step 2: Deploy Network Detection Rules [Source statement; provisional, not tested. Evidence: skills/detecting-ransomware-precursors-in-network/SKILL.md:L95]
  • Step 3: Create SIEM Correlation Rules [Source statement; provisional, not tested. Evidence: skills/detecting-ransomware-precursors-in-network/SKILL.md:L175]
  • Step 4: Integrate Threat Intelligence [Source statement; provisional, not tested. Evidence: skills/detecting-ransomware-precursors-in-network/SKILL.md:L225]
  • Step 5: Establish Alert Triage and Escalation [Source statement; provisional, not tested. Evidence: skills/detecting-ransomware-precursors-in-network/SKILL.md:L248]

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/detecting-ransomware-precursors-in-network/SKILL.md:L1-L58]

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
8
Markdown files
5
scripts
2
references
4
Size
62.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-ransomware-precursors-in-network/assets/template.mdReference1.6 KB
skills/detecting-ransomware-precursors-in-network/LICENSEOther11 KB
skills/detecting-ransomware-precursors-in-network/references/api-reference.mdReference5.2 KB
skills/detecting-ransomware-precursors-in-network/references/standards.mdReference1.7 KB
skills/detecting-ransomware-precursors-in-network/references/workflows.mdReference2.6 KB
skills/detecting-ransomware-precursors-in-network/scripts/agent.pyScript7.2 KB
skills/detecting-ransomware-precursors-in-network/scripts/process.pyScript19 KB
skills/detecting-ransomware-precursors-in-network/SKILL.mdInstruction14.5 KB

SKILL.md frontmatter

{
  "name": "detecting-ransomware-precursors-in-network",
  "description": "Detects early-stage ransomware indicators in network traffic before encryption begins, including initial access broker activity, command-and-control beaconing, credential harvesting, reconnaissance scanning, and staging behavior. Uses network detection tools (Zeek, Suricata, Arkime), SIEM correlation rules, and threat intelligence feeds to identify ransomware precursor patterns such as Cobalt Strike beacons, Mimikatz network signatures, and RDP brute-force attempts. Activates for requests involving pre-ransomware detection, network-based ransomware indicators, or early warning ransomware monitoring.\n",
  "domain": "cybersecurity",
  "subdomain": "ransomware-defense",
  "tags": [
    "ransomware",
    "detection",
    "network-security",
    "incident-response",
    "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": [
      "initial-access",
      "positioning",
      "monetization"
    ],
    "techniques": [
      {
        "id": "T1110",
        "name": "Brute Force",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1219",
        "name": "Remote Access Tools",
        "tactic": "positioning",
        "source": "attack"
      },
      {
        "id": "T1650",
        "name": "Acquire Access",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "F1018",
        "name": "Convert to Cryptocurrency",
        "tactic": "monetization",
        "source": "f3"
      }
    ]
  }
}

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 Ransomware Kill Chain Phases in Network Traffic

    Source-described action candidate under “Step 1: Identify Ransomware Kill Chain Phases in Network Traffic”; not verified execution.

  4. 04
    Action

    Step 2: Deploy Network Detection Rules

    Source-described action candidate under “Step 2: Deploy Network Detection Rules”; not verified execution.

  5. 05
    Action

    Step 3: Create SIEM Correlation Rules

    Source-described action candidate under “Step 3: Create SIEM Correlation Rules”; not verified execution.

  6. 06
    Action

    Step 4: Integrate Threat Intelligence

    Source-described action candidate under “Step 4: Integrate Threat Intelligence”; not verified execution.

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

    Step 5: Establish Alert Triage and Escalation

    Source-described action candidate under “Step 5: Establish Alert Triage and Escalation”; not verified execution.

  2. 08
    Action

    Key Concepts

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

  3. 09
    Action

    Tools & Systems

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

  4. 10
    Action

    Common Scenarios

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

  5. 11
    Action

    Zeek conn.log analysis shows 10.1.5.42 initiated connections to 47 unique internal IPs on port 445, 135, and 3389 between 01:55-02:05

    Source-described action candidate under “Scenario: Detecting LockBit Precursors in a Manufacturing Network”; not verified execution.

  6. 12
    Action

    Zeek ssl.log reveals an outbound HTTPS connection to 185.x.x.x every 60 seconds with consistent 48-byte payloads (Cobalt Strike beacon pattern)

    Source-described action candidate under “Scenario: Detecting LockBit Precursors in a Manufacturing Network”; not verified execution.

  7. 13
    Action

    RITA beacon analysis confirms high beacon score (0.96) for the external IP with 60-second jitter

    Source-described action candidate under “Scenario: Detecting LockBit Precursors in a Manufacturing Network”; not verified execution.

  8. 14
    Action

    Zeek kerberos.log shows TGS-REQ for multiple SPN accounts from 10.1.5.42 (Kerberoasting)

    Source-described action candidate under “Scenario: Detecting LockBit Precursors in a Manufacturing Network”; not verified execution.

  9. 15
    Action

    SMB treeconnect events show access to ADMIN$ shares on 12 hosts (lateral movement staging)

    Source-described action candidate under “Scenario: Detecting LockBit Precursors in a Manufacturing Network”; not verified execution.

  10. 16
    Action

    Containment: Host isolated, credentials for engineering user reset, blocking rule for C2 IP deployed

    Source-described action candidate under “Scenario: Detecting LockBit Precursors in a Manufacturing Network”; not verified execution.

  11. 17
    Action

    Full IR initiated before ransomware deployment could begin

    Source-described action candidate under “Scenario: Detecting LockBit Precursors in a Manufacturing Network”; not verified execution.

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

98 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
Note

File modification is described or implemented

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

Medium

Network access is mentioned

12 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 12 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/detecting-ransomware-precursors-in-network/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 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/detecting-ransomware-precursors-in-network/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/detecting-ransomware-precursors-in-network
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.