TrendNew Politics. Diplomacy. Markets. Tech. What matters.
Tech 6 min read

The Great Unraveling: Why Every Tech Company Is Getting Hacked at Once

From crypto thieves to state-sponsored saboteurs, the threat matrix just collapsed into chaos. Here's what's actually breaking.

The Great Unraveling: Why Every Tech Company Is Getting Hacked at Once

The dominoes started falling in April. Then May. Now they won’t stop.

A North Korean hacking group just stole $290 million from Kelp DAO—the biggest crypto heist of the year. Three days later, Mastodon’s servers got hammered by a DDoS attack. Before that, a US-sanctioned currency exchange lost $15 million to what officials are calling “unfriendly states.” Iran-linked hackers hit critical US infrastructure. Russia’s military turned thousands of consumer routers into botnet nodes. Broadcom’s reputation tanked so badly that thousands of companies are ripping out VMware and replacing it with competitors.

And that’s just the warm-up act.

The reason I’m writing this isn’t because attacks happen—they always have. It’s that they’re happening everywhere, all at once, across completely different attack surfaces, using different tools, different motivations, and different victim profiles. That’s not a trend. That’s a system failure.

A close-up view of pink yarn and knitting needles on a wooden table, ideal for crafts and DIY themes. Photo by Eva Bronzini / Pexels

The Threat Matrix Just Got Denser

Let me be clear about what’s changed. For years, cybersecurity worked like a stack of silos. State actors went after critical infrastructure and defense contractors. Cybercriminals went after banks and payment systems. Script kiddies went after whatever website they could exploit with a pre-built tool. Different attackers, different targets, different damage models.

That’s over.

North Korea’s still stealing crypto. But they’re also working in parallel with Iran-linked groups hitting power grids and water treatment facilities. Russia’s military isn’t just targeting Ukraine anymore—they’re conscripting consumer routers into botnet infrastructure for domestic operations. Meanwhile, the NSA is caught in a weird spot where they’re reportedly using Anthropic’s restricted Mythos AI model despite Pentagon tensions with the company. Even decentralized social networks built explicitly to resist censorship—Bluesky and Mastodon—are taking DDoS fire meant to disable them, not infiltrate them.

The geometry of the threat is breaking the old playbook.

Here’s my honest read: we’re watching what happens when the barrier between attack sophistication and availability collapses. A decade ago, pulling off a $290 million crypto theft required months of prep, zero-day exploits, and operational security that would make a Cold War spy handler jealous. Today, North Korea’s doing it. That’s not because they got smarter. It’s because crypto’s security model is fundamentally broken against state-level attackers, and they know it.

The router hack is worse, actually. Thousands of consumer routers compromised by Russia’s military. These aren’t enterprise-grade devices with hardened firmware. These are the TP-Links and Netgears sitting in people’s homes. The fact that Russia’s military cares enough to commandeer them suggests they’re using them for something beyond simple botnet capacity—probably command-and-control infrastructure, signal relay, or reconnaissance staging points. Which means your mom’s WiFi router is now part of the geopolitical attack surface.

Close-up of hands holding a smartphone displaying 'Announcing Grok 3' on a dark background. Photo by UMA media / Pexels

Why Now? Three Overlapping Reasons.

One: The crypto model broke and nobody fixed it. Blockchain security assumes that decentralization makes you safe. It doesn’t. It makes you auditable. When a state actor targets a yield farming protocol like Kelp DAO, they don’t care about the blockchain’s integrity. They care about the keys. And because crypto protocols are built on the assumption that users will hold their own keys responsibly, there’s no failsafe. A $290 million theft is just math playing out. The system worked exactly as designed—it just turned out the design was a disaster.

