Black October Hack Hits 50+ Sites, Citi, JPMorgan & Wells Fargo Restrict AI Agents

black october 2026

The Black October hack is the name cyber pros gave to a wave of attacks in October 2026, led by two critical PHP bugs that knocked more than 50 websites offline on October 21. It came alongside new AI agent restrictions at Citi, JPMorgan and Wells Fargo. PHP shipped fixes in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35, so the quickest PHP vulnerability test right now is checking a server’s version. As Reuters reveals, government websites went dark as operators rushed to patch.

The PHP Vulnerability Tracker and user reports put the count at 56 sites. Cyber pros started calling this stretch Black October because so many attacks and emergency fixes landed at once. The two Black October 2026 bugs had gone unnoticed in PHP’s code for more than a decade, until AI-assisted research caught them in August.

Also Read: Aave-Linked Exploit Drains 114 ETH as Labs Urges MiCA DeFi Reforms

Black October 2026: PHP Bugs Trigger Outages and AI Agent Restrictions

Black October 2026 PHP Bugs Trigger Outages and AI Agent Restrictions
Source: MarketCapOf

What Are The Black October Bugs?

The flaws, CVE-2026-109618 and CVE-2026-109619, are behind the Black October hack and allow remote code execution without a login. As Axios reveals, attackers could steal passwords and data or take over servers. Researchers at Alphabet-owned security firm Wiz and cybersecurity company Calif found the Black October bugs with AI tools, and data from internet intelligence firm Censys shows about 1.5 million of 2.6 million hosts run PHP versions with no fix.

Tiffany Farriss, the interim chief executive of the Drupal Association, said:

“All servers using any version of PHP released in the last 20 years will be vulnerable. This issue impacts the majority of the internet.”

How The Black October Hack Spread

The embargo leaked a day early, and CERT-EU told anyone who could not patch the Black October bugs at once to pull PHP apps offline. Councils, universities, wikis and an online store went dark within hours, the first big outages of Black October 2026.

PHP2Shell OutagesSites That Went Dark On October 21 And 22
56Went dark
51Back up
5Still dark
French prefecture websitesBBC The Traitors websiteSUUMOat homeLIFULL HOME’SCNILDutch NCSCDigiDDeviantArt4chanTweakersPort of RotterdamMirahezeUniversity of Vienna
Figures as of October 22, 23:12 UTC. Red tags are sites still offline at that time.
17Went dark
16Back up
1Still dark
French prefecture websitesCNILDutch NCSCDigiDMijnOverheidValtoriCity of Edinburgh CouncilOxford City CouncilBelgian Foreign Affairs
Public bodies made up almost a third of the list, from data protection authorities to city councils.
25Went dark
24Back up
1Still dark
BBC The Traitors websiteDeviantArt4chanTweakersRTL NieuwsPort of RotterdamNespresso CroatiaFollow the MoneyPinboard
Media outlets, forums, wikis and an online store pulled their pages as a precaution.
11Went dark
8Back up
3Still dark
SUUMOat homeLIFULL HOME’SNotuBizMirahezeSakura InternetCodmonAcuity Schedulingeasybill
Three Japanese property portals went dark on October 22 and were still offline late that day.
3Went dark
3Back up
0Still dark
Haaga-HeliaUniversity of FreiburgUniversity of Vienna
Universities also took webmail, Moodle and study guides offline.

How Long Sites Stayed Dark During The Black October Hack

The Dutch data protection authority stayed offline for about 32 hours, and Nespresso’s Croatian store came back after just 15 minutes.

DowntimeHow Long Sites Stayed Offline
Dutch data protection authority32h 16m
CNIL (France)27h 05m
NotuBiz council portals24h 11m
National Land Survey of Finland23h 16m
Haaga-Helia University22h 46m
University of Freiburg21h 01m
Nespresso Croatia store15 min
easybill2h 20m
Port of Rotterdam2h 36m
Acuity Scheduling3h 02m
RTL Nieuws3h 32m
University of Vienna4h 17m
Time between the first public report of each outage and the site’s return. Each tab is scaled to its own longest outage.

