agentleFS
Sign inStart free
hypnguyen1209hypnguyen1209/offensive-claude/skills/incident-response/SKILL.md

incident-response

Skill401 starsChanged 54 days agoMITView on GitHub

Use when responding to or forensically investigating an incident — triage acquisition (Velociraptor/KAPE), Volatility 3 memory forensics, Chainsaw/Hayabusa EVTX timelining, anti-forensics detection, cloud IR, ransomware/ESXi response

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dora-metrics, background-jobs and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jholhewresSkill

    dora-metrics

    Calculate DORA metrics from git + deploy logs

    Also in 3 projects that use this

  • YepAPISkill

    background-jobs

    Queue workers with BullMQ/Inngest/Trigger.dev, job retries, dead letter queues, concurrency.

    Also in 4 projects that use this

  • MicrosoftSkill

    data-modeling

    Use when the app needs to store or read data — records, a database, entities, CRUD, lists, "save/remember X", or per-user data with row-level security. This app's data layer is Rayfin's: you declare entities as TypeScript classes with decorators in rayfin/data/, register them in the schema, and read/write them through the typed rayfin-client. Covers: defining an @entity, field decorators, registering it, per-entity access with @role, owner-only row-level security, and the client query/mutation API. Triggers: data, database, model, entity, schema, table, record, CRUD, create, read, update, delete, list, store, save, persist, per-user, row-level security, RLS, access control, ownership.

    Also in 7 projects that use this

  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 4 projects that use this

  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 5 projects that use this

  • csiddhant796-blipSkill

    threat-detection

    Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry. Covers hypothesis-driven threat hunting, IOC sweep generation, z-score anomaly detection, and MITRE ATT&CK-mapped signal prioritization.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Incident Response & Digital Forensics

When to Activate

  • Active security incident: triage, scoping, evidence acquisition, containment, eradication
  • Memory forensics — process injection, rootkit (incl. eBPF), credential-theft, network artifacts
  • Windows event-log / artifact timelining and super-timeline reconstruction
  • Anti-forensics detection — timestomping, log clearing, secure deletion, VSS recovery
  • Cloud incident response — AWS/Azure/GCP identity-plane attacks and forensic collection
  • Ransomware / extortion response — hypervisor (ESXi) encryption, backup destruction, fast-dwell intrusions
  • Verifying suspect DFIR tooling used as adversary persistence (Velociraptor CVE-2025-6264)
  • Repository-compromise post-mortem — a poisoned public repo / force-pushed malicious commit / deleted PR (recover via dangling commits + GH Archive + Wayback + Events API; see references/repo-compromise-forensics.md)

Technique Map

TechniqueATT&CKCWEReferenceScript
Order-of-volatility live triage (Velociraptor/KAPE/UAC/CatScale)T1074CWE-778references/triage-collection.mdscripts/triage_collector.py
Offline collector build + RAM acquisition (winpmem/LiME/AVML)T1074CWE-778references/triage-collection.mdscripts/triage_collector.py
Suspect-tooling verification (Velociraptor CVE-2025-6264)T1219CWE-269references/triage-collection.mdscripts/triage_collector.py
Volatility 3 process/injection analysis (malfind, hollow)T1055CWE-noinforeferences/memory-forensics.mdscripts/vol3_triage.py
Credential extraction from memory (LSASS, hives)T1003.001CWE-522references/memory-forensics.mdscripts/vol3_triage.py
Kernel + eBPF rootkit detection (LinkPro, linux.ebpf)T1014CWE-269references/memory-forensics.mdscripts/ebpf_rootkit_hunt.sh
EVTX Sigma hunting & fast timeline (Chainsaw/Hayabusa)T1070.001CWE-778references/windows-evtx-timeline.mdscripts/evtx_hunt.sh
Super-timeline (plaso) + Timesketch correlationT1070CWE-778references/windows-evtx-timeline.mdscripts/evtx_hunt.sh
Timestomping detection ($SI vs $FN, USN FILE_CREATE)T1070.006CWE-noinforeferences/anti-forensics-detection.mdscripts/timestomp_detect.py
Log/journal clearing & VSS recoveryT1070.001, T1490CWE-778references/anti-forensics-detection.mdscripts/timestomp_detect.py
Cloud IR — IMDSv2/SSRF cred theft, CloudTrail/GuardDutyT1552.005, T1078.004CWE-918references/cloud-ir.mdscripts/cloud_ir_collect.py
Entra ID / token theft, identity-plane containmentT1528, T1078.004CWE-287references/cloud-ir.mdscripts/cloud_ir_collect.py
Ransomware rapid triage (Windows/Linux)T1486, T1490, T1485CWE-noinforeferences/ransomware-esxi-ir.mdscripts/ransomware_triage.ps1
ESXi / hypervisor ransomware response (UNC3944)T1486CWE-noinforeferences/ransomware-esxi-ir.mdscripts/ransomware_triage.ps1

Quick Start

# 0. PRESERVE ORDER OF VOLATILITY — RAM before disk, never reboot a live host first.
#    Windows RAM:  winpmem_mini_x64.exe mem.raw        Linux RAM: AVML  ./avml mem.lime
# 1. Network-wide / endpoint triage (pick one):
python3 scripts/triage_collector.py --os auto --out /evidence --velociraptor-collector
#    Verify any Velociraptor already on-host is NOT adversary persistence (CVE-2025-6264):
python3 scripts/triage_collector.py --check-velociraptor   # flags <0.73.5 / unknown service

