CrowdStrike Threat Research

https://www.crowdstrike.com/blog/category/counter-adversary-operations/

Falcon Counter Adversary Operations / Falcon Intelligence threat reporting. URL CORRECTED 2026-05-08: legacy /blog/category/threat-intel-research/ now 301-redirects to /en-us/blog/category.counter-adversary-operations/, using the redirected URL avoids an unnecessary hop. 2026-05-08 audit: WebFetch returned 5 dated posts latest 2026-05-06 on OverWatch, CORDIAL/SNARKY SPIDER. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → webfetch https://www.crowdstrike.com/blog/category/counter-adversary-operations/ (listing, dates inline) then webfetch each /en-us/blog/<slug>/ article. AVOID: Do NOT use /en-us/blog/category/counter-adversary-operations/, that variant 404s. The stored /blog/category/... URL is the correct listing; individual article URLs DO carry the /en-us/ prefix.. | 2026-07-05 admiralty audit: B, vendor threat-intel lab, original adversary research from own telemetry; live and drillable, no change (active). | 2026-10-04: `extract` returns the crawl date as date: on every post; do not trust it. Use WebFetch on the Counter Adversary Operations listing for the displayed dates. | 2026-10-22 (S3): `extract` on posts works but can return the crawl date instead of the publication date; WebFetch of the listing reads only the first 100,000 characters. | 2026-10-29 (S3): Recipe fix: the working dated discovery path is `python3 tools/fetch_source.py feed https://www.crowdstrike.com/en-us/blog/feed 20` (10 dated items, Oct 8 to Oct 28). The record URL .../blog/category/counter-adversary-operations/ returns 404 to WebFetch; the listing that extract reads is https://www.crowdstrike.com/en-us/blog/category.counter-adversary-operations/ and carries no dates, and extract of a post returns t