Black October: cyber’s month from hell in the age of AI
October 25, 2026

Want to take the controls right away? Play with the simulator ↓
About 50 dollars.
That is what each successful intrusion cost, in tokens (the basic unit of AI), for a lone hacker who went after more than a hundred companies this autumn. Deere, SharkNinja, Cummins. The man did not write his attacks by hand: he handed them to agents, run from Cairn, an open source platform whose author says it “was not designed for hacking attacks.” More than 1,200 sites targeted, more than a hundred breached, about 5,000 dollars of tokens in total.1
Four months earlier, on June 22, the heads of the Five Eyes cyber security agencies (United States, United Kingdom, Canada, Australia, New Zealand) signed a joint statement titled “The AI shift in cyber risk: why leaders must act now.” It reads: “The timeline is not years, it is months.”2
October proved them right.
On October 22 at 3:42 UTC, the X account AISafetyMemes gave the month a name: Black October.3 The name stuck: CNBC put it in a headline the very next day.4 Put end to end, the facts of October do tell the story of a tipping point. Attack becomes automatic, driven by AI agents that cost a few dollars, while defense still works by hand and has to secure infrastructure that is slow to move.
The window and the crowbar
To understand a wave of cyberattacks, you can split it into two stages. The flaw, first: the badly closed window, a mistake in a piece of software that nobody had seen. Its exploitation, next: the crowbar, the program that slips in through that mistake (an “exploit”), and everything the attacker does once inside.
Until now, each stage had its bottleneck: weeks of expertise to find a flaw, as many to write the exploit and carry out the intrusion. Skilled human attention was the scarce resource, so attackers chose their targets.
In October 2026, AI blows open both bottlenecks at once. The number of attackers stays the same. Their striking power, though, multiplies. Flaws are found by AIs. And their exploitation runs through open source attack harnesses (frameworks that organize a model’s intelligence to make it especially good at one task, here cyberattacks), ARTEX, Cairn, Phantom, that anyone can plug into the AI of their choice. Microsoft describes ARTEX as able to run “an autonomous penetration test from reconnaissance through data exfiltration.” Where a team used to be needed, a lone attacker is enough.5
And that striking power is growing fast. According to the UK AI Security Institute, the length of cyberattack tasks (measured in human expert time) that a model completes four times out of five was doubling every eight months as of November 2025, every 4.7 months as of February 2026, and by May Claude Mythos Preview and GPT-5.5 were already above the curve: the attacks AI systems can carry out on their own have gone from a few minutes in late 2024 to several hours today.6
The first stage is plain to see in the numbers. Google Threat Intelligence counts 5,045 published vulnerabilities (the famous “CVEs,” the official identifiers for software vulnerabilities) in January 2026, and 10,740 in August.7 On October 23, on CNBC, Chris Krebs, former head of CISA, the US cybersecurity agency, even claimed that 3% of all critical vulnerabilities ever discovered were found in the last month.4 Across vulnerabilities as a whole, the order of magnitude holds: 4% of all those recorded since 1999 were published in thirty days.
Monthly published flaws have more than tripled since January
Number of CVEs published per month, January 2024 to October 2026
of all flaws recorded since 1999 were published in thirty days: 16,255 from September 25 to October 25, 2026, out of 395,298.
| Month | CVEs published |
|---|---|
| January 2024 | 2591 |
| February 2024 | 2784 |
| March 2024 | 3299 |
| April 2024 | 3604 |
| May 2024 | 4991 |
| June 2024 | 3080 |
| July 2024 | 3113 |
| August 2024 | 2895 |
| September 2024 | 2514 |
| October 2024 | 3566 |
| November 2024 | 4054 |
| December 2024 | 3433 |
| January 2025 | 4273 |
| February 2025 | 3673 |
| March 2025 | 4001 |
| April 2025 | 4033 |
| May 2025 | 3980 |
| June 2025 | 3682 |
| July 2025 | 3774 |
| August 2025 | 3629 |
| September 2025 | 4319 |
| October 2025 | 4274 |
| November 2025 | 3020 |
| December 2025 | 5493 |
| January 2026 | 4302 |
| February 2026 | 4616 |
| March 2026 | 6236 |
| April 2026 | 5813 |
| May 2026 | 6933 |
| June 2026 | 7949 |
| July 2026 | 9759 |
| August 2026 | 12260 |
| September 2026 | 14934 |
| October 2026 | as of October 25: 13,618 (full-month projection: 16,248) |
Before October: the sky darkens
May to August: Claude Code as an attack tool
CrowdStrike, one of the largest cybersecurity companies in the world, observed from May to August four previously unknown groups of attackers, all relying on Claude Code, Anthropic’s coding agent. The report, published on October 21, assesses with moderate confidence that agentic AI “commoditizes baseline offensive cyber operations,” putting basic cyberattacks within almost anyone’s reach. And, with high confidence, that such intrusions will almost certainly increase.8
August 4 to October 4: ARTEX in nineteen countries
Zscaler documents a campaign run with ARTEX, whose prompts span August 4 to October 4, against targets in nineteen countries or territories. The configuration files request deepseek-v4.1-flash, deepseek-v4-pro, GLM-5.3 and Grok 4.7.9 The first three are the best Chinese models, all of them open source.
August 11 to 24: the PHP flaw, found with AI
On August 11, the firm Calif reports to the PHP team (PHP being the language behind a large share of websites) a first critical flaw, found with the help of a generally available model, according to its researcher.10 On the 24th, Wiz Research pins down the full set of flaws that will become “PHP2Shell” (CVE-2026-109618 and CVE-2026-109619), found with its Atlas tool, Gemini 4 Argon and GPT-5.6 Sol. Nearly every version since PHP 5.4 is affected.11
At this point the flaw is still a secret, known only to those who found it and to the PHP team (the standard procedure for a flaw: it is only announced publicly once the patch exists).
At this stage, the case is still completely silent, and OpenAI puts together a coalition of researchers to work on these flaws with its AI systems.12
It is the public announcement of these flaws, on October 21, that will set off the “Black October” tsunami.
August 29 to 31: an open model with its refusals removed
On August 31, the company Abliteration announces on X a rather special model built on GLM-5.3 (an open Chinese model). It tampered with the model’s neural network to remove the refusal mechanisms meant to stop users from giving it dangerous missions. Abliteration explicitly hosts and sells its uninhibited model for “the offensive cyber, red teaming, and agent testing work other models refuse to do” (red teaming meaning simulated attacks).
Today we're releasing abliterated-model-large-v2. Based on GLM-5.3, which is #3 on Terminal-Bench 4.0 (behind only Opus 5 and Fable), with 2× the cyber exploitation of 5.2. We abliterated and hosted it so it does the offensive cyber, red teaming, and agent testing work other Show more
The scores shown were measured by the vendor itself on its modified model, against other vendors’ figures obtained under different conditions, and nobody has verified them; the blog post mentions no identity verification of customers.
The gesture matters more than the scores. An open model is a tool delivered with its safety catch; once the weights (the parameters of the neural network) are published, anyone can file it off.
September 25: one man, some agents, a hundred companies
This is when the Cairn hacker mentioned at the start begins his campaign, according to the Reuters investigation published on October 19. Researcher Snorre Fagerland estimates that he used a mix of DeepSeek and Claude Code, and sums it up: “It’s a new world now.”1
Late September: the Korean banks
At least nine Korean financial institutions have been attacked or targeted since late September; CrowdStrike links these attacks to ARTEX and Claude Code. The ARTEX developer, “Autumn-27,” then closes the source code, citing “misuse of the tool” (hmm, what did he expect?). The suspect named by CrowdStrike, in Guangdong, denies involvement and says his identity was stolen.13
The October log
September to mid-October: 2,250 targets
Microsoft attributes to Storm-0940, a China-state aligned actor, the supply chain compromise of ConnectWise, a vendor of IT management software. After the intrusion, the actor used ARTEX to attempt to sign in to more than 2,250 corporate environments. An automated password-spray campaign, from October 10 to 14, peaked on October 11 at 2,900 failed logins per minute.5 No human types 2,900 passwords a minute…
October 20: the open model pulls ahead
Vals AI, a company that evaluates AI models, posts on X a measurement that circulated widely.
We found DeepSeek V4.1 Flash 1017 beats GPT 6 Sol on our multi-step offensive cybersecurity task. Sol was tested via the Daybreak trusted access program. We have been building a cybersecurity benchmark based on simulated corporate networks. This is a valuable indicator for the Show more
In a simulated attack on a corporate network, DeepSeek V4.1 Flash 1017 completes on average 16.3 objectives out of 21. GPT-6 Sol, tested through Daybreak, OpenAI’s restricted access program for cybersecurity, completes 15.7. Claude Opus 5.5 refuses partway through (1 out of 21).
What is more, DeepSeek gets there by burning many more tokens, but since each one costs far less, the final bill is much lower than GPT’s. On CyberBench, Vals’ other leaderboard, GPT-6 Sol stays ahead.
In short, an offensive capability that a closed lab reserved for hand-picked partners now exists in open models that anyone can download for free.
October 20 and 21: the secret leaks
On the PHP side, the plan was well set: patches and public announcement on Thursday, October 22, at 14:00 UTC. It would not hold. On the 20th, around 15:00, the identifiers of the two flaws are circulating on forums and social media, without technical details. At 20:00, Calif mistakenly publishes a video in which it uses the flaw to carry out an attack. It is quickly taken down, but copies are already going around, and the PHP Foundation believes it sped up the development of public exploits.14
During the night, while the European maintainers sleep, several security vendors report active exploitation of the flaw by attackers, according to Dan Lorenc, CEO of Chainguard, a company that publishes software and had received the patch in advance. On the 21st at 7:41 UTC, more than six hours before the agreed time, Chainguard publishes the fixed versions. For the PHP Foundation, Chainguard “unilaterally broke the embargo.” Any attacker can now study the patch.14
The PHP Foundation decides to bring the public announcement forward (now that the cat is out of the bag…)
October 21: the day things got unplugged
At 14:00 UTC, PHP2Shell officially goes public along with its patches.
According to Wiz, PHP “powers 70% of all websites in the world.”11
The FBI then recommends taking offline any website that cannot be patched right away, ENISA, the EU cybersecurity agency, calls for immediate action, and, in the hours after the announcement, Matthew Prince, CEO of Cloudflare, mentions “millions” of exploitation attempts.12
Before the day is out, the French Interior Ministry takes prefecture websites offline as a precaution, Orange suspends some websites and apps, and the list grows: Germany, Finland, the Netherlands (including the Port of Rotterdam), Belgium, Czechia, Japan, the BBC, Wikimedia, the Internet Archive.15
In the hours that follow, a flood of other flaws is announced, each more serious than the last.
LiteLLM, a widely used open source component that connects applications to AI models, discovers that poisoned, credential-stealing releases were live for nearly three hours before the developers noticed.16 Node.js ships ten security fixes, four of them for serious flaws, and GitLab announces twelve flaws, one of them rated 10 out of 10 for severity, the maximum.17
On the other side of the world, GMO Internet shuts down its “Desktop Cloud” overnight, servers rented by individuals to run their currency-trading bots: attackers had broken in with ARTEX. Nearly 27,000 servers are switched off, and the stolen credentials are used to place trades on clients’ accounts at five or more brokers. The group’s security team had spotted the flaw, but the fix did not come in time. Four days later, its CEO, Masatoshi Kumagai, will call it a national crisis: the internet, he says, “is already starting to break down.”1819
The same day, London launches a three-year household preparedness campaign against cyber risks. Its recommendations: at least three days of water (about three litres per person per day), food that keeps, medicine, cash and a battery radio. Wes Streeting, the Defence Secretary, puts the question bluntly: how would we cope if the supermarkets’ payment systems went down? He points to cyberattacks from hostile states or terrorists. Worth noting: the government does not specifically link the campaign to AI, and it had been announced since September. But the events of the past few hours seem to prove it right.20
Late in the day, Jason Clinton, Anthropic’s deputy chief information security officer, warns on X that the worst is still ahead, and asks security leaders to push for the resources to defend themselves. We will need, he writes, to hold on for about eighteen months before things get better.21
October 22: “any ONE of these”
On the morning of the 22nd, a tweet captures the mood and passes two million views.
they’re calling it “Black October” and i don’t think people realize how serious this is in the last 48 hours there have been over 27 major cybersecurity incidents. not in a month. not in a week. in 48 hours any ONE of these would normally be the biggest story of the year PHP: Show more
“Any ONE of these would normally be the biggest story of the year.”
October 23: the wave goes on
On the 23rd, the announcements keep coming in the same direction. Exploits able to get around a standard memory protection (ASLR) appear, and Mirai-family botnets (networks of zombie machines) pounce on PHP2Shell. Among its customers, Qualys counts about 110 million PHP instances, 71% of the total, on versions too old to receive the patch.22
Finally, the mainstream press picks it up. CNN headlines: “The biggest-ever internet security threat has been known for 22 years. AI made it a crisis in 2 days.”23
October 24 and 25: the ebb
That’s it: the peak of announcements seems to have passed.
Now begins the least spectacular part, and the longest: patching. Millions of servers still have to be updated, and some of them cannot simply be. And the open AI models that make it possible to find flaws also make it possible to exploit them, cheaply and relentlessly. So it is all but certain that the number of attacks will rise in the coming months, and that some will succeed before the defense gets organized.
We are entering a new cyber world.
Automatic attack, defense by hand
Back to our two stages. Finding flaws is more and more automatic: PHP2Shell was found by researchers armed with AI. So is exploiting them: the attack harnesses ARTEX, Cairn and Phantom are public or have been, and unrestrained open source AIs can be rented online. The result: one man did the work of a team, and Storm-0940 ran 2,250 attacks in parallel.
On the other side, the response of many states was the oldest move in computing: pulling the plug. The precaution is wise, since as of October 23 no large-scale compromise had been confirmed. It also says something about the state of the tools: nothing finer was at hand…
AI is shortening the time between the discovery of a flaw and its exploitation. The same families of machines write the exploit and the patch. The difference between the two camps lies in the loop around them. On the attack side, the loop runs on its own, from reconnaissance to exfiltration, for a few dollars. On the defense side, it still goes through an acknowledgment, an embargo calendar, an administrator who updates servers one by one.
Attackers now arrive before the patch
Average time between a patch’s release and the first observed exploitation, in days
| Period | Average (days) | Note |
|---|---|---|
| 2018-19 | 63 | 2018-2019 average |
| 2020-21 | 44 | 2020 to early 2021 |
| 2021-22 | 32 | 2021-2022 average |
| 2023 | 5 | Excluding 15 outliers; 47 days with them |
| 2025 | -7 | Estimate (M-Trends 2026) |
By the end of this cycle, we will probably have learned to use AI to protect ourselves better. It is the problem, and it is also the cure.
For companies, AI can first find flaws before the attacker does. In one month, the fifty or so partners in Anthropic’s Glasswing program found more than 10,000 high or critical severity flaws in their own software; Cloudflare alone found 400.24 It can then fix them: OpenAI’s Codex Security tool has combed through more than 30 million code changes, and OpenAI is funding, with Trail of Bits, HackerOne and Calif, researchers tasked with repairing the open source software everyone depends on.25 The bottleneck, in fact, is no longer discovery: Anthropic writes that the work is now limited by “how quickly we can verify, disclose, and patch.”24 That is where AI now has to come in: triaging alerts, writing and testing patches, monitoring systems continuously and reacting in minutes rather than days.
For individuals, defense is arriving in their pocket. Since October 14, Android analyzes messages with Gemini to spot scams, checks unknown links on the phone before you click and cuts off fake bank calls; Google’s existing protections already flag more than 5 million suspicious calls and texts a month.26 And anyone can already ask their AI assistant to examine a dubious message, attachment or link before touching it. AIs will probably mediate more and more of our digital wanderings, to protect us from the dangers of the internet. In the long run, that could make the internet safer: most security flaws remain… human!
In October, the crowbar went automatic. What remains is to invent the lock that changes itself as fast as it is forced.
In the meantime: what everyone can do
Until this new kind of security is in place, a few habits matter more than all the others.
For everyone:
- Update your phone, computer, browser and apps, and leave automatic updates on.
- Turn on two-factor authentication (with an authenticator app, not by text message or email) wherever possible, starting with your email, which opens every other door; switch to passkeys when a service offers them.
- Keep your passwords in a password manager, with a different password for each service.
- Remove access for third-party apps you no longer use.
- Be more wary of urgent messages: AI makes fakes convincing. At the slightest doubt, call the person back through a channel you know.
- Keep a little cash and an offline copy of your important documents.
For those who run a website or a company:
- If you run a WordPress site or any other PHP site, check with your host that it has moved to the fixed versions released on October 21 (8.2.35, 8.3.36, 8.4.27 or 8.5.12): versions 8.1 and older get no official fix.27
- Know what you expose on the internet, and remove what is no longer maintained.
- Limit and monitor access for the contractors who have a hand on your systems.
- Practice pulling the plug: know who decides to cut off, and how the company keeps running in degraded mode. It is a matter of resilience.
Your turn to play
Simulator
How many doors will stay open to attackers?
One lit door = 50 serious flaws, exploitable and not yet patched. Make two choices.
95
doors open at the same time, Dec 2030
that is 4,700 serious flaws · × 18 compared with today
As long as defense stays manual, open doors pile up. More and more flaws arrive, and each one stays open for about two months. By end of 2030: × 18 compared with today.
| Date | Your choices | If defense does nothing |
|---|---|---|
| Oct 2026 | 260 | 260 |
| Jan 2027 | 310 | 310 |
| Jan 2028 | 630 | 630 |
| Jan 2029 | 1,300 | 1,300 |
| Jan 2030 | 2,500 | 2,500 |
| Dec 2030 | 4,700 | 4,700 |
A scenario model, not a forecast. The starting points are sourced; extending them to 2030 and the values behind the choices are assumptions.
How it is calculated
What the simulator counts. The number of “high-risk” flaws open and exploitable at the same time: exploitation has started, the patch is not applied yet. One door in the grid stands for 50 such flaws.
The flow of flaws. The model starts from about 135 high-risk flaws published per month, the mid-2026 order of magnitude according to Google Threat Intelligence (about 65 a month in mid-2025, about 135 in mid-2026, excluding mass disclosures; the August 2026 peak of 350 is inflated by Linux, Oracle and TOTOLINK routers). “Attackers speed up a little”: +50% a year. “As today”: +100% a year, the doubling Google observed. “A lot”: +200% a year, roughly a doubling every eight months, the pace at which the UK AI Security Institute saw the length of cyber tasks models complete on their own double as of late 2025 (4.7 months in its February 2026 estimate); linking these two different quantities is an assumption.
A flaw’s window. Each flaw becomes exploitable 7 days before disclosure (Mandiant’s estimate for 2025, M-Trends 2026; 14 days before in the “a lot” choice) and stays so until its patch is applied. Manual patching: 55 days, the average time to remediate high and critical application and API flaws in 2025 according to Edgescan (2026 report). AI-driven patching: 14 days in the “halfway” choice, the Glasswing order of magnitude (Anthropic: a high- or critical-severity bug found by Mythos Preview “takes two weeks to patch” on average; Glasswing measures the time to produce the patch, borrowed here as a benchmark); 3 days in the “massively” choice. The AI-patched share starts at zero in October 2026 (nobody measures it today) and rises in a straight line to 50% or 80% by end of 2030.
The stock of open flaws. Stock = flow × window length (Little’s law), corrected for the growth of the flow: N(t) = d(t) × (e−r·TTE − e−r·Tpatch) / r, where d(t) is the daily flow, TTE the time to exploit, Tpatch the patching time and r = ln(1 + G) / 365. The “do nothing” scenario keeps the same attackers and a fully manual defense.
Limits. “High-risk” is Google’s rating, not observed exploitation: in 2026, 0.23% of published flaws were seen exploited. The simulator therefore measures possible exposure, not a number of attacks. Delays are averages applied to every flaw, growth never saturates, and a “patched” flaw is patched everywhere at once, which is optimistic.
Sources: Google Threat Intelligence, September 30, 2026; Mandiant, M-Trends 2026; Edgescan, 2026 report; Anthropic, Glasswing initial update, May 22, 2026; AI Security Institute, May 13, 2026.
Footnotes
-
Reuters, exclusive investigation into the Cairn hacker (republished by CP24), October 19, 2026. https://www.cp24.com/news/world/2026/10/19/how-one-hacker-used-ai-agents-and-a-few-thousand-dollars-to-break-into-scores-of-sites-reuters-exclusive/ ↩ ↩2
-
Heads of the Five Eyes cyber security agencies, “The AI shift in cyber risk: why leaders must act now,” joint statement, June 22, 2026. https://www.ncsc.govt.nz/assets/news/Documents/Five-Eyes-Cyber-Security-Agency-AI-Call-to-Action-22-June-2026.pdf ↩
-
SecurityToday, on the origin of the name and the gap between attacks and disclosures, October 22, 2026. https://www.securitytoday.de/en/2026/10/22/black-october-many-attacks-had-been-running-for-months/ ↩
-
CNBC (Ashley Capoot), “AI’s ‘Black October’: Critical PHP flaws set off global security scramble,” October 23, 2026, with Chris Krebs’s remarks on “Squawk Box.” https://www.cnbc.com/2026/10/23/php-vulnerabilities-ai-cybersecurity.html ↩ ↩2
-
Microsoft Security, post on Storm-0940, ARTEX and ConnectWise, October 21, 2026. https://www.microsoft.com/en-us/security/blog/2026/10/21/storm-0940-uses-artex-agentic-ai-connectwise-supply-chain-compromise/ ↩ ↩2
-
UK AI Security Institute, “How fast is autonomous AI cyber capability advancing?”, May 13, 2026 (CTF-style task suite, 80% reliability, 2.5 million token budget per task). https://www.aisi.gov.uk/blog/how-fast-is-autonomous-ai-cyber-capability-advancing ↩
-
Google Threat Intelligence Group (R. Grunewald, S. Mazumdar, K. Vanderlee), vulnerability discovery and exploitation trends since the rise of AI, September 30, 2026. https://cloud.google.com/blog/topics/threat-intelligence/vulnerability-discovery-and-exploitation-trends-in-the-ai-era ↩
-
CrowdStrike, post on four agentic AI campaigns, October 21, 2026. https://www.crowdstrike.com/en-us/blog/crowdstrike-uncovers-new-agentic-ai-campaigns/ ↩
-
Zscaler, research post on a global AI-assisted hacking campaign, October 21, 2026. https://www.zscaler.com/blogs/security-research/inside-global-ai-assisted-hacking-campaign ↩
-
Calif, account of the PHP2Shell discovery (reports on August 11 and 21, proof confirmed by PHP on August 15), October 21, 2026. https://calif.io/php2shell/ ↩
-
Wiz Research, PHP2Shell disclosure post, October 21, 2026. https://www.wiz.io/blog/php2shell-php-rce ↩ ↩2
-
Associated Press (republished by PBS NewsHour), on the rush to patch PHP, October 22, 2026. https://www.pbs.org/newshour/nation/ai-discovered-a-software-vulnerability-that-could-impact-70-of-websites-worldwide-the-rush-is-on-to-patch-it ↩ ↩2
-
Korea JoongAng Daily, on ARTEX and the Korean banks, October 10, 2026. https://www.koreajoongangdaily.com/business/chinese-ai-tool-linked-to-korean-bank-hacks-halts-public-updates-as-suspect-denies-involvement/12913376 ↩
-
The PHP Foundation, “Today’s PHP Security Release, and How We’re Strengthening PHP Security,” October 21, 2026 (timeline of the leak, embargo broken by Chainguard). https://thephp.foundation/blog/2026/10/21/todays-php-security-release-and-how-were-strengthening-php-security/ ↩ ↩2
-
Reuters (republished by Investing.com), factbox of websites taken offline over the PHP flaws, October 22, 2026. https://www.investing.com/news/stock-market-news/factboxwebsites-taken-offline-over-php-risks-4963631 ↩
-
LiteLLM, incident report of October 21, 2026. https://docs.litellm.ai/blog/security-incident-oct-21-2026 ↩
-
Node.js, October 2026 security releases, October 21, 2026, https://nodejs.org/en/blog/vulnerability/october-2026-security-releases ; SecurityOnline, on GitLab’s critical patch release (CVE-2026-110264), October 21, 2026, https://securityonline.info/gitlab-critical-patch-release-cve-2026-110264/ ↩
-
GMO Internet, notice on unauthorized access to “Onamae.com Desktop Cloud” (October 21, 2026, 26,739 servers concerned), https://www.onamae.com/news/article/11584/ ; 5th notice, October 24, 2026, https://group.gmo/info/alert/2026102402/ ; Finwire, on trades placed by the attackers at five Japanese brokers, https://finwire.io/news/forex-news/five-japanese-fx-brokers-confirm-hackers-placed-trades-after-server-host-breach ↩
-
OfficeChai, on Masatoshi Kumagai’s statements (ARTEX, national crisis, flaw spotted but fixed too late), October 25, 2026. https://officechai.com/stories/the-internet-is-breaking-down-says-japans-gmo-internet-group-ceo-after-hackers-hijack-its-cloud-servers-to-run-unauthorized-fx-trades/ ↩
-
Yahoo News UK (from the Evening Standard), on the launch of the household preparedness campaign by Wes Streeting and Dan Jarvis, October 22, 2026, https://uk.news.yahoo.com/streeting-urged-londoners-stockpile-three-173859903.html ↩
-
Jason Clinton on X, October 22, 2026. https://x.com/JasonDClinton/status/2113325263157395456 ↩
-
SecurityWeek, on Mirai botnets joining PHP2Shell attacks (with Sansec and Qualys figures), October 23, 2026. https://www.securityweek.com/mirai-botnet-operators-join-php2shell-attacks-as-aslr-bypass-exploits-emerge/ ↩
-
CNN, “The biggest-ever internet security threat has been known for 22 years. AI made it a crisis in 2 days,” October 23, 2026. https://www.cnn.com/2026/10/23/tech/ai-cybersecurity-php2shell-explained ↩
-
Anthropic, “Project Glasswing: Initial Update,” May 22, 2026. https://www.anthropic.com/research/glasswing-initial-update ↩ ↩2
-
Help Net Security, on OpenAI expanding Daybreak and launching Patch the Planet, June 23, 2026. https://www.helpnetsecurity.com/2026/06/23/openai-expanded-daybreak-cybersecurity-initiative/ ↩
-
The Next Web, on Android’s new scam protections (Gemini analysis, link checking, fake bank calls), October 14, 2026. https://thenextweb.com/news/google-android-scam-protections-gemini ↩
-
BleepingComputer, on PHP’s emergency patches (8.2.35, 8.3.36, 8.4.27, 8.5.12) and the lack of a fixed release for PHP 8.1 and older, October 21, 2026. https://bleepingcomputer.com/news/security/php-ships-emergency-patches-for-critical-php2shell-flaws ; Help Net Security, October 21, 2026. https://helpnetsecurity.com/2026/10/21/php2shell-php-vulnerabilities-patched-cve-2026-109618-cve-2026-109619 ↩
Want to go further on this topic?