# 2. Memory forensics (Windows or Linux dump):
python3 scripts/vol3_triage.py -f /evidence/mem.raw --os windows --hunt-injection --dump-suspect
bash   scripts/ebpf_rootkit_hunt.sh   # Linux live/IR eBPF rootkit hunt (LinkPro-aware)

# 3. Windows event-log fast timeline + Sigma hunt:
bash scripts/evtx_hunt.sh -d /evidence/C/Windows/System32/winevt/Logs -o /evidence/timeline

# 4. Anti-forensics: timestomp / USN tamper detection from $MFT + $J:
python3 scripts/timestomp_detect.py --mft /evidence/mft.csv --usn /evidence/usn.csv

# 5. Cloud breach (identity-plane first):
python3 scripts/cloud_ir_collect.py aws --collect-cloudtrail --contain-key AKIA... --enforce-imdsv2

# 6. Ransomware on a Windows host (rapid scope, do BEFORE eradication):
powershell -ep bypass -File scripts/ransomware_triage.ps1 -OutDir C:\IR

OPSEC & Detection (summary)

IR is defensive; "OPSEC" below = handling rules that keep evidence admissible and avoid tipping off an adversary who may be monitoring (UNC3944 joins IR bridges in real time).

TechniqueTelemetry / IOCDetection (Sigma / EDR)OPSEC / evidence note
Live triageNew service/scheduled task for collector; large file writes to evidence pathBaseline expected DFIR tooling; alert on unsigned collectorsCollect RAM first; never write evidence to the suspect volume; hash everything
Velociraptor abusevelociraptor.exe svc <0.73.5; MSI from Azure Blob; relaunch after isolationSigma: unexpected Velociraptor service install; CVE-2025-6264 UpdateConfigTreat unexpected Velociraptor as persistence, not your tooling
Memory injectionRX/RWX private VAD not file-backed (malfind); reparented svchostVol3 malfind/hollowprocesses; EDR unbacked-execDocument plugin+offset provenance; keep raw dump read-only
eBPF rootkitbpf_override_return; getdents/sys_bpf hooks; XDP magic-packet (win=54321); /etc/ld.so.preloadlinux.ebpf vs baseline; ss(netlink) vs /proc/net diff; YARA MAL_LinkPro_*bpftool/ps/ss lie on host — acquire RAM out-of-band (hypervisor/LiME RO)
EVTX clearing1102 (Security cleared), 104 (System cleared), gaps in EventRecordIDChainsaw/Hayabusa Sigma; alert on 1102/104Pull EVTX from VSS/disk image, not the tampered live log
Timestomp$SI ≠ $FN create time; sub-second zeros; USN FILE_CREATE mismatchtimestomp_detect.py; MFTECmd Created0x10 vs Created0x30$FN is harder to forge — anchor truth to it + USN/$LogFile
Cloud cred theftInstanceCredentialExfiltration.OutsideAWS; impossible-travel sign-in; CloudTrail StopLoggingGuardDuty findings; Sentinel KQL risky sign-insSnapshot+immutable-export BEFORE remediation; logs to a SIEM the attacker can't reach
Ransomware/ESXiMass file rename/ext change; vCenter/ESXi SSH on; bulk vim-cmd VM power-offSIEM: high-volume VM power-off from one host; vpxuser anomaliesImage before decrypt attempts; preserve note + sample; assume comms compromised

Deep Dives

  • references/triage-collection.md — Order of volatility, RAM acquisition (winpmem/AVML/LiME), Velociraptor 0.75 offline collectors & hunts, KAPE targets, UAC/CatScale for Unix/ESXi, suspect-tooling verification incl. Velociraptor CVE-2025-6264.
  • references/memory-forensics.md — Volatility 3 symbol-table workflow, Windows injection/credential/rootkit plugins, Linux pslist/check_syscall/hidden_modules, eBPF rootkit detection (LinkPro, linux.ebpf, bpf_override_return), dump extraction.
  • references/windows-evtx-timeline.md — Chainsaw v2 & Hayabusa v3 Sigma hunting, key Event IDs, EvtxECmd/Eric Zimmerman parsers, plaso super-timeline, Timesketch + Dissect/Acquire enterprise scaling.
  • references/anti-forensics-detection.md — Timestomping ($SI/$FN + USN cross-validation), log/journal clearing (1102/104, $LogFile gaps), secure-deletion artifacts, VSS recovery, $MFT/$J/$LogFile QuadLink correlation.
  • references/cloud-ir.md — NIST SP 800-61r3 / SP 800-201, AWS CloudTrail/GuardDuty/IMDSv2-SSRF, Azure Entra ID token theft & KQL, GCP audit logs, identity-plane containment, automated evidence preservation.
  • references/ransomware-esxi-ir.md — Ransomware rapid triage & decision flow, Scattered Spider/UNC3944 ESXi LotL chain, backup destruction, cross-platform builders (LockBit 5.0/DragonForce), containment & negotiation hygiene.
  • references/repo-compromise-forensics.md — poisoned public-repo post-mortem from four INDEPENDENT, attacker-uncontrollable sources: dangling/force-pushed commits (dangling_commit_finder.py, git fsck via git_safe), GH Archive + Wayback CDX + live Events API (gharchive_recover.py); hypothesis→verify-at-source (evidence_kit)→adversarial-check→report, attribution-with-confidence, BigQuery kept optional.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free