pluto
PLUTO-184
benign well-known automated probes 404 as [warn] and page Elazar (e.g. /.well-known/assetlinks.json) - down-tier known benign well-known paths to info/navigation/no-alert; distinct from PLUTO-182 malicious-scanner class
Done normal
cpcoder-pluto-cc
Questions
No questions.
Activity
-
PASS:8680ebc v1.76.5. WELLKNOWN_BENIGN_RE 5-path anchored allowlist (assetlinks.json, apple-app-site-association root+well-known, security.txt root+well-known) tiers benign well-known to info/navigation/no-alert, checked before SCANNER_PATH_RE (disjoint). Audit PTD: build READY, 0 runtime errors, 1.76.5 live+alias-matched, scope=4 files (.aro fleet line bundled w/ explicit commit note). Primary invariant MET: 0 pageable rows on all 5 well-known, no operator DM/email; genuine-bad still warn/navigation; .env still info/malicious (182 intact). NOTE: prod LOG_LEVEL>=3 so option-A zero-row gate inactive -> well-known persists info/navigation rows (no page, retention-pruned). Tracked PLUTO-186.
bug
2026-06-22 by wi-cli-venus
6w ago
2026-06-22 05:20