Nobody broke into CNN, Zoom, the BBC, or IKEA on November 16. Their websites served malicious code to visitors anyway.
A supply-chain attack is an attack that reaches its targets by compromising a supplier they all trust, instead of attacking each target directly. A third-party script is code that a website loads from another company's servers every time a page opens - for analytics, chat, testing, ads, or payments.
That was the story of the week, and it arrived in a week already full of them: a Microsoft outage, a nationwide ground stop, a bank slowdown, and two federal-level warnings about AI-driven attacks. It is easy to read all of that as one big wave. It was not. Here is what each one was, from the organizations that own the facts.
*Current as of November 17, 2026, 4:00 p.m. ET.*
One vendor was exploited, and its customers' websites delivered the result.
Optimizely makes a tool that lets companies test different versions of a web page. To use it, a company adds a small Optimizely script to its site. That script loads from Optimizely's servers on every page view.
On November 16, someone changed what those scripts contained. Optimizely's status page says "an unauthorized party exploited a vulnerability in Experimentation" and used it to add malicious JavaScript to some customer projects (Optimizely Status). Optimizely says the vulnerability is fixed and the injected code removed.
Security researcher Scott Helme and his team at Report URI found it. They checked 1,611 Optimizely scripts and found 188 carrying the code, belonging to 178 organizations (Report URI). Banks and financial firms were the largest group, at 32. Report URI says the real number is likely higher, because it could only check the scripts it could find.
No, and the difference matters.
Nothing in Report URI's account says attackers got into the systems of CNN, Zoom, or any other named organization. The code came from the vendor, loaded from the vendor's own servers with a valid security certificate. Each website did exactly what it was built to do: fetch the script and run it.
That is the uncomfortable part. A website can be turned against its visitors without its own code or servers being touched. Optimizely's own website and login page carried the code too.
According to Report URI, four things.
Report URI traced about $7,040 in cryptocurrency to the attacker's wallets that day. The full impact is not known.
No. All three were explained by the organizations themselves as their own equipment or software.
A worldwide Microsoft 365 outage begins. Microsoft later attributes it to a latent software defect in its own network gateway, not an attack.
A telecommunications failure leads the FAA to halt departures nationwide. The FAA says data flooded its network at about 1,000 connection attempts every 4 to 5 seconds.
The FBI issues a FLASH alert on ARTEX, an AI-driven tool attackers are using to automate break-ins.
First malicious code seen in an Optimizely script, on a BBC project.
The attacker adds a payment card skimmer to the code.
Chase reports slow transactions and blames a software bug in its own hardware systems, with no evidence of a cyber cause.
Google's threat intelligence team reports that attackers have moved from prompting AI by hand to running autonomous AI attack frameworks.
One infected script remains, down from 169 an hour earlier.
Optimizely confirms a vulnerability was exploited, says it is fixed and the injected code removed.
Three failures. No intruder in any of the three accounts.
Speed, and the systems nobody is watching.
On November 13, the FBI issued an alert about ARTEX, an open-source tool built for security testing that attackers now use to automate break-ins (FBI FLASH-20261113-001). The FBI says it has been used since at least August 2026, with some intrusions going "from initial targeting to privileged access in under three hours."
Two details in that alert matter more than the AI headline.
On November 16, Google's threat intelligence team reported the same shift: attackers moving beyond typing prompts by hand to running autonomous, multi-agent attack frameworks, ARTEX among them (Google Threat Intelligence Group).
One thing to keep straight: neither Optimizely nor Report URI ties the November 16 attack to AI. These are separate stories that landed in the same week.
Dependency.
Every story this week is about something an organization relied on and did not control. A gateway. A router. A hardware system. A vendor's script. A supplier's portal.
The outages show what happens when a dependency fails. The Optimizely attack shows what happens when a dependency is turned against you. The FBI alert says attackers are now automating the search for the weakest one.
You cannot remove your dependencies. You can know what they are.
Report URI's advice for anyone who visited an affected site on November 16:
The full list of organizations is in Report URI's post.
Your website almost certainly runs code you did not write. A chat widget. A booking tool. An analytics tag. A review badge. A social media pixel. Each one is a third-party script, and each one can change without anyone at your company touching the site.
Ask whoever built or manages your website four questions.
That last number is the lesson. The control exists. Most sites, including some of the largest in the world, had not set it tightly enough to matter.
Knowing what you depend on, and who is watching it, is the work.
Want a quick read on where you stand? The Security Self-Check takes a few minutes.
You are not Zoom. Your website still works the same way theirs does.
A 15-person office usually has a site built once, by someone outside the company, with a handful of add-ons installed along the way. Nobody has listed them since. That list is the first thing to get.
Then run the same exercise for the rest of the business. Which vendors can change something your customers see? Which ones hold your data? If your email, your bank, or your booking system went down for a day, who would you call, and how would you keep working?
None of this takes new software. It takes one afternoon and a written list.
On the Treasure Coast, the sites most exposed to this are the ones that take money or personal details through a form: medical and dental intake, online payments, booking and deposits. If a script on one of those pages is changed, Florida's breach notification deadlines may apply - the Florida section of our DFIR page covers who must be told and when.
Start with the four questions. If your web person cannot answer the first one, that is your first gap.
Disclaimer. This article is provided for general information only. It is not legal, regulatory, or professional advice, and reading it does not create a client relationship with WOM Technology Management Group. Regulations, threats, and vendor products change; specific obligations depend on your industry, jurisdiction, contracts, and data. Verify anything you plan to rely on against the primary source and consult qualified counsel or a security professional before acting.
Sources are cited as of the last-reviewed date shown above. Where a linked source has moved or been withdrawn, the citation reflects what was verifiable at review time.