Threat Analysis: Optimizely Supply Chain Attack and TfL Oyster Breach, What UK SMBs Need to Know
This is your Daily Threat Analysis for the 19th of November 2026.
Two incidents dominate today’s briefing. Both happened this week. Both involve attackers using trusted third-party infrastructure to reach targets those parties were supposed to serve. Neither required a sophisticated nation-state capability. Both caused significant, documented harm. And both carry direct lessons for UK businesses that think supply chain risk is someone else’s problem.
The Optimizely Incident: 178 Organisations, One Exploited Platform
On the 16th of November 2026, an unauthorised party exploited a vulnerability in Optimizely’s Web Experimentation platform. What they found was a field, the optional Project JavaScript field used in A/B testing configuration, that allowed them to inject arbitrary JavaScript into customer projects. The malicious code was active from 04:21 to 23:11 UTC: just under nineteen hours.
In that window, 188 JavaScript snippets across 178 organisations were compromised. The list of affected sites reads like a who’s who of web traffic: BBC, CNN, Fox News, Zoom, GitLab, IKEA, HSBC, Salesforce. These are not obscure outfits with weak security postures. These are organisations with dedicated security teams. They were hit because they trusted a vendor, and that vendor’s platform was successfully exploited.
The payload was not a single piece of malware. It was a framework. Researchers tracking the campaign, designated OPTIMJACK by ReversingLabs, identified several simultaneous capabilities running against visitors to affected sites:
- Cryptocurrency address replacement: wallet addresses pasted or entered by users were silently swapped for attacker-controlled addresses at the point of submission.
- Payment card skimming: card details entered into first-party forms on affected sites were captured and exfiltrated.
- Cookie and screenshot theft: non-HttpOnly cookies and page screenshots were harvested from visitor sessions.
- iOS exploit kit delivery: Mobile Safari users on iPhone and iPad were silently routed to exploit-kit infrastructure without any user interaction.
That last item warrants particular attention. Zimperium’s research identifies the iOS exploitation infrastructure as the Coruna and DarkSword exploit kits, delivered to mobile visitors via the poisoned JavaScript without any click, download prompt, or other user action. The CVE involved in the iOS component is CVE-2022-48503, a WebKit vulnerability. The fact that a 2022 CVE is still being weaponised in a 2026 campaign tells you something about the patch discipline of the devices in scope.
Censys researchers tracking the campaign infrastructure identified the threat actors behind the card skimmer component as a group they designate MCH, and a separate iOS exploitation group called Caishen. This was not one actor running one campaign. It was multiple threat actors operating simultaneously through the same compromised delivery mechanism.
What the coverage is not saying
Optimizely is a widely deployed A/B testing and personalisation platform. The nature of how such platforms work is that their JavaScript runs on your website, in your visitors’ browsers, with the implicit trust of your domain. When you embed a tag manager, an analytics snippet, a chat widget, or a testing platform, you are delegating code execution authority to that vendor. If that vendor’s platform is compromised, your visitors are exposed, and your brand carries the reputational cost.
The NCSC has published guidance on this category of risk. The term in common use is a ‘formjacking’ or ‘web skimming’ attack when focused on payment data, but the Optimizely incident goes significantly further than that framing suggests. This is a supply chain attack that turned a trusted JavaScript delivery mechanism into a multi-payload malware distribution platform.
If your IT provider tells you this does not affect you because you do not use Optimizely, ask them how many third-party script tags your customer-facing websites load, who controls each of those scripts, and what your monitoring looks like for unexpected changes to that code.
What to do
The immediate priorities are:
-
Audit your third-party JavaScript dependencies. List every external script loaded on your customer-facing properties. If you cannot produce that list from memory or existing documentation, your exposure is unknown.
-
Check your Content Security Policy (CSP). A properly configured CSP restricts which domains are permitted to execute JavaScript in your visitors’ browsers. It does not prevent supply chain compromise at the vendor level, but it limits what injected code can do, specifically, it can block exfiltration to attacker-controlled domains. If your site does not have a CSP, this week is a reasonable time to change that.
-
Review your SaaS vendor list against the 178 affected organisations. SecurityScorecard has published guidance for affected customers. If any of your vendors or business partners were running Optimizely Web Experimentation during the 16th of November, review what data those platforms could have been exposed to.
-
Brief your finance and procurement teams on the cryptocurrency swap capability. If anyone in your organisation processes cryptocurrency transactions, including supplier payments, the address-swap payload is a direct financial threat that does not require any malware on your internal systems.
TfL Oyster: Another Breach, the Same Pattern
Transport for London took its Oyster photocard website offline on the 19th of November 2026 after attackers compromised customer accounts. Around 265,000 customers are potentially affected.
The Oyster photocard service handles accounts for young people, older residents, and people with disabilities who use concessionary travel passes in London. The data associated with these accounts includes names, addresses, and payment details linked to travel cards. For the individuals affected, particularly those whose accounts hold details of dependants or vulnerable family members, the exposure is not abstract.
This is not TfL’s first security incident. The organisation has had a difficult few years on the security front. The pattern, customer-facing web platform, credential compromise, delayed public disclosure, is familiar. What is worth noting here is that the method appears to be account compromise rather than a vulnerability in TfL’s infrastructure specifically. The implication is credential stuffing or similar techniques using credentials obtained elsewhere: a consequence of password reuse across services and the volume of credential data available from previous breaches.
The supply chain parallel
The same week, a cyberattack on Wellington IT, a service provider to Irish credit unions, exposed payee data across forty financial institutions. Ireland’s minister for the relevant portfolio described the notification delay as “not acceptable” after an October attack was disclosed only in November. The affected credit unions are customers of Wellington IT. They did not suffer a direct breach of their own systems. Their exposure came through a provider they trusted.
That is the same structural problem as the Optimizely incident, expressed in a financial services context. The attack surface is not just your systems. It is every system your operations depend on.
The Common Thread
Three incidents in the same week, Optimizely, TfL, Wellington IT, all involving third-party or supply chain exposure. None of them required exotic capabilities. All of them caused documented harm to real customers.
The NCSC published guidance on supply chain security risks several years ago. The fact we are still having this conversation tells you everything about how seriously organisations take it. Supply chain security is not a theoretical concern for large enterprises. It is the attack surface that scales down to every business that uses a SaaS platform, embeds a third-party script, or relies on a managed service provider for any part of their operations.
If your business sells through a website, processes customer data, or accepts payment online, the Optimizely incident is directly relevant to you, not because you use Optimizely, but because you almost certainly run code from vendors you have not audited recently.
Sources
If Threat Analysis is useful to you, follow the show wherever you listen so tomorrow’s briefing lands automatically, and pass it to someone who needs the heads-up.