• Everyone complains about AI-generated junk.
• But decades of sloppy human-written software may be a much bigger problem.
• This week's "Black October" freakout was caused by human slop, not AI.

The internet has a slop problem. And for once, we can't blame AI.

Most of us spend hours online every day without thinking much about the software holding everything together. We assume somebody, somewhere, has made sure it all works properly.

So it probably came as a shock this week to discover just how vulnerable some of that software is.

The cybersecurity freakout dubbed "Black October" has inspired warnings about AI-powered hackers, digital catastrophe, and even advice to stockpile cash and canned food.

At first glance, AI looks like the villain. But this is largely a human-made mess.

Here's the problem.

The internet runs on decades of software, some of it containing security weaknesses that have been overlooked, tolerated, or simply left unfixed.

For years, that was a manageable gamble. Fixing software takes time and money. Exploiting obscure weaknesses often required considerable expertise. Companies could convince themselves that the risk wasn't worth worrying about.

AI is changing that calculation. Someone who once needed years of training to hunt for weaknesses can now get help from an AI model. These tools can also examine software at speeds that humans can't match.

Suddenly, all those problems we've been ignoring look more urgent.

"Over the last 10 years the risk acceptance process has morphed from a way to accept risks to enable the business, to a way to justify never fixing security issues," Joel de la Garza and Zane Lackey, partners at a16z, wrote on Friday.

That's quite an indictment. The result is a recent surge in published vulnerabilities.

This looks like AI is creating new security problems. But it's actually AI exposing weaknesses that humans left behind.

Slop irony

The irony is delicious. We've spent the past couple of years complaining about "AI slop." Turns out human slop can be pretty consequential, too.

"The funny thing is everyone was saying AI slop code will cause a cyber crisis but it's actually all the old human slop causing it and the AI is just cleaning it up," software engineer Ben Kaufman wrote on X on Thursday.

"Humans have been the ones writing and reviewing each other's code for decades," tech founder Anant Jain wrote on X. "If we're being intellectually honest and holding ourselves to the same bar we hold AI to, we'd have to admit that we haven't been all that good at it either."

Humans are sloppy

Anyone who's worked with other humans for a decade or two knows exactly how this happens.

It's Friday afternoon. You've almost finished a project. You could spend another few hours making it perfect, or declare it 90% done and head off to that dinner party. We've all been there.

AI agents don't have dinner parties. They don't get tired on Friday afternoons. They can keep searching, testing, and trying again. That persistence is now colliding with an internet built by busy, imperfect humans who often settled for "good enough for now."

A tragedy of the commons

There's another wrinkle here, though, and it's an important one.

Much of the software underpinning the internet is freely available for anyone to use. Some of it is maintained by volunteers or small groups of experts, even as enormous technology companies depend on it.

In 2020, the cartoonist Randall Munroe captured this absurdity in an xkcd comic. Modern digital infrastructure still rests precariously on tiny foundations.

It's funny because it's uncomfortably close to reality. Take the specific PHP problems from this week. These flaws have existed for years, and the PHP Foundation acknowledges that limited resources and disagreements over fixes contributed to delays in fixing them.

Tom Occhino, chief product officer at Vercel, brought up Munroe's cartoon during my recent interview with him.

He explained that AI is finding weaknesses even in software that the industry has treated as dependable for decades.

This is partly a version of the tragedy of the commons: Everyone benefits from a shared resource, but no one has sufficient incentive to take responsibility for maintaining it.

And let's be clear: The volunteers keeping essential software running aren't the villains here. The companies benefiting from their work have a much greater responsibility.

Occhino thinks AI could help solve the problem it is exposing.

He described an idea being discussed at Vercel: Create a foundation or coalition that funds efforts to identify vulnerable software and replace it with safer alternatives.

"We need a consortium. We need a coalition," he told me.

He suggested companies could contribute computing resources and AI tools to the effort. Nothing has been formally announced, but the idea is compelling.

Indeed, OpenAI's Patch the Planet effort is an example of what's possible.

Rather than simply using AI to create more software, the industry could use it to repair what already exists.

Occhino put it nicely: Companies need to spend less time chasing new ideas and more time asking how to make existing systems "just work really, really well."

That's a better response than panicking about the imminent collapse of the internet.

AI didn't create decades of neglected software. We did. Perhaps it's time to clean up our own slop.

Sign up for the AI Insider newsletter here. Reach out to me via email at abarr@businessinsider.com

• PHP, the open-source computer programming language, had two major vulnerabilities exposed.
• Yonaton Keller woke on Wednesday to panicked messages about the two PHP vulnerabilities.
• He shares three steps you can take to protect your website.

This as-told-to essay is based on a conversation with Yonaton Keller, a 46-year-old product manager at Zafran Security, based in Tel Aviv. His words have been edited for length and clarity.

