hn.today

Yandex outage: data shows that instead of going dark, malicious bots moved

blog.cloudflare.com239 points76 comments
Screenshot of Yandex outage: data shows that instead of going dark, malicious bots moved

Commenters debated Cloudflare’s analysis of the Yandex outage and whether Russian troll activity was actually disrupted. Some cited Cloudflare’s conclusion that strikes didn’t knock social-media manipulation offline and said the viral narrative that “trolls went dark” was wrong, noting Cloudflare’s point that ASN volume is an unreliable proxy for bot behavior. Others pushed back, saying people observed quieter social feeds and that bot-driven posting may have temporarily declined because operations relied on Yandex-hosted crawlers or news-scraping infrastructure. Several commenters clarified that Cloudflare was mainly measuring web-scraping crawlers rather than the social-media posting bots many readers had in mind, and some faulted early Cloudflare tweets and press coverage for seeding misleading memes.

Opinion split on how the malicious automation adapted and what defenders should do. Some argued bots simply shifted providers or used residential/mobile proxies and intermediaries (names like Radist and Selectel were mentioned), making ASN-blocking ineffective; others pointed to the centralization of Russian cloud providers as a strategic vulnerability with real service impacts. Practical advice ranged from treating behavior and JA3/JA4 fingerprinting and WAF rules as primary defenses to ad-hoc nginx rules and moderation queues. A number of commenters emphasized that well-run bot operations obfuscate origin, so mitigation requires application-layer detection rather than blunt network-level blocks.

Read on blog.cloudflare.com76 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.