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

The Infrastructure Meltdown Nobody's Talking About

Your router is compromised, your GPU isn't yours anymore, and the cloud platforms you depend on are hemorrhaging customers. Here's what's actually breaking.

The Infrastructure Meltdown Nobody's Talking About

We’re living through a slow-motion infrastructure collapse that nobody wants to call by its name.

Not because it’s subtle. It’s not. The symptoms are everywhere: Russian military hackers have compromised thousands of consumer routers. New attacks on Nvidia GPUs give attackers complete machine control. Iran-linked groups are disrupting US critical infrastructure. Broadcom’s handling of VMware is triggering mass customer exodus. And somehow we’re still treating these as separate news cycles instead of what they actually are—data points in a single catastrophic story about who controls the systems we’ve built our economy on.

Let me be direct: this isn’t a security problem anymore. It’s a governance problem.

Site of roadway under concrete bridge construction with heavy equipment on dirty ground Photo by Maarten van den Heuvel / Pexels

The Router Thing Is Worse Than You Think

Russia’s military hacking thousands of consumer routers sounds like a headline. It’s actually a symptom. Those devices—the ones sitting in millions of homes and offices—aren’t being targeted because they’re valuable endpoints. They’re being targeted because they’re invisible infrastructure. They’re the unpatchable, rarely-monitored gateway between you and everything else.

Most people don’t know what version of firmware their router runs. They’ve never updated it. The manufacturer stopped supporting it three years ago. It sits there, blinking, completely compromised, and nobody notices because routers don’t scream when they’re pwned.

This matters because routers aren’t separate from your critical infrastructure. They’re part of it. A hacked router becomes a pivot point for lateral movement into corporate networks. It becomes a staging ground for distributed denial-of-service attacks. It becomes a surveillance post.

The Iran-linked operations hitting US critical infrastructure sites? They probably didn’t start with some sophisticated zero-day. They probably started with someone plugging in a device from a compromised supply chain. Or a router that nobody patched. The difference between a consumer annoyance and a blackout is just a matter of what’s on the other end of that compromised gateway.

The GPU Vulnerability Changes Everything

Then there’s Rowhammer on Nvidia GPUs. Read that headline again: “complete control of machines running Nvidia GPUs.”

GPUs aren’t just graphics processors anymore. They’re doing the heavy lifting for AI inference, machine learning, financial modeling, scientific computing. They’re in your cloud infrastructure. They’re in Tesla factories. They’re running the models that increasingly make decisions about money and safety.

Rowhammer—the technique where precisely-timed memory access hammers adjacent cells to flip bits—has been around since 2014. But GPUs present a specific problem: they’re designed for maximum throughput, which means minimal memory protection. You’re trading security for speed because that’s what you need for 10,000 parallel calculations per second.

Now someone’s figured out how to use that architectural tradeoff to get complete machine control.

My read is this hits different than previous GPU vulnerabilities. This isn’t a side-channel leak or a timing attack. This is full compromise. And unlike consumer routers, organizations actually care about their GPU fleets because they’re expensive and they know what they do. So this will get patched faster.

But the window—the moment where this is exploitable and unknown—probably means it’s already been used in the wild. That’s always how this works. The public disclosure comes months after the sophisticated attackers stopped using it.

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

The Broadcom-VMware Exodus Is About Trust

Broadcom buying VMware was supposed to be a story about consolidation and synergy. What it’s actually become is a referendum on corporate ownership.

When you run thousands of VMs on VMware infrastructure, you’re betting everything on the company that owns it understanding your incentives matter. Broadcom’s post-acquisition moves—licensing changes, price increases, what sounds like a shift toward extracting more money from existing customers—have apparently made that bet look terrible.

“Negative views of Broadcom driving thousands of VMware migrations” isn’t just a market story. It’s a warning sign about what happens when a platform becomes seen as extractive rather than enabling.

Here’s the thing about infrastructure software: once people decide to leave, the exodus accelerates. The first migration is painful. The second one creates tooling and knowledge. By the fifth, you’ve got proven playbooks. By the twentieth, you’ve got a community doing it. Broadcom probably has 18 months before this becomes a rout.

