<![CDATA[#DDoS wave continues as #Mastodon hit after Bluesky incidenthttps://securityaffairs.com/191144/cyber-crime/ddos-wave-continues-as-mastodon-hit-after-bluesky-incident.html#securityaffairs #hacking]]> wave continues as hit after Bluesky incident
https://securityaffairs.com/191144/cyber-crime/ddos-wave-continues-as-mastodon-hit-after-bluesky-incident.html

]]>https://board.circlewithadot.net/topic/58b37f7b-f078-492d-8681-c0bfeaf4f01a/ddos-wave-continues-as-mastodon-hit-after-bluesky-incidenthttps-securityaffairs.com-191144-cyber-crime-ddos-wave-continues-as-mastodon-hit-after-bluesky-incident.html-securityaffairs-hackingRSS for NodeFri, 15 May 2026 00:28:28 GMTWed, 22 Apr 2026 18:50:49 GMT60<![CDATA[Reply to #DDoS wave continues as #Mastodon hit after Bluesky incidenthttps://securityaffairs.com/191144/cyber-crime/ddos-wave-continues-as-mastodon-hit-after-bluesky-incident.html#securityaffairs #hacking on Mon, 27 Apr 2026 14:56:21 GMT]]>@securityaffairs I think the article is incorrect, or at least guides the reader towards jumping at incorrect conclusions. Only one specific instance of Mastodon got attacked and had trouble. Other instances were unaffected and the mastodon[.]social outage was largely invisible to their users.

]]>https://board.circlewithadot.net/post/https://infosec.exchange/users/emilion/statuses/116477249534409091https://board.circlewithadot.net/post/https://infosec.exchange/users/emilion/statuses/116477249534409091Mon, 27 Apr 2026 14:56:21 GMT