Which Sites Are Still Down After The Black October Hack

As the PHP2Shell outage page shows, 56 sites had gone offline by 23:12 UTC on October 22. Five were still offline, including three Japanese property portals and the BBC’s The Traitors site. Being listed does not mean a site failed a PHP vulnerability test or got hacked, and most went dark as a precaution.

Outage CountWhere PHP2Shell Outages Hit
56Tracked
51Back up
5Still down
5h 06mMedian
Netherlands24
Global11
Japan5
United Kingdom4
France3
Finland3
Germany2
Belgium2
Austria1
Croatia1
Website25
Government17
Platform11
University3
BBC The Traitors websiteSince Oct 22, 11:36 UTC
LIFULL HOME’SSince Oct 22, 04:09 UTC
at homeSince Oct 22, 03:42 UTC
SUUMOSince Oct 22, 03:10 UTC
French prefecture websitesSince Oct 21, 17:05 UTC
Figures as of October 22, 23:12 UTC. Most sites went offline as a precaution, not because of a confirmed breach.

Have Hackers Exploited The Black October Bugs Yet?

As NBC News shows, hackers seem to struggle with the flaws behind the Black October hack. Nine firms, including CrowdStrike and Sophos, saw no successful attack as of Thursday.

Sherrod DeGrippo, vice president of threat intelligence at Palo Alto Networks‘ Unit 42, had this to say:

“We have not yet seen these PHP vulnerabilities exploited in the wild yet.”

Also Read: Bitcoin ETFs Plunge 95.6% as Wintermute Moves $90M in BTC

Why Black October 2026 Brought AI Agent Restrictions To Banks

Axios also reported that banks have spotted unauthorized AI agents inside customer accounts, one of the problems cyber pros group under the Black October hack. The AI agent restrictions are already in place, as JPMorgan, Citi, Wells Fargo, Bank of America and Charles Schwab have restricted third-party AI agents from accessing customer accounts.

Citi said in a statement:

“To help safeguard customer accounts and information, we do not permit third-party AI agents or assistants to log into a customer’s account or transact directly within our digital banking platforms.”

Where AI Agent Restrictions Leave Trading Apps

Trading apps are moving the other way. Robinhood targets US crypto traders with 10x leverage and AI agents, adding AI-powered trading tools inside its app and offering up to 10x leverage on Bitcoin and Ethereum perpetual futures for eligible users. Banks are shutting outside agents out of accounts, and brokers are building their own agents in.

That split matters as more money flows into crypto. The AI agent restrictions also land as wealthy investors plan bigger crypto allocations, with a recent study finding institutions expect their average crypto share to rise from 11% to nearly 17% within three years. On-chain use stays busy too, as TRON averaged 4.41M daily active accounts over 30 days earlier this month. The Black October hack has turned account access into a security question for banks and brokers alike, and both now have to decide how much control to give an AI agent.

What The Black October Hack Means For Bitcoin Holders

The Black October bugs did not touch blockchains, but crypto sites on PHP still need patches. For holders, the bigger question right now is price, and Bitcoin traded near $81,488, which is the starting point for the calculator figures below.

Bitcoin profit calculation
A $10,000 Bitcoin buy at $81,488 would return $921.85, or 9.22%, if BTC climbs to $89,000. Source: MarketCapOf Crypto Profit Calculator

MarketCapOf’s Crypto Profit Calculator puts a possible rebound in dollar terms. A $10,000 buy at $81,488 would grow to $10,921.85 if Bitcoin climbs back to $89,000, a profit of $921.85, or 9.22%, before any trading fees. That means Bitcoin needs a gain of just over 9% from its current price for this position to reach that level.

