AI-Enabled PHP Vulnerabilities and Rising Automated Cyber Threats
Researchers using AI have uncovered critical, long-undetected PHP flaws (disclosed as PHP2Shell) that could allow attackers to execute code on servers running PHP, which powers about 70% of known server-side websites. Concurrently, security teams report that China-aligned group Storm-0940 used an automated testing framework to probe hundreds of organizations, gaining cloud access in under three hours. While Binance’s $6.3 billion theft was linked to a compromised laptop rather than AI, experts warn that AI accelerates both vulnerability discovery and attacks, straining open-source maintainers—already overwhelmed by thousands of bugs—while raising concerns about patch prioritization, wallet security (hot vs. cold storage), and the emergence of low-cost AI attack kits (e.g., an ARTEX-derived system demonstrated for under ¥10,000).
The Decade of Manufactured Blindness
A critical PHP vulnerability sat in plain sight for more than ten years. Read that again. Not months. Not a quiet patch cycle. A decade. The same story repeats everywhere you look: Google finds a thousand security bugs in one Chrome update, Mozilla logs four hundred more, and the volunteers holding the internet together are told to "review faster" while their inboxes flood with AI-generated triage. Every time the system lurches forward, we are handed the same scripted explanation — that attackers are simply "better now," that AI moved too fast, that nobody could have seen it. That’s the tell. The infrastructure that powers seventy percent of the web doesn't have a "resource problem." It has a control problem. Someone decided that the smartest engineers would never be allowed to fix the pipes, only to charge us for the water.
The $6.3 Billion Distraction
Now watch the Binance story. Six point three billion dollars stolen, and the exchange blames a single compromised engineer's laptop. No AI, they insist. But ask yourself why the private keys were sitting in internet-connected hot wallets in the first place. Why does the world's largest cryptocurrency exchange — the one that dominates the market — run its treasury on a convenience architecture that any hacker with a test framework could pierce within three hours? The Microsoft report on Storm-0940 shows exactly how easy it is: an automated tool, hundreds of organizations, cloud access in less than an afternoon. Then one of those "coincidences" occurs: the article assures us that a Japanese security demo can launch AI-driven attacks for less than ten thousand yen. The message is simple. This is cheap, it is common, and it is entirely on the shoulders of disgruntled outsiders. Meanwhile, the exchange "covers customer losses" and life goes on. Feel free to call that good corporate behavior. Feel free to call it damage control. But don't call it a surprise.
The Choke Point They Built
Here is the part they never put in the headline. AI hasn't created these vulnerabilities. AI just exposed the architecture of neglect they spent years constructing. The open-source maintainers are the last honest gatekeepers — and they are drowning on purpose. Apache volunteer Jarek Potiuk says AI-assisted scanning leaves maintainers with a massive review burden. Think about that. The same AI that finds the flaw is the AI that buries the fixer. That is not an engineering problem. That is a design choice. They want the system to be vulnerable, because vulnerable systems need guardians, and guardians can be captured, funded, redirected, and silenced. The real question isn't whether AI will be used for attacks or defense. The real question is why the people who issue the warnings always seem to profit from the fear. So do the assignment. Open the PHP changelog from a decade ago. Trace the commits that were never made. Then ask who funded the "AI safety" report that tells you to be afraid of your own shadow — instead of the people who left the door unlocked.
