CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

GreyNoise Labs

greynoise · B · active

https://www.greynoise.io/blog

vulnsresearchlang: enfetch failures: 0quiet periods: 1last fetch: 2026-09-30

Mass-scanning and opportunistic-exploitation telemetry. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → webfetch (listing) then webfetch per-article URL for body. https://www.greynoise.io/blog lists dated posts; drill into /blog/{slug}.. AVOID: Listing dates can be slightly out of order (a research post dated April surfaced above June ops posts), sort by date, don't trust top-of-page ordering.. | 2026-07-05 admiralty audit: B, independent scan-telemetry research lab, first-hand data; live, keep active. Sort by date (listing top-of-page ordering is unreliable). | 2026-09-13 quality audit (G3 broken-recipe duty, closing 2026-09-06 recommendation 3): RE-CONFIRMED WORKING (the 2026-09-09 fire recorded it as a 'stale blog'). `python3 tools/fetch_source.py extract https://www.greynoise.io/blog` returns current posts. Same caveat as socradar: page-level date metadata is unreliable, so drill per-article for the real publication date. fetch_method webfetch -> bridge. | 2026-10-18 (S1): `extract` of the listing returns the wrong content (one article body or navigation only); `url --direct` raw HTML is the working listing recipe. | 2026-10-22 (S1): confirmed: `url --direct <listing>` plus a regex on href="/blog/<slug>" enumerates posts; `extract <post URL>` dates are reliable.

Cited in 5 entries

Citation cadence

Citation days per ISO week (9 weeks of coverage span, total 5).