Every sailor learns it eventually, usually at two in the morning with a flashlight in his teeth. Boats don’t sink because of the storm. They sink because of the hose clamp somebody meant to replace last spring. The storm just collects the bill. Don’t ask me about the Fischer Panda of doom and the 50 cent hoseclam that damn near sunk me.
So here’s the question people keep asking after Microsoft, the FAA and Chase all fell over inside five days. Are there more hacks, or just more headlines? More hacks. A hell of a lot more. And the headlines are lying to you by omission, because the news hit its ceiling a long time ago.
My test is simple. Count what the gangs post, not what the networks air.
The Count
In September and October of 2023, NCC Group counted 855 victims on ransomware leak sites. The same two months ran 893 in 2024 and 1,015 in 2025. This year September alone hit 821. NCC hasn’t published October yet, but the trackers that have put it between 953 and 1,178. That’s somewhere between 1,770 and 2,000 claimed victims in two months. Measured by what the bastards brag about, extortion has roughly doubled.
You didn’t hear about most of them, and that’s no accident. A newsroom runs only so many breach stories a week, and the victim list has gone downmarket. Black Kite found companies with more than $100 million in revenue fell from 13.9% to 9.5% of victims with known revenue in the year ending March 2026. Sophos found median ransom demands down 65% over two years. The heist business turned into a dollar store. A regional machine shop on a leak site never trends, so coverage looks flat while the count doubles.
The Later Ledger
Now the outages, and the excuse everybody reached for. Microsoft called its nearly daylong Microsoft 365 failure “a technical issue not related to cyber or AI / agents” and traced it to an earlier network capacity upgrade that surfaced after a later change. The FAA’s investigation points to a site where its contractor was deploying a new router, and the instability hit radar and radio feeds at 17 of its 22 en route centers. Chase blamed a software bug, and a source told CNN an update to its own systems set it off. Nobody hacked anybody. No model went rogue. As far as the companies have said, each failure traces back to a change in old plumbing, and each spread faster than people could contain it.
So it was just a bad patch? That’s the stupidest excuse in the building, because it lets leadership walk. The patch is only where the bill came due. The bill itself lives on the “Later Ledger“.
Every company keeps two sets of books. There’s the one the auditors see, and there’s the Later Ledger. The Later Ledger is where the router that should have been replaced goes, along with the help desk seat that got cut, the upgrade that slipped three quarters, and every “we’ll get to it later” anyone ever said in a budget meeting. Companies chase revenue, book the performance gains early, and park the maintenance that keeps those systems standing on the Later Ledger, payable in a quarter that never arrives.
I didn’t make this up. McKinsey describes tech debt as the off balance sheet accumulation of all the technology work a company needs to do in the future, and the CIOs it surveyed put that debt at 20 to 40 percent of the value of their technology before depreciation. Twenty to forty percent. That is a material risk, and it sits on almost nobody’s books. Shareholders don’t see it. Boards don’t see it. The only people who see it are the ones on call at 2 a.m., and we’re firing them.
Government runs the same con with more zeros. Federal agencies spend more than $100 billion a year on IT and report about 80 percent of it going to operating and maintaining what they already have. GAO notes the FAA has been trying to modernize air traffic control since the 1980s with limited results. Washington’s Later Ledger never gets paid. It gets handed from one administration to the next like a hot potato with a security clearance. Sydney Liles made this argument about roads and bridges on this site years ago: maintenance goes undone while enormous sums keep old infrastructure in a mediocre state. Swap the bridges for routers and you don’t have to change a word. By the way she is twenty times smarter than me, and a bazillion times better looking in a skirt and high heels. If you think that is sexist you’ve never met her.
IT Pays First
IT operations is further behind, and the numbers show it. Verizon’s 2026 DBIR found the median time to fully patch a vulnerability grew from 32 days to 43, and organizations fully remediated only 26% of the vulnerabilities on CISA’s known exploited list, down from 38%. Exploitation is now the most common way breaches start, at 31%. Defenders got slower in the same year attackers got faster, and nobody upstairs blinked.
Tap tap tap… is anybody listenting? Is this thing on?
The Later Ledger runs deeper than patches. Lansweeper’s device data shows 18.7% of Windows devices on an operating system past end of support, with another 22.2% on versions due to reach it within six months. Windows 7 still accounts for 1.65% of Windows desktop web traffic, more than six years after its support ended. Windows 7, for God’s sake. In government the gap is measured in decades. Of the ten critical federal legacy systems GAO flagged in 2019, only three had been modernized by early 2025, and the seven left range from 23 to 59 years old. GAO also rated more than 75% of the FAA’s 138 air traffic control systems unsustainable or potentially unsustainable, and the FAA blamed its November 13 instability on that legacy network.
Fewer Hands
The people on the other side of that curve did not double. ISC2’s 2025 workforce study found 24% of security teams reporting layoffs and 36% reporting budget cuts, and it called that leveling off, which is a polite way of saying the numbers stopped getting worse. IANS found 2026 security budgets up 5% on average, with 45% of organizations flat and 10% shrinking. Flat staffing against doubled tempo is a staff cut. It just never shows up as one in the HR system.
The federal backstop shrank outright. CISA went from roughly 3,300 employees to about 2,200 and now talks about hiring 330 back. In the ISC2 study, 72% of respondents said cutting security staff raises the odds of a breach, and they are the people who would know.
IT gets it worse. Futurum’s 2026 CIO survey found that among 327 organizations making AI driven IT headcount reductions, 60% are cutting help desk and support. WTF? Barracuda, citing an ETR survey from the same Futurum group, puts IT operations and infrastructure at 53%. Those are the hands that patch servers and fix what breaks at 2 a.m. Take them away and the backlog doesn’t get automated. It just gets older, and the Later Ledger gets longer.
The Questions I Keep Getting
Isn’t this just the news running more stories?
The record says the opposite. Of the 1,020 ransomware attacks Comparitech logged in October, the victims confirmed 81. Eighty one. The rest never became stories because nobody admitted a goddamn thing. The notices that do go out say less every year. In 2020 almost every breach notice named a root cause, and by 2025 only 30% did. Researchers at the University of Tulsa found substantial gaps between what companies disclose to regulators and what reaches the news. Coverage hit its ceiling a while ago, and the count kept climbing underneath it like water in a bilge nobody’s checking.
Isn’t the rush to AI what’s breaking everything?
No. Look at what actually broke: a network change, a router job and an update to Chase’s own systems. AI isn’t moving fast enough to be the main problem. Census survey data shows about 40% of firms with 250 or more employees using AI in some business function as of October, but use is not deployment. In an Insight Global survey this spring, 89% of business leaders said an AI initiative had stalled at their company, and Writer found 79% of organizations struggling to adopt AI, a double digit jump from 2025. Resilience isn’t a fucking word board rooms give a damn about. Moarrrr proffffittt. Says the zombie MBAs
Fine. Won’t AI cover for the people we cut?
The money is betting on it. In the IANS survey, 69% of CISOs named AI for security as the top place for new dollars. Much of it buys pilots that sit on the same networks that fell over this month. Meanwhile the other side already figured it out. On October 29, attackers moved about $6.3 billion out of Binance’s hot wallets. Binance says the chain began months earlier, when an engineer downloaded a tampered installer for an AI coding tool, and that the attackers later used an internal AI tool to take over two engineers’ machines. They finished by deploying a container with stolen credentials and using it to reach the wallet signing service. Automation is an accelerant, and it doesn’t care which side lit the match.
The Hose Clamp
So the problem isn’t the shiny new thing. Everything underneath it is rotten, and leadership put it there one entry on the Later Ledger at a time. The bad guys are accelerating. The technology keeps shifting under everyone’s feet. The people who protect it are getting cut while the work piles higher, and every one of them is one less set of eyes on a change window or a strange login from an engineer’s laptop. The hose clamp is going, and everybody on the boat can see it. What the fuck else did anyone think would happen?
Sources are listed on the first tab.