When I woke up at 6:30 a.m. on Wednesday, I had multiple messages from around 4:45 a.m. alerting me that two vulnerabilities in the PHP programming language had been disclosed.

I immediately understood that this was a very serious situation.

Websites run different versions of PHP, and it's estimated that around 70% of websites worldwide use it. This isn't the first time PHP vulnerabilities have been found, but these ones require essentially no authentication on the attacker's part.

It's a very tricky situation. If it were a year and a half ago, nobody would have really responded to this so urgently. But this might be one of the first major incidents of its kind in this AI era, and the cycle of how attackers operate and how we typically respond is broken.

AI enhances detection and response times, but it also means that any limited-technical person could exploit these vulnerabilities within minutes.

My team was very concerned and had to act fast

I'm based in Israel, so when it was 6:30 a.m., my time, it was the middle of the night in the US. This time gap worked in our team's favor, as we had time to figure out what was going on before our customers woke up.

PHP is an open-source computer programming language used to create websites and web applications. It's such a widely used programming language that we immediately understood that every one of our customers, which includes major corporations and businesses, would likely be affected by this.

With bugs or critical flaws in the infrastructure, like the two that were found in PHP, exploitation is actually quite easy, especially if you use AI agents. That was the first thing we understood: even completely unskilled attackers can use these vulnerabilities to take down sites.

The PHP Foundation said it would disclose the details of the vulnerabilities and release a fix for newer versions of the language around 5 p.m. Israel time. But some details had already been informally disclosed on an online forum. The post was deleted minutes afterward, but screenshots spread around the internet quite quickly in unofficial forums.

So, my team and I dropped everything else and spent all day on Wednesday gathering informal information to see whether we could mitigate the risk of exploitation before an official fix was released.

How to tell if you're at risk

The first step people can take to figure out if they're impacted is to look at their websites and web applications, and try to understand where PHP is involved. You can also assume that most, if not all, of them will use PHP in some way, unless you have very basic HTML-based pages.

The second step would be to look at what vulnerability scanners online are telling you. Tenable, Qualys, and Rapid7 are usually the big three for releasing detection rules and actually detecting the vulnerability. In this case, these vulnerabilities have caused such widespread panic worldwide that they were quick to respond. This is also a way to understand the exact vulnerabilities in your internet-facing assets.

After taking these steps, immediately look online to upgrade your website to the current PHP version. It's quite easy to upgrade that, and it's free. There are some technical steps to do after the fix, so you might need a tech guy to implement them. If you don't update your PHP version, the impact on your business and website can be very, very serious.

Some people are also fully taking their sites offline, and I think that can be the right call if you have evidence that you are being targeted. However, 70% of the internet can't and shouldn't be taken offline just because those sites have some vulnerabilities. It's an emergency step to take if you have evidence of potential exploitation, but it can't be a step taken by everyone.

This was not just about attackers disrupting your website or web application; it was about them taking control of your server, stealing sensitive documents, moving inside your network, and then carrying out malicious operations, such as deploying ransomware or other actions they intended.

The situation has calmed down, but my cybersecurity team is still very concerned

Things have calmed down a bit since Wednesday, but we're still very, very concerned. Patching 70% of worldwide websites doesn't take a minute or two.

Hours after the fix was disclosed by the PHP Foundation, there were already tons of exploitation attempts popping up online. Attackers are getting quicker. I think that in this AI era, when in a matter of minutes, many attackers can attack, you don't have the time you used to.

The whole traditional process of scoping the attack surface, establishing a remediation plan, then calling a guy who's going to be responsible for this remediation plan, et cetera, is broken.

For a long period of time, organizations were investing a lot in what we call post-compromise scenarios. I think the AI era of cybersecurity will involve a lot more security investments in the pre-compromise realm, so defenses can be pre-built and ready for attacks in situations like this.

• Nick Woodhead said he went 48 hours without sleep while helping patch a major website vulnerability.
• The CTO said that with security problems piling up, October feels like "the month of hell" for tech.
• Because AI makes it easier to find and exploit security gaps, Woodhead expects more disruption.

This is an as-told-to essay based on a conversation with Nick Woodhead, founder of the AI company GPTree and chief technology officer at Rothco and Compubox. He spoke with Business Insider on Thursday to share how he's responded to vulnerabilities in the PHP programming language that could affect the majority of the world's websites. The following has been edited for brevity and clarity.

It's always a nightmare when these things happen. Since Tuesday evening, I haven't slept. It's coming close to 48 hours working on this. I'm a CTO, but I also run an agency for multiple clients and have my own company with my own product. So, balancing my time to get everything updated — it's just been exhausting.

About 70% of the internet runs on a programming language called PHP. I'm actively involved within the PHP community itself, so I did get a warning on Tuesday evening regarding the vulnerability and the fact that it was already being addressed by the PHP team. That gave me a head start.

I have some teams offshore, so I was able to jump on that with them.

It's not just applying the patches. It's making sure that nothing was already exposed. We already had infrastructure in place to easily deploy patches, but it still requires a good amount of manual involvement.

I knew that as soon as I walked into the office on Wednesday, I'd have to have my teams jump on this. They were already waiting for the patches to be released.

People are willing to help

One of the biggest headaches, especially on the client side, is that we have a lot of legacy systems, which are running on older versions of PHP that are no longer supported, and official patches are not going to be produced. For those, we ultimately had to come up with other plans. For example, taking sites temporarily offline or moving them behind VPNs.

Eventually, because it's an open-source community, those patches have already been backported, or implemented, by the community. So now we're shuffling back to some of those older systems to get them patched.

That's one of the nice things about PHP. There's such a vast community of people all willing to roll up their sleeves and jump in and help.

Even though I've been in leadership for the last 10 years, I've never taken my hand off the pulse in terms of being connected with the code and the infrastructure. So, I've been hands-on with the development and infrastructure teams to help make sure these issues are resolved. We've been reviewing logs and looking for any potential signatures of a breach that this vulnerability exposed.

The month of hell

It's also meant keeping up to speed with the latest news that's coming out and what other people are finding. We're in a position now where we feel comfortable and safe, but there are new vulnerabilities in the coding tool Node.js. We have some Node services, so now we're looking at how that potentially affects us. October just seems like the month of hell from a technology perspective.

I don't think there is an end in sight with the advancements in AI. For all the positives we get from it, there are a whole bunch of negatives, and this is a perfect example.

OpenAI has already stated that they found many more of these types of vulnerabilities that, thankfully, haven't been leaked. Over the coming months, they are either going to be patches or this information is going to get leaked in the same way and cause the same kind of panic.

I don't think we're at the end of the road yet. There's going to be a lot more to come.

• This week's cyber freakout explained: AI is making software weaknesses easier to find and exploit.
• The message from Cloudflare's Stephanie Cohen and Vercel's Tom Occhino: Don't panic!!!
• Do we need everything connected to the internet? Paper bank statements work well.

A few weeks ago, I heard a strange story about a friend who works at one of the Big Tech companies in Silicon Valley.

She'd recently ripped out the connected devices in her home, ordered paper bank statements, and stocked up on canned goods in her basement.

Now, she's a very sane, experienced person, and quite senior at one of the largest internet companies on earth. Why was she disconnecting so much? Just to be sure, my family ordered paper bank statements, too. It was still a head-scratcher, though.

Fast forward to this week, and her actions look a little less crazy.

AI models have exposed serious security weaknesses in software used by roughly 70% of websites. Meanwhile, US banks are finding AI agents inside customer accounts, including some that appear to be acting without their owners' instructions, Axios reported.

'Black October'

The digerati have now entered full freakout mode. Much of the internet meltdown is happening on, well, the internet, my colleague Alice Tecotzky noted.

On X and Reddit, warnings of a looming “Black October” spiraled into visions of AI grinding civilization to a halt. One lengthy post on X warned of a potential “global cyberattack/AI swarm” and offered a survival checklist: Stockpile cash in small bills, print out your neighbors' phone numbers, download maps, buy a hand-crank radio, and stash a gallon of water per person per day.

Oh, and don't forget the manual can opener. You don't want to survive the AI apocalypse only to be defeated by a tin of beans.

Nikita Bier, a prominent app developer and former head of product at X, best captured the mood.

"It's time to turn off the internet," he posted Wednesday night.

A Cloudflare exec says it's 'a little bit scary'

If you're reading this, you haven't done that yet. But should we really be worried?

I put that question to Stephanie Cohen, chief strategy officer at Cloudflare, which helps protect about 20% of the internet.

"The world is a little bit scary right now," she told me on the side of Cloudflare's annual conference in San Francisco this week.

Here's the problem. The internet is built on decades of software, much of it riddled with security holes.

Some of these weaknesses have been known for years. However, fixing them takes time and money, and hackers often lacked the skills to exploit them anyway. So they were left alone.

AI changes that calculation dramatically. Someone who previously needed years of training to break into a computer system can now get help from an AI model. And these tools can search for weaknesses at a speed humans simply can't match.

The result: The number of newly published software vulnerabilities (Common Vulnerabilities and Exposures in industry lingo) has exploded.

Now, there's a frantic race between people trying to break into systems and those trying to protect them.

Don't panic about AI

Cohen's message, though, was surprisingly reassuring.

AI helps the good guys find and fix these problems. Cloudflare, for instance, released protections for the latest vulnerability to customers, including those using its free service.

And there's a bigger effort underway.

OpenAI has launched an initiative called Patch the Planet, working with Cloudflare and other security professionals to use AI to find weaknesses in widely used software and help repair them.

Tom Occhino, chief product officer at Vercel, told me recently that his company has been talking with partners about launching a nonprofit that would fund a swarm of good AI agents that go out on the internet to find and fix software flaws.

Amazon is joining the fight, too. Its new Continuum service, available Thursday, uses AI agents to find security holes and propose fixes. Amazon said that people maintaining freely available software can use it to help protect the wider internet.

Humans may still have to check and approve these repairs, but the prospect of AI helping clean up decades of neglected software is encouraging.

The irony of this is not lost on some in the industry.

"The funny thing is everyone was saying AI slop code will cause a cyber crisis but it's actually all the old human slop causing it and the AI is just cleaning it up," software engineer Ben Kaufman wrote on X on Thursday.

Either way, Cloudflare's Cohen thinks these AI-inspired freakouts will push the industry to do better — by exposing issues and adding urgency to get them patched.

"We may end up in a world where actually we've become significantly more secure at the end," she said.

The trouble is getting there.

A fundamental question about the internet

When I ran into Occhino recently at a Vercel conference in San Francisco, he described a world in which software that everyone assumed was safe suddenly looks vulnerable because increasingly capable AI models are scrutinizing the basic systems that underpin the internet.

That led to a more fundamental discussion between us: Why did we connect so many things to the internet in the first place?

For years, the technology industry has raced to put everything online. Thermostats. Refrigerators. Doorbells. Cars. Bank accounts.

We assumed that connecting something to the internet automatically made it better.

Perhaps we should reconsider.

Before the internet

I remember the world before the internet. It worked pretty well. We managed to buy groceries, pay bills, heat our homes, and generally get through the day without every appliance talking to a computer somewhere.

That doesn't mean abandoning online banking or throwing your smartphone into the sea.

Occhino, for one, isn't particularly worried about hackers wiping out his bank account. Modern banks have sophisticated protections, and he recommends everyone turn on additional login security.

Maybe the cybersecurity crowd, which spends its life immersed in online threats, is missing something obvious.

Not everything needs to be connected.

Occhino put it neatly: "There's certain things that don't make sense to be on the internet in the first place."

Perhaps that's the lesson from this week's panic. We don't need to turn off the internet.

We just need to remember where the off switch is.

Alice Tecotzky contributed reporting.

Sign up for the AI Insider newsletter here. Reach out to me via email at abarr@businessinsider.com

• Cybersecurity researchers say the PHP vulnerability has repercussions for normal people, too.
• Even if you don't own a website, hackers could use the vulnerability to steal your information.
• One quick fix: diversify your passwords.

If you're still using the same password for everything, it might finally be time to get on that.

While the major cybersecurity vulnerabilities that OpenAI agents helped expose on Wednesday primarily impact the owners and operators of websites, it could also give hackers the opportunity to hijack your personal information, researchers said.

"Be extra careful visiting ANY web site in the next few days," Changpeng Zhao, the cofounder of cryptocurrency platform Binance, said on X.

OpenAI said on Wednesday that researchers using its AI models uncovered two "critical" flaws in the infrastructure of PHP, a popular open-source programming language used on about 70% of the world's websites.

Because digital commerce websites, for instance, can store personal shopper information in PHP systems, that information would be accessible to a bad actor exploiting the web provider's system if that provider hasn't updated it.

The National Security Administration warned that hackers using one of the PHP exploits could "steal sensitive data, disrupt services, or move deeper into a network."

"Even if you yourself are not building software and that's not where your core business is, a lot of your life does depend on companies that depend on those systems," Madeline Lawrence, cofounder of Aikido Security, an application security platform, told Business Insider on Thursday.

"And they could be deeply, deeply vulnerable," she added. She said that one day after the disclosure, cybersecurity platform Cloudflare reported millions of attempts to exploit the vulnerability.

If you do own a website, PHP has released updates it says will help shield websites from hackers. Instructions for applying those updates are available on PHP's homepage.

For everyone else, here are a few tips cybersecurity researchers say you can use to protect your info.

• Don't reuse passwords; use a password manager.
• Check for security advisories from your bank.
• Use two-factor authentication on your devices and accounts — especially for email, banking, and your password manager.
• If your data has been breached, expect more convincing scams and phishing emails.
• Turn auto-updates on and restart your computer weekly.

"You can ask your claude code to audit what on your laptop is out of date and needs updating," Peter Wildeford, head of policy at the AI Policy Network, a bipartisan nonprofit that advocates for safety guardrails and federal oversight, added in a post on X.

Though Lawrence called the vulnerability "very severe," she cautioned against people running to close their bank accounts to protect themselves.

"Assume that if you're getting a notification that your data has been leaked," she said. "Take action on that because you could have credentials or information floating around the dark web."