cleanup-template
Cleanup & restoration plan generator — artifact inventory, persistence removal commands, pre-engagement baseline, post-engagement verification.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- cleanup-template
- metadata
- { "tags": "cleanup, restoration, persistence, post-engagement, hygiene", "subdomain": "planning", "when_to_use": "create cleanup plan, artifact inventory, persistence removal, post-engagement teardown, restoration plan", "upstream_ref": "Soundwave cleanup template — artifact inventory, persistence removal, restoration plan" }
- description
- Cleanup & restoration plan generator — artifact inventory, persistence removal commands, pre-engagement baseline, post-engagement verification.
- allowed-tools
- Read Write Edit
03 SKILL.md 正文
Cleanup & Restoration Plan Generator
The cleanup plan is the anti-foothold roster — every artifact the kill chain will create must have a concrete removal command and a verifier, or dummy accounts / scheduled tasks / beacons routinely outlive the engagement.
When to Use
- After CONOPS is written (the kill chain phases dictate what artifacts will exist)
- User says "create cleanup plan", "list what we'll leave behind", "post-engagement teardown"
Workflow
Step 1: Map Kill Chain Phases → Expected Artifact Types
For every phase in CONOPS.kill_chain, infer which CleanupArtifact.artifact_type entries will be produced:
| Kill Chain Phase | Likely artifact_types |
|---|---|
| recon | tool (installed scanners), network-rule (firewall whitelist) |
| initial-access | account (test users), file (uploaded payloads), tool (web shells) |
| post-exploit | persistence-mechanism (scheduled-task / service / registry-run), account (created backdoor users), file (dropped binaries) |
| c2 | beacon (C2 implants), network-rule (egress allow), tool (sliver / cobalt-strike payloads) |
| exfiltration | file (staged exfil archives), network-rule (DNS tunneling) |
Step 2: Seed CleanupArtifact entries
For each expected artifact, set:
artifact_type— category abovehost— placeholder (e.g."<initial-access target>") — operations agents replace at run timepath— likely filesystem / registry / account-name locationpersistence_mech— concrete mechanism if applicableremoval_command— idempotent shell or API call to removeverifier_command— zero-exit on successcreated_by_objective— left blank; operations agents fill on creationremoved=False,removed_at=""
Step 3: Pre-engagement Baseline
Set pre_engagement_baseline to whatever snapshot reference the operator gives during the interview (volume ID, AWS AMI, hypervisor snapshot, manual filesystem hash list). If no baseline is available, record that explicitly — it's a critical risk signal for the engagement owner.
Step 4: Completion Criteria
Default schema text covers most engagements. Override only when the engagement specifies different completion semantics (e.g. "leave honeyfile FILE_X in place for blue team training" — note as a cancellation_reason on that artifact later).
Validation Checklist
Before writing plan/cleanup.json:
- [ ] Every CONOPS phase that creates persistence has a matching artifact entry
- [ ] Every artifact has a non-empty
removal_command - [ ] No artifact's
pathreferences an out-of-scope host - [ ]
pre_engagement_baselineis either set or explicitly marked "no baseline available"
Anti-patterns
- Leaving
removal_commandempty — operations agents will skip the artifact entirely - Putting absolute paths from the operator's machine (engagement workspace is
/workspace/<eng>inside the sandbox; cleanup runs on TARGETS not the workspace) - Forgetting C2 beacons — the kill chain's c2 phase is the most common omission
Output
Write to plan/cleanup.json validating against decepticon.core.schemas.CleanupPlan.
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
wpa3-sae
WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.