Back to catalog
Static reviewDevelopment

Skill dossier

deploying-decoy-files-for-ransomware-detection

Source declaration

Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for encryption.

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

Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for 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.

Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for 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/deploying-decoy-files-for-ransomware-detection/SKILL.md:L79]
  • Step 1: Design Canary File Strategy [Source statement; provisional, not tested. Evidence: skills/deploying-decoy-files-for-ransomware-detection/SKILL.md:L81]
  • Step 2: Generate Realistic Canary Files [Source statement; provisional, not tested. Evidence: skills/deploying-decoy-files-for-ransomware-detection/SKILL.md:L106]
  • Step 3: Deploy File System Watcher [Source statement; provisional, not tested. Evidence: skills/deploying-decoy-files-for-ransomware-detection/SKILL.md:L132]
  • Step 4: Configure Alerting and Response [Source statement; provisional, not tested. Evidence: skills/deploying-decoy-files-for-ransomware-detection/SKILL.md:L158]
  • Step 5: Validate Detection Coverage [Source statement; provisional, not tested. Evidence: skills/deploying-decoy-files-for-ransomware-detection/SKILL.md:L183]

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/deploying-decoy-files-for-ransomware-detection/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
4
Markdown files
2
scripts
1
references
1
Size
31.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/deploying-decoy-files-for-ransomware-detection/LICENSEOther11 KB
skills/deploying-decoy-files-for-ransomware-detection/references/api-reference.mdReference3.1 KB
skills/deploying-decoy-files-for-ransomware-detection/scripts/agent.pyScript9.2 KB
skills/deploying-decoy-files-for-ransomware-detection/SKILL.mdInstruction8.1 KB

SKILL.md frontmatter

{
  "name": "deploying-decoy-files-for-ransomware-detection",
  "description": "Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for encryption.\n",
  "domain": "cybersecurity",
  "subdomain": "ransomware-defense",
  "tags": [
    "ransomware",
    "detection",
    "canary-files",
    "honeytokens",
    "deception",
    "file-integrity"
  ],
  "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": [
    "T1486",
    "T1083",
    "T1490",
    "T1485"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "monetization",
      "positioning",
      "stealth"
    ],
    "techniques": [
      {
        "id": "F1018",
        "name": "Convert to Cryptocurrency",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "F1017.001",
        "name": "Conversion to Physical Monetary Instruments: Cash",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "T1219",
        "name": "Remote Access Tools",
        "tactic": "positioning",
        "source": "attack"
      },
      {
        "id": "T1070",
        "name": "Indicator Removal",
        "tactic": "stealth",
        "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: Design Canary File Strategy

    Source-described action candidate under “Step 1: Design Canary File Strategy”; not verified execution.

  4. 04
    Action

    Step 2: Generate Realistic Canary Files

    Source-described action candidate under “Step 2: Generate Realistic Canary Files”; not verified execution.

  5. 05
    Action

    Create decoy files with realistic content and metadata:

    Source-described action candidate under “Step 2: Generate Realistic Canary Files”; not verified execution.

  6. 06
    Action

    Step 3: Deploy File System Watcher

    Source-described action candidate under “Step 3: Deploy File System Watcher”; not verified execution.

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

    Step 4: Configure Alerting and Response

    Source-described action candidate under “Step 4: Configure Alerting and Response”; not verified execution.

  2. 08
    Action

    Step 5: Validate Detection Coverage

    Source-described action candidate under “Step 5: Validate Detection Coverage”; not verified execution.

  3. 09
    Action

    Verification

    Source-described action candidate under “Verification”; 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.

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

22 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

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

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

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/deploying-decoy-files-for-ransomware-detection/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/deploying-decoy-files-for-ransomware-detection/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/deploying-decoy-files-for-ransomware-detection
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.