The Optimizely hack explained like you're five

Nicolas Rak
Nicolas Rak
Founder & Webflow Developer
Dev Diaries
Published
November 17, 2026
Last updated
November 17, 2026
Read time
6
​
No attention span?

Summarize this article with AI.

​
AI summary
On November 16, 2026, attackers used a flaw in Optimizely, an A/B testing tool, to push malicious code onto around 178 websites including Zoom, CNN and HSBC. The code swapped crypto wallet addresses, stole card details and cookies, and targeted older iPhones. Any third-party script that can change your website, especially Google Tag Manager, carries the same type of risk, so the first steps are removing unused scripts and limiting who can publish. A Content Security Policy blocks most of this, and on Webflow you can add one through Enterprise security headers or a reverse proxy.
On this page

On November 16, 2026, visitors to Zoom, CNN, the BBC, HSBC, IKEA and around 170 other big-name websites got served malware for a good part of the day. Nobody hacked those websites directly. The attackers got in through a marketing tool those companies had installed: Optimizely.

If you're a founder or someone with a simple marketing website, this one is worth five minutes. Even if you probably don’t use Optimizely, it’s good to understand how these things work. You don’t want to be the next site that serves malicious code by accident. Let me explain in layman’s terms, no developer background needed.

If you can't explain it simply, you don't understand it well enough

What is Optimizely?

Optimizely is an A/B testing tool. Runs on the same logic as Webflow’s Optimize (which is a different tool). Your marketing team pastes one line of code into the website, then runs experiments from a dashboard. For example, they want to show a different heading for 50% of the visitors to test which works better.

What happened, explained in simple terms

To do A/B testing, the Optimizely code (aka script) needs to run in your browser (aka client-side JavaScript) and rewrite the text very quickly as the page loads. Now that’s an easy 1-liner code. However, that means you’re allowing a third-party script to run and edit your website to change some text and button colors.

That’s what malicious actors abused. They ran their own script, which didn’t just replace the heading text and the button colors, but screenshotted your browser, copy-pasted your autofilled credit card details and rewrote crypto wallet addresses to redirect an outgoing payment to their own wallet.

Optimizely says the attacker used a security flaw in their product to add their own code to customers' experiments. Optimizely's servers then delivered that code to visitors, the same way they deliver every A/B test. To the visitor's browser it looked completely normal, because it came from a source the website already trusted.

What the malicious code did

According to the security researchers who caught it (Report URI, StepSecurity, Cynet), the code did four things:

  • Swapped crypto wallet addresses. You copy a wallet address to send money, you paste the attacker's. Make sure you double check what you copy!
  • Stole card details. It read card numbers as people typed them into the site's forms.
  • Stole login cookies. Some of these can be used to take over a logged-in session.
  • Attacked iPhones. It quietly loaded code aimed at older, unpatched iOS versions.

Want the nitty-gritty details? Scott Helme at Report URI published a full technical breakdown with the timeline, the code and which security settings held up. It's a great read but only if you’re a developer or a tech person with 30 mins to spare.

"But isn't my browser supposed to protect me?"

Fair question. Your browser does protect you, just not from this.

The browser stops a website from touching your computer: your files, your other apps, your other tabs. What it doesn't do is stop a website from reading itself. Any code running on a page has the same powers as the website's own code on that page. It can:

  • read whatever you type into a form, as you type it
  • change what's on the screen
  • change what you copy
  • send all of that somewhere else

The browser can't tell "the site's real code" apart from "code that sneaked in through a trusted tool". From its point of view, it's all the same website.

And no, the dots in a password field don't help. They only hide the text from someone looking over your shoulder. Your real password can still be read by any script on the page, behind the scenes.

Why this matters even if you never touched Optimizely

Open your website's settings and look at what's loading on every page. On a typical startup marketing site I'd expect something like:

  • Google Tag Manager
  • Google Analytics
  • a heatmap tool like Hotjar or Microsoft Clarity
  • a chat widget
  • a cookie banner
  • the LinkedIn and Meta ad pixels
  • maybe an A/B testing tool

Google Tag Manager especially: anyone with publish access to your GTM account can put any code they want on every page of your site.

You don't need to panic and remove everything. You need to know who has what access. Maybe don’t give full publish access to that random freelancer you just met online who has no profile picture or reviews. Give him edit access while you or your developer review each publish.

I'm on Webflow. Am I affected?