Two: Critical infrastructure is still running 20-year-old security architectures. Iran-linked attackers are disrupting US critical infrastructure sites. The fact that we’re reading about it in headlines means they’re successful enough that someone has to publicly acknowledge it. These systems were built in the 1990s and 2000s when the threat model was “keep the Russians out.” Now the threat model is “keep out everyone, forever, while staying operational.” Those are incompatible goals when your infrastructure is built on the assumption that a firewall and a VPN are sufficient.

Three: Quantum’s coming and everyone knows it. Recent advances are pushing Big Tech closer to the “Q-Day danger zone”—the moment when quantum computers can crack current encryption standards. This is driving urgency across the entire security stack. The NSA using Anthropic’s restricted Mythos model makes sense in that context. If you’re a US intelligence agency and quantum’s on the horizon, you need to understand what AI can do in a post-encryption world. Mythos is restricted for a reason. The NSA probably wants to know what it can and can’t do before adversaries figure it out first.

This isn’t paranoia. This is institutional survival logic kicking in.

The Mastodon/Bluesky Pattern Tells You Something

Both platforms got DDoS’d within a week of each other. Both are decentralized social networks designed to resist exactly this kind of attack. Both failed to resist it.

That should bother you more than it does.

A DDoS attack is the dumbest possible way to disrupt a system. You’re just sending it too much traffic. Modern infrastructure can usually handle this with basic rate-limiting, geographic distribution, and cloud provider protection. The fact that both Mastodon and Bluesky went down suggests either: (A) their infrastructure isn’t as distributed as advertised, (B) their cloud providers aren’t filtering as aggressively as they should, or (C) someone had specific intelligence about their architecture and exploited it surgically.

My read is (A) and (B) together. Mastodon’s flagship server is, well, still a server—singular. It’s faster to attack a known single point of failure than to try to take down a truly distributed network. And if you’re throwing enough traffic at it, even Cloudflare’s expensive DDoS mitigation gets expensive fast. You don’t have to win. You just have to make it cost more than the platform can afford.

This is asymmetric warfare against infrastructure that was supposed to be asymmetry-proof. That’s a design loss, not an attack win.

The Blue Origin Wildcard

The FAA ordered an investigation into Blue Origin’s New Glenn rocket failure. The upper stage apparently didn’t perform. New Glenn’s now grounded.

This matters for exactly one reason: space infrastructure is about to become a critical attack surface. As more companies launch mega-constellations—Starlink’s already got thousands of satellites up—the intersection of space, communications, and critical infrastructure becomes a target. If a nation-state can compromise satellite ground stations, they can compromise the comms backbone that every other system relies on.

Blue Origin’s probably just had an engineering failure. But if I’m at the NSA or China’s equivalent, I’m watching this timeline. Space is the next battlefield, and right now the security models are still theoretical.

What I’m Watching

  • Quantum timeline acceleration. Watch for public announcements from Google, IBM, or Chinese labs about quantum error correction breakthroughs. When someone credibly demonstrates 1,000+ stable qubits (we’re at hundreds right now), the cryptography migration will go from five-year plan to emergency sprint. Q3 2024 is my threshold—any major leap now means Q-Day moves from 2030s to late 2020s.

  • Critical infrastructure attribution speed. Track how long the US government takes to formally attribute the recent infrastructure attacks. If it’s under 30 days, someone in intelligence has a high-confidence trail. If it takes months, we’re dealing with more sophisticated operational security from Iran’s side. Speed of attribution tells you how vulnerable we actually are.

  • Mastodon’s infrastructure fix. Did they actually distribute their flagship server or just add more DDoS filtering? If they announce real federation of their core infrastructure in the next quarter, the platform survives long-term. If they just threw it behind Cloudflare and called it a win, they proved that decentralization is harder than advertised.

  • NSA/Anthropic tension boiling over. Watch for Congressional questioning about Mythos access. The Pentagon and NSA don’t usually get called out for using restricted AI in public. If this becomes a hearing, someone in government decided the oversight issue was worth the political heat. That’s a signal that the AI-security relationship just broke into the public eye for real.

The system’s not broken yet. But the seams are showing.