<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Botnet-Disruption on CuraSec</title><link>https://curasec.metacog.co.kr/tags/botnet-disruption/</link><description>Recent content in Botnet-Disruption on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 16:34:51 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/botnet-disruption/index.xml" rel="self" type="application/rss+xml"/><item><title>ASD Disrupts Amadey Malware Backend, Severs 180K Infected Hosts</title><link>https://curasec.metacog.co.kr/insights/2026-10-27-australia-gets-into-amadey-malware-backend-cuts-off-access-t/</link><pubDate>Tue, 27 Oct 2026 16:34:51 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-27-australia-gets-into-amadey-malware-backend-cuts-off-access-t/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> No patch or config action applies here; note that C2 disruption does not clean infected hosts, so Amadey loaders may still be dormant on endpoints even without callbacks.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> The severed C2 means infections persist without active exfiltration — sweep your estate for Amadey indicators using existing EDR/YARA signatures now, before a new C2 spins up and re-acquires those hosts.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A notable government-led botnet disruption at scale; no executive action required unless an internal sweep reveals organizational endpoints were among the 180,000 compromised hosts.&lt;/li>
&lt;/ul></description></item></channel></rss>