ransomware-response
Skill0 starsChanged 13 days agoMITView on GitHub
Respond to a ransomware or extortion incident — stop encryption spread, preserve evidence, identify the variant and access vector, assess data theft, protect backups and drive recovery decisions. Use when encryption, ransom notes, mass file renames, shadow-copy deletion or a data-leak-site extortion claim is observed.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- dandye/adk_runbookstheir own version, first seen Nov 1, 2026
- blamejs/exceptd-skillstheir own version, first seen Aug 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- dandye/adk_runbooks★ 88same name
- blamejs/exceptd-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository273 other files it gives its agents.
- ad-attack-path-analysisSkill
- adcs-security-reviewSkill
- ad-privileged-access-reviewSkill
- dcsync-detectionSkill
- gpo-security-reviewSkill
- kerberos-attack-detectionSkill
- agent-tool-permission-reviewSkill
- ai-incident-responseSkill
- llm-gateway-controlsSkill
- llm-security-evaluationSkill
- mcp-server-security-reviewSkill
- model-artifact-securitySkill
- prompt-injection-reviewSkill
- rag-security-reviewSkill
- api-abuse-detectionSkill
- api-authorization-testingSkill
- api-inventorySkill
- api-schema-securitySkill
- dast-baselineSkill
- sast-triageSkill
- sca-dependency-riskSkill
- secure-code-reviewSkill
- security-requirementsSkill
- threat-modelingSkill
- asset-criticality-tieringSkill
- asset-inventory-reconciliationSkill
- external-attack-surface-reviewSkill
- shadow-it-discoverySkill
- aws-credential-compromiseSkill
- aws-iam-reviewSkill
- aws-org-guardrailsSkill
- cloudtrail-investigationSkill
- guardduty-triageSkill
- s3-exposure-reviewSkill
- azure-activity-investigationSkill
- azure-rbac-reviewSkill
- conditional-access-reviewSkill
- entra-audit-investigationSkill
- entra-signin-investigationSkill
- backup-assuranceSkill
- critical-service-mappingSkill
- ransomware-recoverySkill
- recovery-exerciseSkill
- cloud-exposure-reviewSkill
- cloud-incident-responseSkill
- cloud-logging-baselineSkill
- cloud-posture-assessmentSkill
- audit-evidence-packageSkill
- continuous-control-monitoringSkill
- control-mappingSkill
- control-testing-samplingSkill
- container-incidentSkill
- dockerfile-hardeningSkill
- image-scanningSkill
- runtime-detection-falcoSkill
- db-audit-loggingSkill
- db-exfiltration-investigationSkill
- db-hardeningSkill
- db-privilege-reviewSkill
- data-classificationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Do not run the encryptor, do not contact the threat actor (negotiation is done by designated specialists under counsel), and do not wipe …
- Distinctive: line 64
No More Ransom: https://www.nomoreransom.org/
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ransomware Response
Modern ransomware is usually double extortion: data theft precedes encryption, often by days. Restoring files does not end the incident.
Immediate actions (first hour)
- Isolate affected hosts via EDR and, if spreading, segment at the network (block SMB/RDP east-west, disable VPN for affected users). Prefer isolation over power-off to keep memory.
- Protect backups: confirm backup consoles and repositories are not reachable from compromised credentials; disable compromised backup admin accounts; verify immutability/air-gap copies.
- Disable or reset compromised privileged accounts; identify accounts used for deployment (GPO, PsExec, SCCM, RMM tools).
- Preserve: memory from 1–2 representative hosts, a ransom note, an encrypted file sample, the encryptor binary if found, relevant logs (DC, VPN, EDR) before they roll.
- Engage: IC, legal/counsel (privilege), cyber insurer (notification clause), IR retainer, executive crisis team.
Investigation
| Question | Sources |
| Variant? | Ransom note, extension, ID Ransomware, No More Ransom; vendor intel |
| Initial access? | VPN/RDP logs, exploited edge device (check CISA KEV), phishing, valid accounts |
| Deployment method? | GPO changes (5136), service installs (7045), PsExec, scheduled tasks, RMM tools |
| Data exfiltration? | Large outbound transfers, rclone/MEGAsync/WinSCP execution, cloud storage uploads, proxy logs |
| Dwell time? | Earliest attacker artifact vs. encryption time |
Encryption precursors to hunt/alert on: vssadmin delete shadows, wmic shadowcopy delete, bcdedit /set {default} recoveryenabled no, wbadmin delete catalog, mass service stop of SQL/backup/AV, Set-MpPreference -DisableRealtimeMonitoring.
Decision points for leadership
- Restore vs. rebuild scope; restore order (
critical-service-mapping). - Extortion response: payment decisions are legal/board decisions; check sanctions screening (e.g., OFAC advisory) and law-enforcement engagement. Analysts provide facts, not recommendations to pay.
- Regulatory and customer notification if data was stolen (
privacy-incident-assessment).
Output template
Ransomware incident <id> — <UTC>
Variant: <> (confidence) Encryption start: <t> Affected: <n hosts/services>
Initial access: <> Dwell time: <>
Exfiltration: confirmed/likely/not observed (evidence)
Backups: status/integrity/immutability
Containment status: <>
Decisions needed: <>Safety
Do not run the encryptor, do not contact the threat actor (negotiation is done by designated specialists under counsel), and do not wipe encrypted systems before evidence and decryption options are evaluated.
Related skills
ransomware-recovery, containment-plan, backup-assurance, incident-scoping, privacy-incident-assessment
References
- CISA #StopRansomware Guide: https://www.cisa.gov/stopransomware/ransomware-guide
- No More Ransom: https://www.nomoreransom.org/
- OFAC updated advisory on ransomware payments (2021): https://ofac.treasury.gov/recent-actions/20210921
- CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

