Optimizely gap: 178 global companies hacked (Zoom, BBC, CNN, IKEA), supply chain attack massive
On November 16, 2026, was detected an attack that affected 178 global companies simultaneously.
It was not a direct attack to each company.
It was an attack on Optimizely, third-party provider for all of them to trust.
In minutes, the malicious JavaScript is executed at millions of user sessions on:
- Zoom
- BBC
- CNN
- Salesforce
- IKEA
- HSBC
- Equifax
- And 171 more
What happened
The attack
FACT (according to Emol, Infobea, and Anadolu Agency):
Optimizely platform (customization digital) was compromised.
FACT: a malicious JavaScript was injected into the platform.
FACT: performed in 178 sites simultaneously the 16-17 November.
What stole
The malware was designed to:
- Steal credit card data from visitors
- Swap addresses of wallets crypto (redirect payments to attacker)
- Steal session cookies (to take control of accounts)
- To capture screenshots (visual access to devices)
- Compromise iPhones (attack mobile devices)
The victims
178 organizations committed:
Well-known companies:
- Zoom (video conferencing, millions of users)
- BBC news, United Kingdom)
- CNN (news, global)
- Salesforce (CRM, enterprises)
- IKEA (retail, global)
- HSBC (bank, global)
- Equifax (financial data, million people)
- Plus 171
The benefit to the attacker
FACT (according to sources): wallets crypto of the attacker received approximately $7,040 USD in a period of 9 hours on the 16th of November.
This is only what is verifiable. The theft of card data + cookies is probably multiples of this.
Why it was possible to
Vulnerability: a Third party without validation
Optimizely is a trusted third party.
Each of the 178 companies relied on that:
- Optimizely is safe
- Optimizely will not be committed
- Optimizely will not inject malware
All these assumptions failed.
The chain of trust failed
Company → Optimizely → Committed → malicious JavaScript in the Company
Each link is critical.
Lack of third-party validation
If these 178 companies have been validated:
- What code is being injected by Optimizely?
- How unexpectedly changed the code?
- Are there any anomalous behavior in applications to Optimizely?
The attack would have been detected before they reach users.
Preventive measures of monitoring
IMPORTANT: The measures that would have prevented this:
1. Validation of content of third party
- Monitor changes in third party scripts
- Compare hashes cryptographic file
- Alert if code changes unexpectedly
2. Monitoring of anomalous behavior of third parties
- How Optimizely is making requests to the new locations?
- How Optimizely is injecting code that was not there before?
- What volume of traffic from Optimizely is anomalous?
3. Correlation of incidents
- If you Zoom detects malicious JavaScript ITSELF is detected in BBC simultaneously
- Pattern: Same-malware on multiple sites at the same time’ = Supply chain attack
- Automate alerts cross between companies
4. Validation of data integrity
- Monitor how visitors are being redirected to wallets unknown
- To detect changes in directions of payment crypto
- Alert if session cookies are being stolen in mass
How to 24Cevent would have helped (incident management)
Measure 1: early Detection of the third-party
When Optimizely was committed:
- 24Cevent in each company: ‘JavaScript Optimizely changed unexpectedly’
- Correlation: the ‘Same change in 178 companies at the same time’
- Analysis: ‘Pattern of supply chain attack in progress’
- Automatic action: Blocking scripts Optimizely in all companies
Attack is content before they reach users.
Step 2: Block data exfiltration
If the JavaScript is already running:
- Monitoring: ‘card Data being sent to unknown location’
- Correlation: ‘massive Volume of data coming out towards the attacker’
- Action: Blocking of communication + off script
Exfiltration is stopped in seconds.
Measure 3: Coordination inter-company
24Cevent could coordinate response among the 178 companies:
- ‘We have detected attack the supply chain affecting 178 companies’
- ‘The containment measures are X’
- ‘Third Optimizely is committed’
- ‘Look at all of your third parties for similar patterns’
Coordinated response in place of each company to investigate in isolation.
Step 4: forensic Analysis, accelerated
Post-incident, 24Cevent automatizaría:
- Timeline exactly when malware was injected
- How many sessions were affected
- How much data was stolen
- What systems were compromised
Results: complete Response in hours, not days.
Pattern emerging: Supply chain is the new attack
We see the pattern clearly:
- The Post: committed Third party
- Uber: committed Third party
- Osaka: committed Third party
- TSMC: cloud Provider committed
- Optimizely: Third party committed to 178 companies
The attack modern is not a direct one. Is via a third party.
Because:
- Easier to engage third party
- A gap = multiple objectives
- Scale exponential
SOURCES CHECKED: