Phi PlusAdvisory
Insights · Technology and AI

Nobody clicked a bad link


Careful staff could not have stopped the attack of 16 November 2026. It came in through a supplier, which makes it a question about who owns what in your business.

By Victor Barron18 November 20263 minute read

On Monday 16 November 2026, websites belonging to 178 organisations served malicious code to their visitors. Report URI, the security firm that found it, lists the BBC, CNN, Salesforce and Equifax among them. The visitors did nothing unusual. They opened a site they knew, saw the padlock in the address bar and carried on.

In numbers
178
organisations whose websites served the code
24
sites tested had rules that blocked it
72
hours to report a breach in the UK

Report URI, 16 November 2026, and the Information Commissioner’s Office.

What happened

None of those organisations had to be broken into. Each used Optimizely, a tool for testing different versions of a web page. According to Report URI, the attacker added code inside customers’ Optimizely projects, so it reached visitors from Optimizely’s own servers, which those websites already trusted. Optimizely says a weakness in its product was exploited, and that it has fixed the weakness and removed the code.

The report describes code built to copy card numbers typed into a website’s own payment form, redirect cryptocurrency payments and attack older iPhones and iPads. About 7,000 US dollars in cryptocurrency reached the attacker, on the report’s count, and there is no public figure for cards or logins.

Being on the list means only that an organisation used the tool. Equifax said it had stopped using Optimizely and had found no evidence of any compromise to its systems or its data. Salesforce said it was investigating and had switched the scripts off.

If you or your team used one of those sites that day, Report URI’s advice is to update any iPhone or iPad and to watch your card statements.

Why careful staff were not enough

We teach people to be wary of strange links and unexpected attachments. That advice still holds, and it would have changed nothing on 16 November. The websites were genuine. Only the people responsible for each website and its suppliers were in a position to catch it.

Some of them had prepared. A website can give the browser a set of rules, known as a Content Security Policy, about which code may run and where a page may send data. When Report URI tested the affected sites, 24 had rules that blocked the code and 68 had no such rules at all.

The suppliers inside your business

You may never have heard of Optimizely, but your business probably relies on something like it. A booking form, a chat window, a payment button, the payroll portal your staff sign in to: each one is another company’s code or system working inside yours. Pay and bank details are among the most personal data a company holds, and they often sit with a payroll or benefits provider.

The AI (artificial intelligence) tools you may be adding are suppliers too. The UK’s National Cyber Security Centre advises giving an AI agent, meaning a tool that can take actions for you, only the permissions its task needs.

What to do this week

If your own website uses Optimizely, start with the checks in Report URI’s report. Then, whatever tools you use:

  1. List every outside supplier whose code runs on your website, starting with the pages where people sign in or pay.
  2. Limit who can change that code, and protect those accounts with a second sign in step.
  3. Ask whoever looks after your website about a Content Security Policy with reporting switched on.
  4. Decide now who starts the clock if something goes wrong.

The clock in that last step is a legal one. In the UK, a personal data breach must be reported to the Information Commissioner’s Office (ICO), the data protection regulator, within 72 hours of your becoming aware of it, unless it is unlikely to put people at risk. The ICO’s guide advises starting a log straight away.

If the breach happens at a supplier that handles personal data for you, the supplier must tell you without undue delay and the duty to report stays with you. If your customers or staff are outside the UK, other regulators’ rules may apply too, and their deadlines can differ.

I work on how organisations are structured and paid, so I read this event as a question of ownership. Security specialists can set up the protection.

Someone in your business still has to be named beside each supplier, and someone beside those 72 hours.

Working out who owns what is part of what I do at Phi Plus Ltd. See organisation and business diagnosis.

The next question

Could your managers explain how pay is decided?

New rules in the UK and the European Union will make employers say what they pay. Explaining each figure is the harder part.

Read the next article

This article gives general information and is not legal or security advice. The facts were checked on 18 November 2026 and the investigation is still open, so details may change. If you represent an organisation named here and believe something is wrong, write to hello@phiplus.co.uk.

Sources

  1. Report URI: World’s Largest Brands Infected With Malware Via Optimizely, 16 November 2026, updated 17 November 2026.
  2. Optimizely Service Status: Web Experimentation Security Incident, 17 November 2026.
  3. KPRC 2 Click2Houston: report carrying the Equifax statement, 17 November 2026.
  4. CSO Online: report carrying the Salesforce statement, 17 November 2026.
  5. Information Commissioner’s Office: 72 hours, how to respond to a personal data breach.
  6. Information Commissioner’s Office: Personal data breaches, a guide.
  7. National Cyber Security Centre: Managing the cyber risk of agentic AI, 20 August 2026.

Glossary

© 2026 Phi Plus Ltd. All rights reserved. phiplus.co.uk

More insights