--- name: implementing-honeypot-for-ransomware-detection-4b6ecb686d7f description: 'Deploys canary files, honeypot shares, and decoy systems to detect ransomware activity at the earliest possible stage. Configures canary tokens embedded in strategic file locations that trigger alerts when ransomware attempts encryption, uses honeypot network shares that mimic high-value targets, and deploys Thinkst Canary appliances for comprehensive deception-based detection. Activates for requests involving ransomware honeypots, canary files, deception technology for ransomware, or early ransomware alerting. ' domain: cybersecurity subdomain: ransomware-defense tags: - ransomware - detection - honeypot - canary - defense - deception version: 1.0.0 author: mahipal license: Apache-2.0 d3fend_techniques: - File Metadata Consistency Validation - Content Format Conversion - File Content Analysis - Platform Hardening - File Format Verification nist_csf: - PR.DS-11 - RS.MA-01 - RC.RP-01 - PR.IR-01 mitre_attack: - T1078 - T1190 - T1059 - T1486 - T1490 --- # Implementing Honeypot for Ransomware Detection ## When to Use - Deploying early-warning detection for ransomware encryption attempts using canary files - Creating honeypot file shares that detect lateral movement and data staging before encryption - Supplementing EDR and SIEM-based detection with deception-layer alerts that have near-zero false positives - Detecting ransomware variants that evade signature-based detection by triggering on file modification behavior - Validating that ransomware detection capabilities work by testing with controlled encryption tools **Do not use** as the sole ransomware detection mechanism. Honeypots are a high-confidence supplementary layer, not a replacement for EDR, network monitoring, and backup protection. ## Prerequisites - File server or NAS infrastructure where canary files can be deployed - Windows File Server Resource Manager (FSRM) or equivalent file activity monitoring - Thinkst Canary or similar deception platform (optional, for advanced deployment) - SIEM platform for centralizing honeypot alerts - Administrative access to deploy canary files across file shares - Network segment for honeypot systems (if deploying full honeypot servers) ## Workflow ### Step 1: Deploy Canary Files on File Shares Place canary files in strategic locations that ransomware will encounter during encryption: ```powershell # Deploy canary files across all file shares # Files are named to appear early in alphabetical and directory order # Ransomware typically encrypts alphabetically or by directory traversal $shares = @("\\fileserver01\finance", "\\fileserver01\hr", "\\fileserver01\engineering") $canaryNames = @( "!_IMPORTANT_DO_NOT_DELETE.docx", "000_Budget_2026_FINAL.xlsx", "_Confidential_Employee_Records.pdf", "AAAA_Quarterly_Report.docx" ) foreach ($share in $shares) { foreach ($name in $canaryNames) { $targetPath = Join-Path $share $name # Create a legitimate-looking file with canary content # The file contains a unique token that triggers on access $content = "This document contains confidential financial data.`n" $content += "Q4 2025 Revenue: $42.3M | Q1 2026 Forecast: $45.1M`n" $content += "Prepared by: Finance Department`n" Set-Content -Path $targetPath -Value $content # Set file as hidden system to avoid user interaction $file = Get-Item $targetPath $file.Attributes = [System.IO.FileAttributes]::Hidden } } # Also deploy in subdirectories (ransomware traverses recursively) $subDirs = Get-ChildItem -Path "\\fileserver01\finance" -Directory -Recurse | Select-Object -First 20 foreach ($dir in $subDirs) { $canaryPath = Join-Path $dir.FullName "!_Budget_Summary.xlsx" Set-Content -Path $canaryPath -Value "Canary file for ransomware detection" (Get-Item $canaryPath).Attributes = [System.IO.FileAttributes]::Hidden } ``` ### Step 2: Configure File Integrity Monitoring on Canary Files **Windows FSRM approach:** ```powershell # Configure FSRM to monitor for ransomware file extensions # and canary file modifications Install-WindowsFeature -Name FS-Resource-Manager -IncludeManagementTools # Create file screen for known ransomware extensions $ransomExtensions = @( "*.encrypted", "*.locked", "*.crypto", "*.crypt", "*.locky", "*.cerber", "*.zepto", "*.thor", "*.aesir", "*.zzzzz", "*.wallet", "*.onion", "*.wncry", "*.wcry", "*.lockbit", "*.BlackCat", "*.ALPHV", "*.rhysida", "*.play" ) # Create file group for ransomware extensions New-FsrmFileGroup -Name "Ransomware_Extensions" -IncludePattern $ransomExtensions # Create file screen template New-FsrmFileScreenTemplate -Name "Ransomware_Screen" ` -IncludeGroup "Ransomware_Extensions" ` -Active:$false # Passive mode: alert without blocking # Apply to all monitored shares $monitoredPaths = @("D:\Shares\Finance", "D:\Shares\HR", "D:\Shares\Engineering") foreach ($path in $monitoredPaths) { New-FsrmFileScreen -Path $path -Template "Ransomware_Screen" } ``` **Canary file modification monitoring with PowerShell FileSystemWatcher:** ```powershell # Real-time canary file monitoring service $canaryPaths = @( "D:\Shares\Finance\!_IMPORTANT_DO_NOT_DELETE.docx", "D:\Shares\HR\000_Budget_2026_FINAL.xlsx", "D:\Shares\Engineering\_Confidential_Employee_Records.pdf" ) $watcher = New-Object System.IO.FileSystemWatcher $watcher.Path = "D:\Shares" $watcher.Filter = "*" $watcher.IncludeSubdirectories = $true $watcher.EnableRaisingEvents = $true $action = { $path = $Event.SourceEventArgs.FullPath $changeType = $Event.SourceEventArgs.ChangeType $timestamp = $Event.TimeGenerated # Check if modified file is a canary $isCanary = $false foreach ($canary in $canaryPaths) { if ($path -eq $canary) { $isCanary = $true; break } } if ($isCanary -or $changeType -eq "Renamed") { $alertMsg = "RANSOMWARE ALERT: Canary file modified! Path: $path | Change: $changeType | Time: $timestamp" # Log to Windows Event Log Write-EventLog -LogName Application -Source "RansomwareCanary" ` -EventID 9999 -EntryType Error -Message $alertMsg # Send SIEM alert via syslog # Trigger automated containment } } Register-ObjectEvent $watcher "Changed" -Action $action Register-ObjectEvent $watcher "Deleted" -Action $action Register-ObjectEvent $watcher "Renamed" -Action $action ``` ### Step 3: Deploy Honeypot Network Shares Create decoy file shares that appear to contain high-value data: ```powershell # Create honeypot share on dedicated server # This server monitors ALL file access and alerts on any activity New-Item -Path "D:\HoneypotShares\Executive_Compensation" -ItemType Directory New-Item -Path "D:\HoneypotShares\M&A_Documents" -ItemType Directory New-Item -Path "D:\HoneypotShares\Board_Meeting_Notes" -ItemType Directory New-Item -Path "D:\HoneypotShares\Customer_Database_Exports" -ItemType Directory # Share with broad read access (enticing to attackers) New-SmbShare -Name "Executive_Compensation" ` -Path "D:\HoneypotShares\Executive_Compensation" ` -FullAccess "DOMAIN\Domain Users" ` -Description "Executive Compensation Files - Restricted" # Populate with realistic-looking but fake documents # Use document templates that look legitimate $docContent = @" CONFIDENTIAL - Executive Compensation Summary FY 2026 Base Salary and Bonus Structures CEO: [REDACTED] | CFO: [REDACTED] | CTO: [REDACTED] Total Compensation Package: See Appendix A "@ Set-Content -Path "D:\HoneypotShares\Executive_Compensation\FY2026_Comp_Summary.txt" -Value $docContent # Enable detailed audit logging on honeypot share $acl = Get-Acl "D:\HoneypotShares" $auditRule = New-Object System.Security.AccessControl.FileSystemAuditRule( "Everyone", "ReadAndExecute,Write,Delete", "ContainerInherit,ObjectInherit", "None", "Success,Failure" ) $acl.AddAuditRule($auditRule) Set-Acl "D:\HoneypotShares" $acl # Enable object access auditing via GPO auditpol /set /subcategory:"File System" /success:enable /failure:enable ``` ### Step 4: Deploy Thinkst Canary Tokens For organizations using Thinkst Canary or the free canarytokens.org service: ```bash # Generate canary tokens via API (Thinkst Canary) # These trigger alerts when documents are opened or URLs are accessed # Word document token curl -X POST "https://CONSOLE.canary.tools/api/v1/canarytoken/create" \ -d "auth_token=YOUR_API_TOKEN" \ -d "memo=Finance_Share_Canary" \ -d "kind=doc-msword" \ -o /tmp/canary_budget_report.docx # PDF document token curl -X POST "https://CONSOLE.canary.tools/api/v1/canarytoken/create" \ -d "auth_token=YOUR_API_TOKEN" \ -d "memo=HR_Share_Canary" \ -d "kind=pdf-acrobat-reader" \ -o /tmp/canary_employee_handbook.pdf # Windows folder token (alerts when folder is browsed) curl -X POST "https://CONSOLE.canary.tools/api/v1/canarytoken/create" \ -d "auth_token=YOUR_API_TOKEN" \ -d "memo=Executive_Folder_Browse" \ -d "kind=windows-dir" # Deploy Canary appliance (emulates a file server) # Configure via web console to appear as: # - Windows file server with SMB shares # - Contains realistic-looking directories # - Any access triggers immediate alert with source IP and activity details ``` ### Step 5: Integrate Alerts with SIEM and Automated Response ```python # siem_integration.py - Forward honeypot alerts to SIEM and trigger containment import json import requests import logging from datetime import datetime SIEM_WEBHOOK = "https://siem.company.com/api/alerts" NAC_API = "https://nac.company.com/api/v1/quarantine" EDR_API = "https://edr.company.com/api/v1/isolate" def send_ransomware_alert(source_ip: str, canary_path: str, action: str): """Send high-priority alert to SIEM and trigger automated containment.""" alert = { "timestamp": datetime.utcnow().isoformat(), "severity": "CRITICAL", "category": "Ransomware - Canary File Triggered", "source_ip": source_ip, "canary_file": canary_path, "action_detected": action, "automated_response": "Host isolation initiated", "mitre_technique": "T1486 - Data Encrypted for Impact", } # Send to SIEM try: requests.post(SIEM_WEBHOOK, json=alert, timeout=5) except requests.RequestException as e: logging.error(f"SIEM alert failed: {e}") # Automated containment - isolate host via NAC try: requests.post(f"{NAC_API}/{source_ip}", json={"action": "quarantine", "reason": "Ransomware canary triggered"}, timeout=5) except requests.RequestException as e: logging.error(f"NAC quarantine failed: {e}") # Automated containment - isolate host via EDR try: requests.post(EDR_API, json={"ip": source_ip, "action": "isolate"}, timeout=5) except requests.RequestException as e: logging.error(f"EDR isolation failed: {e}") logging.critical(f"RANSOMWARE CANARY ALERT: {source_ip} modified {canary_path} ({action})") ``` ## Key Concepts | Term | Definition | |------|------------| | **Canary File** | A decoy file placed in strategic locations that triggers an alert when modified, renamed, or deleted by ransomware | | **Honeypot Share** | A decoy network share designed to attract attackers, where any access is suspicious and triggers alerts | | **Canary Token** | A trackable token embedded in a document or URL that reports back when accessed, revealing the accessor's IP and time | | **FSRM** | File Server Resource Manager - Windows Server role that monitors file operations and can screen for ransomware extensions | | **Deception Layer** | Security architecture layer using decoy assets to detect threats with near-zero false positive rates | | **File System Watcher** | System service that monitors real-time file system changes (creation, modification, deletion, rename) | ## Tools & Systems - **Thinkst Canary**: Commercial deception platform providing canary appliances (emulate servers) and canary tokens (trackable documents) - **Canarytokens.org**: Free service from Thinkst for generating basic canary tokens (Word docs, PDFs, URLs, DNS) - **OpenCanary**: Open-source honeypot daemon that emulates common services (SMB, RDP, SSH) and logs access attempts - **FSRM (File Server Resource Manager)**: Windows Server built-in tool for file screening, quota management, and ransomware extension detection - **Elastic Endpoint**: Uses canary files internally for ransomware protection, triggering behavioral alerts on canary modification ## Common Scenarios ### Scenario: Early Detection of BlackByte Ransomware via Canary Files **Context**: A retail company deploys canary files across 200 file shares and 3 honeypot shares. At 3:00 AM on a Saturday, the canary monitoring system generates 47 alerts in rapid succession as canary files across 12 shares are modified within 90 seconds. **Approach**: 1. Canary file alert triggers automated containment: source workstation (10.2.8.55) quarantined via NAC within 30 seconds 2. SIEM correlation shows the source workstation had EDR alerts for PsExec execution 2 hours earlier (missed by overnight SOC) 3. Additional canary alerts from 3 other workstations indicate the ransomware is spreading via scheduled tasks 4. IR team isolates the affected VLAN, preventing encryption of the remaining 188 file shares 5. The 12 affected shares are restored from immutable backups within 4 hours 6. Estimated damage prevented: $2.3M in downtime and recovery costs based on the 95% of shares protected **Pitfalls**: - Placing canary files only in root directories where ransomware may skip them by targeting subdirectories first - Using obvious canary names that sophisticated ransomware may recognize and avoid - Not testing canary alerting end-to-end, discovering during an actual incident that alerts are not reaching the SOC - Generating excessive canary alerts during legitimate file migrations or antivirus scans, causing alert fatigue ## Output Format ``` ## Ransomware Honeypot Deployment Report **Organization**: [Name] **Deployment Date**: [Date] ### Canary File Deployment | Share | Files Deployed | Naming Convention | Alert Method | |-------|---------------|-------------------|--------------| | [Share path] | [Count] | [Pattern] | [FSRM/Watcher/Token] | ### Honeypot Shares | Share Name | Location | Apparent Content | Monitoring | |-----------|----------|-----------------|------------| | [Name] | [Server] | [Description] | [Audit/Canary] | ### Alert Integration - SIEM: [Connected/Not Connected] - Automated Containment: [EDR Isolation/NAC Quarantine/None] - Alert SLA: [Expected response time] ### Testing Results | Test Date | Test Type | Canary Triggered | Alert Received | Containment Executed | Time to Alert | |-----------|----------|-----------------|----------------|---------------------|---------------| ``` --- Source attribution: 26zl Original project: https://github.com/26zl/cybersec-toolkit/blob/2ad2519d437cda1f8a822ef7adc336993601a5ac/.claude/skills/implementing-honeypot-for-ransomware-detection/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: 26zl Original project: https://github.com/26zl/cybersec-toolkit/blob/2ad2519d437cda1f8a822ef7adc336993601a5ac/.claude/skills/implementing-honeypot-for-ransomware-detection/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Security Engineer Specialties: Backend Tools: Siem Platform, Thinkst Canary Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: c2a59bed4135aa60dad5df98625a28f59b87ef6ac20679220137de25ceb382be