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.*

What happened on November 16?

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.

Were those companies hacked?

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.

What did the code do to visitors?

According to Report URI, four things.

  1. Swapped cryptocurrency addresses. If a visitor copied or entered a wallet address, the code replaced it with the attacker's.
  2. Skimmed payment cards. From the afternoon of November 16, it captured card numbers, expiry dates, and security codes typed into forms on the site itself. Payment forms hosted by a separate payment provider were not affected.
  3. Took cookies and screenshots. It sent the page address, some cookies, and a screenshot when the page mentioned wallets or payments.
  4. Targeted iPhones and iPads. It tried to deliver exploit kits to devices on older versions of iOS.

Report URI traced about $7,040 in cryptocurrency to the attacker's wallets that day. The full impact is not known.

Were last week's outages part of this?

No. All three were explained by the organizations themselves as their own equipment or software.

  1. Nov 12
    Microsoft

    A worldwide Microsoft 365 outage begins. Microsoft later attributes it to a latent software defect in its own network gateway, not an attack.

  2. Nov 13, about 3:30 p.m. ET
    FAA

    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.

  3. Nov 13
    FBI

    The FBI issues a FLASH alert on ARTEX, an AI-driven tool attackers are using to automate break-ins.

  4. Nov 16, 04:21 UTC
    Report URI

    First malicious code seen in an Optimizely script, on a BBC project.

  5. Nov 16, 13:43 UTC
    Report URI

    The attacker adds a payment card skimmer to the code.

  6. Nov 16
    Chase

    Chase reports slow transactions and blames a software bug in its own hardware systems, with no evidence of a cyber cause.

  7. Nov 16
    Google

    Google's threat intelligence team reports that attackers have moved from prompting AI by hand to running autonomous AI attack frameworks.

  8. Nov 16, 21:52 UTC
    Report URI

    One infected script remains, down from 169 an hour earlier.

  9. Nov 17, 01:02 UTC
    Optimizely

    Optimizely confirms a vulnerability was exploited, says it is fixed and the injected code removed.

  • Microsoft, November 12: Microsoft's summary of its preliminary report names three factors behind the outage in the network gateway that sits in front of many Microsoft 365 services. The first was a latent defect that caused servers to become overwhelmed under certain load (Charles Lamanna, Microsoft). We covered the day itself in our outage analysis.
  • FAA, November 13: The FAA says its legacy equipment became unstable when data flooded its telecommunications network at about 1,000 connection attempts every 4 to 5 seconds, disrupting aircraft communications and radar feeds (FAA). Operators canceled about 12,462 flights that day. The investigation is still open.
  • Chase, November 16: Chase blamed a software bug in its on-premise hardware systems and said "there is no evidence this is cyber-related" (Chase). It said other banks may have been affected only where Chase was a party to the transaction.

Three failures. No intruder in any of the three accounts.

What are the FBI and Google warning about?

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.

  • Where it goes first: partner and supplier portals, legacy services, third-party integrations, and other systems that get less attention than the front door.
  • How it travels: through weaker vendors into the organizations they serve. The FBI cites one supply-chain compromise that gave attackers access to more than 2,250 downstream customer environments.

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.

What do all of these have in common?

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.

I visited one of those sites. What should I do?

Report URI's advice for anyone who visited an affected site on November 16:

  1. Update your iPhone or iPad. Report URI says the exploit kit's own notes indicate iOS 18.7.3 and later, and iOS 26.3 and later, are patched.
  2. Watch your card statements if you typed card details into one of those sites that day.
  3. Verify any cryptocurrency address before sending a payment.

The full list of organizations is in Report URI's post.

How do I find out what my own website loads?

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.

  1. What outside services does our site load? Get the list in writing, with the company behind each one.
  2. Which ones do we still use? Remove the rest. Every script you delete is one less company that can change your website.
  3. Who takes our card payments? A payment page or form hosted by your payment provider keeps card entry off your own pages. PCI DSS requirements 6.4.3 and 11.6.1, in effect since March 31, 2025, cover the scripts that run on payment pages (PCI Security Standards Council).
  4. Do we have a Content Security Policy? A Content Security Policy is a set of instructions a website gives the browser listing which sources may run code on the page and where data may be sent. Report URI checked the affected organizations' own sites: 68 had no policy at all, 50 had one that let both the code and the data theft through, and 24 had one strict enough to block it.

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.

How WOM helps

Knowing what you depend on, and who is watching it, is the work.

  • Vendor oversight: Governance, Risk & Compliance includes knowing which third parties touch your systems and data, and having someone review that access on a schedule.
  • An independent look: A Third-Party Assessment reviews what is actually configured, including vendor access, by an assessor with no role in your daily IT.
  • Watching for what gets through: Cyber Risk Management covers vendor risk, monitoring, and the plan for the first hour.
  • When it has already happened: Digital Forensics & Incident Response finds what was reached and what you are required to report. If it is happening now, go to /under-attack or call +1 (888) 966-7228.

Want a quick read on where you stand? The Security Self-Check takes a few minutes.