Technology moves fast. Context matters. Independent by design ↗

Find your next rabbit hole.

Explore the collection, or type to search.

ExplainerPHP2Shell: the two PHP flaws that put most of the web at riskIn October 2026 two critical memory-safety bugs in PHP itself, CVE-2026-109618 and CVE-2026-109619, leaked before the fix was ready. They let an attacker with no account run code on servers running PHP versions going back to 5.4.ExplainerThe eMudhra key compromise: when a certificate authority’s keys could be guessedIn October 2026 a researcher showed that eight intermediate certificate authority keys belonging to India’s eMudhra were so weak they could be recovered in under a second. Browsers blocked them within hours, and eMudhra quit the global TLS certificate business.ExplainerAI and security: faster bug hunting, faster attacks and new targetsAI models now find serious flaws in core internet software, and attackers use the same tools to exploit them within hours. What October 2026’s run of disclosures shows about the risks, and what defenders can do.ExplainerYahoo closes GeoCities: how the web lost millions of home pagesYahoo bought GeoCities for billions in 1999 and switched it off a decade later. The closure became a turning point for web preservation.ExplainerThe Storm worm: the botnet that started with a weather headlineIn January 2007 an email about deadly storms in Europe spread a Trojan that built one of the largest peer-to-peer botnets of its time.

Press Esc to close

2007 · Security

The Storm worm: the botnet that started with a weather headline

Last reviewed 5 October 2026

In January 2007 an email about deadly storms in Europe spread a Trojan that built one of the largest peer-to-peer botnets of its time.

How it began

In January 2007, as a severe windstorm hit Europe, inboxes filled with messages carrying headlines about storm deaths. The attachment was a Trojan for Windows. The timely subject line gave the malware its name.

Later waves used whatever was topical: e-cards, news alerts, holiday greetings and fake video links. The lures changed constantly, which made simple subject-line filtering ineffective.

Why it was different

Earlier mass-mailing worms were mostly about spreading. Storm was about building a resilient botnet. Infected machines communicated over a peer-to-peer network rather than a single control server, which made it much harder to shut down.

The network was rented out for spam and used for distributed denial-of-service attacks, including against researchers who probed it. Estimates of its size varied enormously, from hundreds of thousands to millions of machines, because a peer-to-peer botnet is hard to count.

Decline

By late 2007 researchers reported that Storm’s active population was shrinking, helped by antivirus updates and Microsoft’s Malicious Software Removal Tool. Its operators were never publicly identified. Its peer-to-peer design and fast-changing lures influenced the botnets that followed.

Sources

  • Wikipedia: Storm Worm
  • Microsoft Malware Protection Center reports on Win32/Nuwar, 2007
  • Academic and vendor analyses of the Storm peer-to-peer botnet, 2007–2008

More on Security