BTC ROI Calculator
Bitcoin at 0.97x and Solana at 0.89x from September 24 to October 23, 2026 – Source: MarketCapOf ROI Calculator

MarketCapOf’s ROI calculator shows how the past month played out. From September 24 to October 23, Bitcoin returned 0.97x, so $1,000 invested would now be worth $968.54, a drop of about 3%. Solana fared worse at 0.89x, turning the same $1,000 into $891.23, a loss of almost 11%.

That puts this week’s dip in proportion. Bitcoin has traded in a fairly tight band between roughly $81,000 and $86,000 over the month, and it lost far less than a major rival like Solana. ARK Invest CEO Cathie Wood also recently said Bitcoin is turning against gold as spot ETFs posted $241M in inflows.

Why Upgrading PHP Fixes The Black October Hack

The PHP2Shell tracker calls upgrading the only full fix. Admins must restart PHP afterward, and a firewall does not replace the patch, so a PHP vulnerability test only helps if an upgrade follows.

How To Run A PHP Vulnerability Test

A basic PHP vulnerability test starts with the version number. Anything below the new releases still carries the Black October bugs, and a PHP release manager said changing settings will not stop attacks. Small sites on shared hosting run the highest risk from the Black October hack, so their PHP vulnerability test often comes down to asking the host.

Version CheckIs Your PHP Version Patched?Pick your PHP branch (run php -v on the server to see it):
Patched from PHP 8.5.12
Vulnerable8.5.0 to 8.5.11
Patched8.5.12 and newer
Versions below 8.5.12 are exposed to CVE-2026-109618 and CVE-2026-109619. Upgrade to 8.5.12 or later, then restart PHP.
Patched from PHP 8.4.27
Vulnerable8.4.0 to 8.4.26
Patched8.4.27 and newer
Versions below 8.4.27 are exposed to CVE-2026-109618 and CVE-2026-109619. Upgrade to 8.4.27 or later, then restart PHP.
Patched from PHP 8.3.36
Vulnerable8.3.0 to 8.3.35
Patched8.3.36 and newer
Versions below 8.3.36 are exposed to CVE-2026-109618 and CVE-2026-109619. Upgrade to 8.3.36 or later, then restart PHP.
Patched from PHP 8.2.35
Vulnerable8.2.0 to 8.2.34
Patched8.2.35 and newer
Versions below 8.2.35 are exposed to CVE-2026-109618 and CVE-2026-109619. Upgrade to 8.2.35 or later, then restart PHP.
No official update
No official fix7.4, 8.0, 8.1
Move to8.2 to 8.5
The PHP security team published source backports for these old branches, but moving to a supported branch is the safer route.
1Upgrade PHP to the fixed release for your branch.
2Restart PHP so the new build actually runs.
3Do not rely on a firewall or a settings change as the fix.

Also Read: Bitcoin Still 34% Below ATH After 43% Rebound. What Factors Could Drive the Next BTC Rally?

What Comes Next After Black October 2026

Experts expect the Black October hack to linger for weeks, if not longer. Hackers keep scanning for servers that missed the update, and security firms are still checking more than 200 proof-of-concept exploits. For site owners, a PHP vulnerability test and a quick upgrade come first. For everyday users, experts advise strong passwords, a password manager and no panic.

Banks face a slower fix. Liability for payments an AI agent makes is still unresolved, and regulators have privately backed the blocks, so the AI agent restrictions of Black October 2026 look set to stay for now. Read-only access remains open, with Citi still letting approved open-banking providers view account data. Crypto platforms face rule pressure too, with BNB issuer Binance facing MiCA scrutiny.

Vladimir Popescu

Written by Vladimir Popescu

Vladimir Popescu leads editorial coverage at MarketCapOf, with over 8 years in financial and tech journalism. He previously held editorial leadership roles at Watcher Guru and Windows Report, and has been cited by Forbes for his crypto market coverage.

Read Next