Glassworm botnet disrupted after resilient C2 infrastructure takedown

What happened

Recent reporting highlighted glassworm botnet disrupted after resilient c2 infrastructure takedown. The Glassworm botnet targeting developers in software supply-chain attacks has been disrupted after researchers took down its resilient command-and-control infrastructure relying on Solana blockchain transactions and the BitTorrent DHT network. ​In a coordinated operation conducted yesterday, CrowdStrike, Google, and The Shadowserver Foundation cut off the botnet operators’ access to four distinct command-and-control (C2) channels designed to resist conventional disruption efforts.

Why it matters

This matters because it has practical implications for defensive prioritisation, exposure management, or incident response rather than sitting as abstract security commentary. It also helps frame how defenders should think about attacker adaptation and recurring tradecraft rather than single incidents in isolation.

Assessment

The strongest signal here is the tradecraft pattern and what it says about attacker adaptation, not just the single campaign or disclosure. In practice, that means operators should read this as a broader signal over noise item rather than a narrow one-off.

Recommended actions

• Review whether the issue, advisory, or attack pattern is relevant to your environment, suppliers, or exposed systems
• Patch, harden, or validate logging and monitoring coverage where applicable
• Map the observed activity to existing detections and threat-hunting hypotheses instead of tracking it only as narrative reporting
• Monitor follow-on reporting or primary-source updates for scope expansion, implementation guidance, or stronger enforcement signals

Further reading

• Primary source
• Source profile: Reporting