Optimizely isn't built into Webflow. It's only on your site if someone added it on purpose, through custom code or the Optimizely integration. If you're not sure, check Site settings → Custom code and your page-level custom code, or ask whoever runs your marketing. Or realistically, ask Claude to crawl your site’s code and figure out if you’re using Optimizely.

Webflow has its own testing tool, Webflow Optimize, built on Intellimize (a company Webflow acquired in 2024). It's a separate product on separate infrastructure, and it wasn't part of this incident. It is the same type of tool though, so the same rules apply: be careful who can edit experiments.

How to protect your marketing site

Nothing fancy here. These are boring, and they work.

1. Make a list of every script on your site.
Your developer or your AI agent can pull this together in 30 mins. Third-party code tends to pile up over the years: an old chat widget, a tracking pixel from a SaaS you stopped using in 2023.

2. Remove what you don't use.
Every script you delete is one less key out there. Bonus: your site gets faster!

3. Check who has access to the tools that can change your site.
That means Webflow, Google Tag Manager, your A/B testing tool and anything else that injects code. Remove former employees and old agencies. Turn on two-factor authentication everywhere.

4. Don't handle card details on your own page.
If you take payments, use Stripe Checkout, embedded Stripe fields, Google Pay or Apple Pay. With those, card numbers never actually touch your page, so there's nothing for a skimmer to read.

5. Add a Content Security Policy.
This is the one that actually stopped the attack. A Content Security Policy (CSP) is a short instruction your website sends to the browser: "only run code from these places, and only send data to these places." When the malicious code tried to load its payload from an unknown domain, sites with a strict CSP simply blocked it. The researchers counted 24 sites that were protected this way.

Adding a CSP to a Webflow site

This is where Webflow gets a bit annoying.

On Webflow Enterprise, you can add custom security headers, including a CSP, right in the site settings.

On every other plan, you can't set this header yourself. The fix is a reverse proxy: a thin layer (Cloudflare, for example) that sits in front of your Webflow site and adds the security header to every page before it reaches the visitor. Your site stays on Webflow, you keep editing it the same way, and visitors get the extra protection.

One warning: a CSP needs care. Set it too strict and your chat widget, analytics or forms stop working. Set it too loose and it doesn't protect anything. It takes a proper look at what your site actually loads, and it needs updating whenever marketing adds a new tool.

I’d say that 80% of the readers don’t need custom CSP right now. If you’re a high-risk target, handle sensitive data (like payments or logins) or run at a big scale, you or your CTO are probably already aware of this risk. If not, ask them about it!

Want us to check your site?

Two options, depending on where you are:

  • Free website audit. We review your site's UX, design and conversion, and list every third-party script that loads on it, so you know what's running and what can go. You get the results within 24 hours. Get your free audit.
  • CSP setup for Webflow. If you're in the 20% that needs one, we set up the reverse proxy and Content Security Policy, plus the script and access cleanup that comes before it. No Enterprise plan needed. Book a free call with me.

Sources

Nicolas Rak
Written by
Nicolas Rak
Founder & Webflow Developer
Builds Webflow sites for funded B2B startups. Writes about CMS architecture, SEO and the systems that keep a site editable in year two.
​
LinkedIn

Keep reading

​
All resources
Webflow
November 18, 2026

Webflow for B2B SaaS: Is It the Right Platform for Your Website?

Webflow suits B2B SaaS teams whose marketing ships pages without engineering. Where it works, where it falls short and what to use instead.
Webflow for B2B SaaS: Is It the Right Platform for Your Website?
Dev Diaries
November 16, 2026

Why I Founded GeekyGrowth After Four Years of Freelancing

After four years as an independent Webflow developer, I founded GeekyGrowth to bring branding, design and development together.
Why I Founded GeekyGrowth After Four Years of Freelancing
Webflow
November 13, 2026

How We Structure Webflow CMS So SaaS Sites Scale to Thousands of Pages

How we plan collections, reference fields, templates and components so adding page 300 doesn't take the same work as building page 30.
How We Structure Webflow CMS So SaaS Sites Scale to Thousands of Pages
Migrations
November 12, 2026

WordPress to Webflow: Migrate Without Losing SEO Rankings

How we move SaaS websites from WordPress to Webflow in 6 to 12 weeks while protecting rankings, traffic and backlinks.
WordPress to Webflow: Migrate Without Losing SEO Rankings
talk to a Developer

Skip the sales pitch.

Nicolas Rak, Founder & Lead Dev at GeekyGrowth
Nicolas

Founder & Lead Dev

Book a call with Nicolas
​
Schedule a call

Or send us an e-mail