On Monday 16 November 2026, visitors to Zoom, the BBC, CNN, Salesforce, GitLab, IKEA and more than 170 other major websites were served malware. None of those companies was hacked. The attack came through a script they all loaded from the same outside provider, Optimizely, a platform businesses use to test and personalise their websites. If your own website loads analytics, a chat widget, a booking tool or a marketing pixel, it loads the same kind of script, and this is the week to know exactly which ones are running on your pages.
The campaign has been named Optimjack by researcher Amirul Iman. It was found by security researcher Scott Helme of Report URI, and the scale is what makes it a story for every website owner, not just for the big brands. Your site does not need to be famous to be exposed. It only needs to load a script from a provider that gets compromised.
What happened
Optimizely is a digital experience and experimentation platform. Businesses use it to run tests and personalise their websites, and its JavaScript files load into their webpages to do that work. Attackers inserted malicious code into Optimizely customer projects, so the JavaScript files hosted on Optimizely’s own content delivery network loaded malware on every website that used the service.
Helme checked 1,611 Optimizely scripts and found 188 infected files belonging to 178 organisations. BleepingComputer independently confirmed that the malicious script loaded, or tried to load, on many of them, including Zoom, KLM, GitLab, the BBC, CNN, American Girl, Smartsheet, Stamps.com and Salesforce. Other affected websites include Fox News, Mutual of Omaha, American Eagle, Air France, Change.org, Optimizely itself, HSBC Insurance, Bitly, IG and UNICEF USA. The first injection Helme found was in the BBC’s snippet at 04:21 UTC on Monday 16 November.
The injected code loaded a further malicious script from an attacker-controlled domain, 1688360[.]cc/track.js. Some infected files pointed at that address directly, while others hid it with Base64 encoding. One variation could even run an embedded copy of the malicious code if the remote script was blocked.
Once it loaded, the malware did four things. It watched webpages for cryptocurrency wallet addresses and replaced them with attacker-controlled addresses, so a visitor who copied an address and pasted it into a payment could send money to the attacker. It searched for credit card numbers, expiry dates and security codes typed into web forms and tried to send them to the attacker’s server. It loaded code linked to the Coruna and DarkSword exploit kits, which target iPhones and iPads. And it collected browser cookies, page addresses and screenshots.
The wallets linked to the malware received about $7,000 in cryptocurrency on 16 November, according to BleepingComputer. Cointelegraph put the figure at about $7,100 from its own check of blockchain records, while StepSecurity counted about $6,600 and noted that some of the wallet addresses had activity before the attack. Helme said it could not be determined how many payment card details or cookies had reached the attackers’ server.
Cleanup moved fast once the campaign was found. By 21:52 UTC on 16 November, only one of the 188 infected files still contained the malicious code. Ledger’s snippet was cleaned at about 20:41 UTC.
Optimizely confirmed to Cointelegraph that an unauthorised party exploited a vulnerability in its Experimentation account signup flow to add malicious JavaScript to some customer projects. The company said it has blocked access to the vulnerable path, deployed a fix, removed the injected code from affected projects, ended active sessions, revoked tokens, reset access for affected user accounts, blocked code delivery in Cloudflare, and notified all affected customers. It is still investigating. How the attackers gained access to modify so many different customer projects is still unknown.
What it means for a small business
The lesson of this attack is simple. Your website’s security is only as strong as the weakest script it loads. A typical small business website loads analytics, a chat widget, a booking form, a payment button, a social feed and a cookie banner. Each of those scripts runs with full access to your pages. If any one provider is compromised, your visitors can be served malware and your checkout can be skimmed, while your own server, your WordPress install and your passwords are all untouched.
That is also why this story is different from the usual advice to update WordPress and change your password. No WordPress update would have stopped it, because the malicious code never touched WordPress. It arrived through a trusted script that the website owner had deliberately added.
One detail matters for anyone who takes payments online. StepSecurity found that the skimmer could not read payment fields isolated inside a third-party payment provider’s cross-origin frames. If your checkout hands the card fields to your payment provider’s own secure frame, those fields were out of this skimmer’s reach. If customers type card details directly into a form on your own page, they were not.
The attack also ran for most of a working day before it was cleaned up, so the risk was not theoretical. A visitor who opened an affected site on Monday morning and copied a crypto wallet address could have pasted the attacker’s address instead. That is a small detail with a large consequence, and it is the kind of thing a customer would blame on the website they visited.
This is not a reason to remove every third-party tool from your site. Most of them do useful work. It is a reason to know what is on your site, to keep the list short, and to check the ones that can see your checkout.
What to do about it
Work through this list today, in order.
- Ask your developer or host for a list of every third-party script your website loads, and remove any you do not use or cannot name. Most small business sites carry scripts they forgot about.
- If you use Optimizely, open your Optimizely project’s Project JavaScript today and look for any script from a domain you do not own, or ask your developer to check it. Optimizely says it has removed the injected code and fixed the flaw, but check your own project anyway.
- Check your checkout. Ask your payment provider whether card details are typed into your own page or inside the provider’s own secure frame. Fields inside the provider’s frame were out of reach of this skimmer.
- Ask your developer to set up a Content Security Policy that only allows scripts from domains you approve. It does not stop every attack, but it stops a script loading from an unknown domain like the one used here.
- If you or a customer copied a cryptocurrency wallet address from a major website on Monday 16 November, check the address before sending anything. The clipper swapped addresses in the clipboard, and the wrong address sends the payment to the attacker.
- Keep phones updated. The payload also targeted iPhones and iPads, so install the latest iOS update when it is offered.
If you run a website for customers in Pakistan, the United Kingdom or the United States, the same checks apply. The affected brands were global, and the scripts that carry this risk are the same ones small businesses use everywhere.
Related reading
- Apache Fixed a Critical Web Server Flaw. Your WordPress Update Cannot Fix It
- An AI Hacking Tool Targeted 2,250 Microsoft 365 Accounts. Your Password Was Never the Target
- PHP2Shell: The Critical Website Flaw Your WordPress Update Cannot Fix
How Digilistan can help
Digilistan builds and maintains websites for small businesses, and our web development service covers the build, the third-party tools on it and the checks that keep it safe. Our hosting and setup service watches for updates like this and deals with your host on your behalf. If you want someone to audit the scripts on your site and remove the ones you do not need, that is the work we do.
Sources
- BleepingComputer, Optimizely supply chain attack infects major brands’ sites with malware, 16 November 2026
- Cointelegraph, Hackers inject credit card, crypto-stealing malware into 178 major websites, 17 November 2026