The irony is Broadcom didn’t necessarily do anything wrong by trying to make more money. They did something wrong by making it so obvious that the customer wasn’t part of the equation anymore.

OpenAI’s Weird Week

In the span of 72 hours, OpenAI announced a $100/month Pro plan (jumping from the previous $20/month tier straight to $200) while also getting investigated by Florida’s AG for alleged harm to minors and a possible connection to a mass shooting.

Let’s separate these. The pricing move makes sense: power users exist, they’ll pay, and the gap between $20 and $200 was always leaving money on the table. But $100/month as an intermediate tier? That’s not just pricing strategy. That’s signaling that this is now a professional-grade product for serious use cases.

The investigation is trickier. I’m genuinely uncertain whether there’s there there. The allegations sound hyperbolic—investigating a software company for a shooting requires a pretty specific causal chain. But it also signals something real: as AI tools become more ubiquitous, liability questions that seemed theoretical are becoming actual legal questions that attorneys general are willing to ask.

This probably doesn’t crater OpenAI. But it does mean they can’t operate in the assumption that they’re just a software company anymore. They’re increasingly a public institution dealing with public harm frameworks.

The Volkswagen Thing Is Weirdly Relevant

VW dropping the ID.4 electric SUV to go all-in on gas versions at their US factory has nothing to do with cybersecurity and everything to do with confidence.

A company that built out manufacturing for electric vehicles, then reverses that bet so completely that they’re shelving the EV line entirely, is a company that’s made a judgment call about near-term market reality. They looked at demand, production costs, consumer preferences, and decided the safe bet was backwards.

But here’s the connection: infrastructure choices are confidence bets. When Broadcom inherits VMware, they’re making a confidence bet that extraction strategies work. When OpenAI prices at $100/month, they’re betting on a professional tier. When Russia’s military gets comfortable hacking US routers, they’re making a confidence bet about consequences.

Sometimes those bets are wrong. And when they are, the correction is violent.

Glowing digital globe display at night in Dubai Expo, showcasing illuminated continents. Photo by Denys Gromov / Pexels

What Actually Worries Me

I think we’re in a period where infrastructure—the boring stuff nobody wants to think about—is simultaneously becoming less trustworthy and more critical. The attacks are getting better. The platforms are getting more extractive. The software supply chains are getting more tangled.

The EFF leaving X is a small thing. But it’s a sign that even institutions focused on open internet principles are deciding that certain platforms are no longer worth participating in. When that happens at scale, infrastructure fragments. And fragmented infrastructure is less resilient.

Here’s what I’d bet on: by Q3 2024, we’ll see the first major incident where a Rowhammer attack on GPUs causes actual business interruption that gets public attribution. Not a theoretical proof-of-concept. A real outage. That’s when the GPU security question becomes something CISOs have to brief boards about, and that’s when patches actually force architectural choices.

The VMware exodus will accelerate through 2024 and either Broadcom will reverse course or they’ll fully accept they’re harvesting a legacy business rather than growing a platform. There’s no middle ground in infrastructure plays.

And the router situation will stay terrible because consumer devices don’t have business cases for security theater. They’ll keep getting compromised. The question is just whether the attacks stay targeted at corporate infrastructure or whether we see them used for actual consumer harm at scale.

What I’m Watching

  • GPU patching velocity: How long between now and when Nvidia releases Rowhammer mitigations, and whether they require architectural changes or just firmware updates. Architectural changes mean your 2-year-old GPU might not get fixed.

  • VMware customer attrition rate: Specific threshold—if more than 15% of mid-market VMware customers migrate off in the next 18 months, it signals irreversible momentum. We’ll know by Q4 2024.

  • Critical infrastructure incidents with clear attribution: Whether the next power grid or industrial control system compromise gets traced back to router-based initial access. One confirmed attribution changes how seriously enterprise security takes consumer device security.

  • OpenAI’s legal calendar: Specifically, whether the Florida investigation leads to actual charges or settlement, and whether other states follow. That determines whether AI companies operate under liability frameworks or not.