VenariX

https://venarix.com/blog

Added 2026-08-04 as the ONE candidate source of this run. Threat-intelligence research blog; surfaced as the primary for the ExfilSquad access-path analysis cited by the 2026-08-04 PNLD entry, first-hand review of leak samples from 11 of 15 claimed victims, identification of the Microsoft Power Pages / Dataverse Anonymous-Users misconfiguration class, and independent live reproduction of unauthenticated Dataverse record retrieval from a public municipal portal. No tracked source covered that finding. FETCH → `python3 tools/fetch_source.py url <article-url>` returned HTTP 200 with the full body (verified this run). Astro-built site; per-post dates render on the article page. Candidate; promote to active after 3 contributing runs. | 2026-08-15: listing is a client-filtered single-page app with no per-post dates in the served HTML; needs an RSS or API recipe before it can be rotated reliably. | 2026-08-17: unreachable again, direct transport refused and the jina reader pool returned HTTP 402 on every rotating key, so the documented ladder had no last rung. Transport blocking plus an exhausted reader quota; NOT demoted. | 2026-08-19: reachable again; the recorded /blog 404 was a path problem, not content death; the per-article path under /blog/<slug> serves a full server-rendered body to the direct bridge. Carried this run's Metabase downstream-victim tracker. | 2026-08-23: bridge `url` returns HTTP 200 with the full body, resolving the 3-run failing streak, BUT the rendered listing exposes post slugs with no per-article publication dates, so in-window recency cannot be established from the listing alone. Next fire: drill 2-3 candidate slugs directly for dates rather than re-probing the listing.