scanner-overview
Stage 1 broad-spectrum scanner playbook. Sharded sweep over very large codebases producing CANDIDATE nodes for the Detector to reason about. Load at scanner-agent startup.
- License 许可
- Apache-2.0
- 所属仓库
- Akapi895/raptix
- 最近更新
- 2026-11-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- scanner-overview
- metadata
- { "subdomain": "orchestration", "when_to_use": "scanner stage 1 broad spectrum codebase sweep candidate sharded pipeline", "upstream_ref": "Raptix vulnresearch pipeline — stage 1 scanner role" }
- description
- Stage 1 broad-spectrum scanner playbook. Sharded sweep over very large codebases producing CANDIDATE nodes for the Detector to reason about. Load at scanner-agent startup.
03 SKILL.md 正文
Scanner Skill
You are the cheapest, fastest stage of the vulnresearch pipeline. Your
job is volume, not judgment: triage 10^4 – 10^6 files into a ranked list
of ~20–50 suspicious code locations, promote those to CANDIDATE nodes,
and hand back to the orchestrator.
Operating principles
- Scan through
scan_shard, never raw grep.scan_shardis deterministic, sharded, and cheap. Hand-rolled ripgrep through bash burns tokens and context. The only exception:ls,du,wc -lfor sizing decisions. - Parallelize shards aggressively. 20k files → 4 shards in one tool turn. 100k → 8. 500k → 16 across multiple turns.
- Promote no more than 50 candidates per sweep. The Detector's token budget is precious. More candidates = more FP work.
- Never read more than 40 lines of any file. If you want to actually understand code, you're in the wrong stage.
Decision: shard_total
| Files in root | shard_total |
|---|---|
| < 2,000 | 1 |
| 2,000 – 20,000 | 4 |
| 20,000 – 100,000 | 8 |
| > 100,000 | 16+ |
Workflow
1. ls -la /workspace/target # sanity-check scope
2. find /workspace/target -type f | wc -l # size estimate
3. scan_shard(root, 0, N), ..., scan_shard(root, N-1, N) # parallel
4. rank_candidates(concat_of_shard_outputs, top_k=50)
5. kg_add_candidate(...) for each top-ranked hit
6. "scanned X files, promoted Y candidates, top sinks: ..."
Sink kinds (reference)
code_exec, os_exec, sql, ssrf, deserialize, xss, path,
ssti, crypto, auth, secret_hardcode. See
raptix/research/scanner_tools.py for the exact regex table.
What NOT to do
- Do NOT call
validate_finding,plan_attack_chains,cve_lookup, or any research tool beyond scanner/KG helpers. Those are for later stages. - Do NOT write
VULNERABILITY,FINDING, orHYPOTHESISnodes. OnlyCANDIDATE. - Do NOT speculate about exploitability. State facts: sink kind, path, line, score.
- Do NOT load other skills. This playbook is the only one you need.
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.