On Monday 16 November 2026, attackers used Optimizely, a popular website testing service, to slip malicious code onto the websites of 178 organisations, including the BBC, CNN, Zoom and HSBC. The attack, which researchers have named OPTIMJACK, is a clear reminder that every third-party script on a website is a door someone else holds the key to.

What happened?
Optimizely helps businesses test changes to their websites, such as trying out two versions of a page to see which works better. To do that, its customers add a small Optimizely script to their sites, which loads from Optimizely's own servers.
The attackers found a flaw in Optimizely's account sign-up process and used it to insert malicious JavaScript into customers' scripts. Because the code was delivered through Optimizely's trusted network, the affected websites passed it straight on to their visitors. Optimizely confirmed the incident the following day, saying it had fixed the flaw, removed the malicious code and notified the organisations affected.
Security firm Report URI, which spotted the attack, checked 1,611 Optimizely scripts and found 188 carrying the malware.
What did the malware do?
- It swapped cryptocurrency wallet addresses for the attackers' own, so payments went to the wrong place.
- It captured payment card details typed into forms on affected pages.
- It collected cookies and screenshots from visitors' browsers.
- It tried to deliver exploit kits to iPhones and iPads.
Reports suggest around US$7,000 reached the attackers' cryptocurrency wallets on the day. How many payment cards were exposed isn't yet known.
Card payments taken through a hosted payment form, where the card fields load from the payment provider's own servers rather than the website itself, are much harder for this kind of malware to reach.
What should visitors do?
If you visited a well-known website on 16 November and made a cryptocurrency payment, check that it went to the right address. It's also worth keeping an eye on your card statements over the next few weeks and reporting anything unfamiliar to your bank.
Why we keep third-party scripts to a minimum
This attack didn't need to break into the BBC or CNN. It only needed to compromise one service those websites trusted. Every external script a website loads adds another company whose security you're relying on.
That's why we keep third-party scripts to a minimum on the websites we build. We use Google tools such as Analytics, Google Ads and reCAPTCHA, and some of our clients' websites use tawk.to for live chat. Beyond that, we avoid unnecessary plugins and external tools, which keeps websites simpler, faster and less exposed to incidents like this one.
Security headers such as a Content Security Policy help by limiting where a website can load scripts from, but they wouldn't have stopped this attack on their own, because the malicious code came from a domain the websites already trusted. The most reliable protection is simply to load fewer scripts.
If you'd like us to review the third-party scripts on your website, get in touch or call us on 020 3916 5890.
Sources: Help Net Security, SecurityWeek, Malwarebytes.





























