Optimizely scripts hijacked: what it means for your business website
Hijacked Optimizely code served malware to visitors of 178 major websites on November 16, 2026. The lesson for any business website that loads outside scripts.
On November 16, 2026, visitors to some of the best-known websites in the world, including the BBC, CNN, Zoom and Salesforce, were quietly served malicious code. The sites themselves were not hacked. The code arrived through Optimizely Web Experimentation, a third-party tool those sites load to run A/B tests. Most small businesses do not use Optimizely, but almost every business website loads code from somebody else, which is why this incident is worth ten minutes of your time.

What happened
Help Net Security reports that researchers at Report URI checked 1,611 Optimizely snippets and found malicious code in 188 of them, belonging to 178 organizations. The attacker wrote a small loader into each project's "Project JavaScript" setting and left the rest of the snippet untouched, so it kept loading from Optimizely's own servers and looked trustworthy to visitors' browsers.
The Record reports that Optimizely confirmed a vulnerability in its Experimentation platform was exploited. On its status page the company said it had fixed the flaw, removed the injected code from affected projects and secured affected accounts. The Hacker News describes the payloads as a payment card skimmer, cryptocurrency theft code and exploit kits aimed at iPhones and iPads.
Why a small business should care
Your website probably loads several outside scripts: analytics, a tag manager, a chat widget, a booking or payment form, a review badge, a cookie banner, an advertising pixel. Each one runs with the same power as your own code. If any of those providers, or the account you use to manage them, is compromised, an attacker can change what your visitors see or steal what they type into your forms, without touching your web server at all. Updating your website software, important as it is, does not protect you from this.
What to check this week
- List every outside script your site loads. Ask your web developer, or look at your tag manager and your website's header and footer settings. Write down what each one is for and who in the business owns it.
- Remove what nobody uses. Old A/B testing tools, past campaign pixels and abandoned chat widgets are common. Every script you remove is one less provider you have to trust.
- Lock down the accounts that control them. Your tag manager, analytics, chat and testing accounts can change code on your site. Turn on multifactor sign-in, remove former staff and agencies, and keep the number of people who can publish changes small.
- Keep payment and login forms simple. Pages where customers type card details or passwords should load as little outside code as possible. If you take payments, a hosted checkout page from your payment provider keeps card entry off your own site.
- If you use Optimizely Web, follow the advice in the coverage: review the Project JavaScript and custom code of every project, check the change history, and confirm who can edit them.
And for your staff
Because some of the code targeted iPhones and iPads, this is also a good moment to make sure company phones and tablets are on the latest updates. Our earlier note on Apple's November updates for company iPhones covers how to check.
How we can help
Our cybersecurity service can review what your website and staff accounts depend on, and our patch management keeps devices current. If your site runs on WordPress, see also our post on the WordPress upgrade flaw. Call (213) 986-4855.