deploying-decoy-files-for-ransomware-detection

Deploys monitored canary files across file systems to detect ransomware encryption activity.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill deploying-decoy-files-for-ransomware-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploying-decoy-files-for-ransomware-detection
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/ransomware-defense/deploying-decoy-files-for-ransomware-detection
Command: npx skills add https://github.com/xalgord/xalgorix --skill deploying-decoy-files-for-ransomware-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires watchdog, python-docx.

What problem does it solve?

Ransomware often encrypts files before traditional antivirus or EDR tools raise an alert, leaving teams blind until damage is done. This Skill sets up deception-based tripwires — decoy files that legitimate users never touch — so any modification, rename, or deletion immediately signals active ransomware encryption.

Core Features & Use Cases

  • Strategic Canary Placement: Guides placement of decoy files that sort first and last alphabetically in every share, endpoint folder, and backup staging directory to catch both A-Z and Z-A enumerators early.
  • Realistic Decoy Generation: Creates convincing .docx, .xlsx, and text canaries with realistic content and metadata using python-docx.
  • File System Watching: Implements a Python watchdog-based monitor that catches modification, deletion, and rename events (including ransomware's rename-to-new-extension pattern).
  • Alert Response Matrix: Defines severity tiers and automated responses, from SOC alerts to process kills and network isolation when multiple canaries trip.
  • Use Case: A security engineer seeds canary files across Finance and HR shares, then validates the pipeline by simulating encryption and confirming a SOC alert arrives within 30 seconds.

Quick Start

Deploy canary files across my file shares and set up a watchdog monitor that alerts the SOC when any decoy is modified, renamed, or deleted.

Frequently Asked Questions about deploying-decoy-files-for-ransomware-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect ransomware with canary files?

Place decoy files that sort first and last alphabetically in every monitored directory, then watch them with a file system monitor like Python's watchdog library. Any modification, deletion, or rename of a canary indicates ransomware encryption activity and should trigger an immediate alert.

Where should ransomware canary files be placed?

Place canaries at the root of every file share, on endpoint Desktop and Documents folders, in backup staging directories, and in high-value department shares like Finance and HR. Use names that sort both first and last so A-Z and Z-A enumerators hit them early.

Does the watchdog library detect ransomware file renames?

Yes, but only if the handler watches all event types. Many ransomware families write file.locked and delete the original, which fires on_moved or on_deleted rather than on_modified, so the handler must implement all four event callbacks.

Why do canary files cause false positive alerts?

False positives typically come from backup agents and antivirus scans touching the decoys. Exclude known-good process IDs and paths from alerting, and verify canaries survive backup and restore cycles unmodified before going live.

Are canary files enough to stop ransomware?

No, canary files are a detection mechanism, not prevention. They should complement backups, EDR, and access controls as an early-warning layer with very low false-positive rates, since legitimate users have no reason to touch decoy files.