Skip to main content

The Week the Internet Broke

November 19, 2026

If it felt like nothing worked this week, you weren’t imagining it. Between November 10 and 17, Microsoft 365 went dark across 70+ countries, the FAA grounded every flight in the US, Chase customers were locked out of online banking, Apple’s iCloud stumbled, and even the NSA’s classified internal network went down.

What may be surprising though is that almost none of the outages were reported as attacks. The companies involved blame bad config changes, buggy hardware and aging copper.

But that doesn’t mean that the attackers weren’t busy elsewhere, burning zero-days in Outlook, Chrome and N-able, poisoning a JavaScript supply chain used by at least 178 organizations, and dumping fresh victims onto leak sites. Here’s the round-up.

Every operator below has said there’s no evidence of a cyberattack. That hasn’t stopped the rumors.

DateWhat BrokeImpactStated Cause
Nov 17Apple iCloud, App Store, Apple Music, Apple PayWidespread service failures, same day as the NSA outageAn internal update; Apple ruled out a cyberattack
Nov 17NSA Net (NSA’s classified internal network)Internal classified comms down“Temporary degradation during scheduled routine maintenance”; no sign of attack
Nov 17Charles Schwab, Marriott, National Weather Service1,000+ Schwab reports; Marriott logins and bookings; 40-min NWS outageSchwab: page-loading issue. NWS: routine maintenance
Nov 16JPMorgan Chase online banking (plus other banks), United Airlines toolsThousands locked out; pilots’ weight-and-balance apps hitChase: “a software bug in on-premise hardware systems”
Nov 13FAA nationwide ground stop4+ hour stop, thousands of cancellations over two daysA newly installed router, fitted during L3Harris’s copper-to-fiber upgrade, flooded the network
Nov 12–14Microsoft 365 (Outlook, Teams, Exchange, Copilot, Intune)~30 hrs, 70+ countries; ~$7bn lost productivity estimated; NHS cancelled some operationsA latent defect from an earlier network capacity upgrade, triggered by a later network change, took most networking gateway servers offline
Table 1: Major outages, November 12–17, 2026 (newest first)

The FBI is now giving technical support to the FAA and its contractor L3Harris, though it says no hardware has been seized. Expect the “was it really an accident?” threads to keep running.

November’s Patch Tuesday was enormous: Microsoft fixed 1,093 flaws (63 critical), its second month in a row above 1,000. Then the rest of the stack piled on.

•   Outlook, CVE-2026-124194. Exploited before the patch. Open a crafted message file and Outlook connects to the attacker without its usual warning, leaking your NTLMv2 hash. CISA added it to KEV with a November 24 deadline.

•   Chrome, CVE-2026-125350. A use-after-free in XML handling, exploited in the wild. It’s Chrome’s eighth zero-day of 2026.

•   N-able N-central, “4EverAble2Shell”. Exploited within hours of a public PoC to drop crypto miners. At least 21 servers hit, 19 of them already on N-able’s latest emergency patch.

•   Check Point gateways, PHP2Shell + CVE-2026-123039. Attackers came in through Mobile Access portals, escalated to root, and in some cases wiped VMware ESXi hosts. It started in Israel and spread worldwide.

•   SAP “ICM2Shell” (CVE-2026-76964 and CVE-2026-89126, CVSS 10.0) and Apache HTTP Server (CVE-2026-119618, CVSS 9.8). Both allow unauthenticated remote code execution. Apache is fixed in 2.4.71.

The week’s most damaging attacks went through someone else’s software.

•   Optimizely (“OPTIMJACK”). Disclosed November 16. An attacker exploited a flaw in Optimizely’s Experimentation tool and altered the JavaScript snippets customers load on their sites, delivering a card skimmer, a crypto-wallet swapper and iPhone exploit kits. At least 178 organizations were affected, reportedly including Zoom, HSBC and Equifax.

•   ConnectWise ScreenConnect. Attackers got into managed service provider environments and pushed malicious remote-access tools to at least 288 endpoints across 48 organizations, possibly through third-party extensions.

•   La Poste / Maileva. Confirmed November 14: names and postal addresses of 22 million people, roughly a third of France, stolen from the business mailing platform back in September. The victims aren’t Maileva’s customers; they’re the patients, tenants and employees those customers wrote to.

•   TSMC. Employee data exposed via an unnamed cloud provider, with 6.9 GB advertised on a cybercrime forum. TSMC says its own systems are clean.

The Maileva case shows a pattern we keep seeing: the breach happens in September, and people find out in November.

•   Maersk. Confirmed data theft from a legacy system it picked up in an acquisition. The WhiteArmor extortion group claims 100 GB and wants $5 million.

•   Coles. The Australian supermarket chain disclosed a cyber incident on November 16, though it says it has found no evidence that customer, staff or supplier data was taken.

•   N0n ransomware. On November 16 alone the group posted a large batch of claims, among them a US asset manager, an Italian drugmaker, a US ad-tech firm and a US pharmaceutical company. N0n had listed about 221 victims as of November 16, since it first appeared in September.

Leak-site posts are the group’s claims, not confirmed breaches. Wait for the victim to confirm, or check the data itself, before treating the numbers as fact.

This week brought several clear cases and disclosures of attackers using AI to speed up their attacks.

•   On November 12, Palo Alto Unit 42 disclosed an autonomous campaign running DeepSeek and Zhipu GLM agents that, in August and September, carried out 25 operations against at least 19 organizations, compromising 10 of them and exposing more than a million records.

•   At a US retailer, an intruder whose commands were blocked switched to AI-generated scripts. It pulled credentials from SolarWinds Orion config files and reached another server within minutes.

•   Arctic Wolf linked “AntiFox” agents to intrusions that planted IIS webshells, read AWS production secrets and deleted S3 objects, with one AWS burst lasting about 30 minutes.

•   At the end of October, SpyCloud found the WardenStealer and Aoki infostealers taking Claude Code and Codex tokens from infected machines. Developer AI credentials are now standard loot in stealer logs.

Attackers now move in minutes, and defenders who triage in hours are falling behind.

This week’s outages were mostly self-inflicted, while the attacks mostly came in through suppliers. In both cases, organizations got hurt by systems they don’t fully control. A few things worth doing this week:

1. Patch the Outlook and Chrome zero-days now, and block outbound SMB/NTLM to the internet while you’re at it.

2. Audit the third-party JavaScript running on your checkout and login pages. OPTIMJACK won’t be the last skimmer to come in through a trusted snippet.

3. Check your MSP’s remote-access tools (ScreenConnect, N-central) and confirm they’re on the latest builds.

4. Have an offline fallback for email and comms. When Microsoft 365 went down, some NHS staff fell back on paper patient records.

5. Watch the dark web for your own data. Maileva’s victims found out two months late, and leak-site claims like N0n’s often show up before any official disclosure.


At DarkOwl, this is what we track every day; the forum posts, leak sites and stealer logs where a breach often shows up first, sometimes weeks before the press release. Contact us to learn more.

See why DarkOwl is the Leader in Darknet Data