Repository navigation
Phase-3 alerting lands: pounce now classifies each correlated connection against the trigger rules in TRIGGERS.md, replacing the earlier ✓/? verdict with a type · severity · confidence finding model. Still the zero-FDA MVP (Phases 1–3); still observe-only.
Highlights
- Trigger rules —
⚠alert /?to review /✓expected, led by a one-line verdict:#1capability mismatch — a local-only tool (built-in prior + learned baseline) egressed at all#2destination mismatch — a call connected somewhere it didn't declare (eTLD+1 compare; the declared host's own IPs count as legit)#3cloud-metadata / raw-IP properties#4novel destination — a new registrable domain for a(server, tool), soft during its first-session learning window
- Learned baseline — persisted per-
(server, tool)profile at~/.pounce/profile.json, order-independent, learned onwrapsession close. - Confidence = attribution × naming; low-confidence findings stay in the timeline rather than pushing.
- Dedupe — one finding per
(tool call, destination), shown as×N.
The headline exfil demo now reads at a glance:
⚠ 1 alert — destination mismatch
tools/call fetch {"url":"https://example.com"}
✓ tcp 93.184.216.34:443 declared example.com
⚠ tcp 1.1.1.1:443 declared example.com — connected to 1.1.1.1 (no DNS)
The feature (#5) was adversarially reviewed before merge; 9 issues from that pass were fixed with tests.
Install (macOS)
curl -sSL -o pounce https://github.com/tstefank/pounce/releases/download/v0.4.0/pounce-darwin-arm64
chmod +x pounce && xattr -d com.apple.quarantine pounce 2>/dev/null || true(Use pounce-darwin-amd64 on Intel.) Verify with checksums.txt.
Full changelog: v0.3.1...v0.4.0