Scan my site freeScan free

Security notices / Optimizely Experimentation supply-chain attack, no CVE, November 16, 2026: card skimmer on 188 snippets at 178 organizations, review scripts and watch cards

Security notice

Does your site use Optimizely Experimentation? Attackers abused a signup flaw on November 16, 2026 and injected a card skimmer into snippets used by 178 organizations.

Last updated: Tuesday, November 17, 2026, 5:39 PM ETStatus: Supply-chain attack disclosed. Optimizely says it fixed the flaw and removed the code. Watch cards.

Optimizely told BleepingComputer that on November 16, 2026 an unauthorized party exploited a vulnerability in the Experimentation account signup flow and added malicious JavaScript to some customer projects. Those projects supply JavaScript that customer websites load, so the injected code ran in visitors' browsers. Scott Helme, as reported by BleepingComputer, found 188 infected Optimizely JavaScript files belonging to 178 organizations after reviewing 1,611 scripts used by the platform. BleepingComputer said it independently confirmed that the malicious script loaded, or tried to load, on a number of those sites, and named brands including Zoom, CNN, Fox News, BBC, Salesforce, GitLab, American Eagle and HSBC Insurance. That is not a complete list. BleepingComputer said the injected code was designed to skim payment card details, swap cryptocurrency addresses, and collect browser cookies, page URLs and screenshots. Optimizely said it blocked access to the vulnerable path, deployed a fix, removed the injected code from affected projects, ended active sessions, revoked tokens, and reset access for affected user accounts. It also said it notified all affected customers and would publish updates at its status page. If you run a site that loads Optimizely Experimentation, review your third-party scripts and Content Security Policy. If you entered payment card details on an affected site on November 16, watch your card accounts. (BleepingComputer, Nov 16)

What happened

Who should worry

You run a website that loads Optimizely Experimentation, or you entered payment card details or made a cryptocurrency transfer on a site that loaded an affected snippet on November 16, 2026. The brand names above are examples from BleepingComputer, not a complete list of affected sites. If your site does not load Optimizely Experimentation, this notice does not apply to you as a site owner, though the lesson about third-party scripts still does.

What to do now

  1. If you run a website, find out whether it loads Optimizely Experimentation. Ask your developer, agency or host to check templates, tag managers and third-party scripts. If it does, follow Optimizely's official updates and review those scripts, especially on checkout and account pages.
  2. Review third-party scripts and Content Security Policy. Ask for a list of every script your checkout and account pages load, including scripts loaded by other scripts. For each, ask who runs it, why it is there, and whether you still need it. Review your Content Security Policy as part of that work. This is our advice, not Optimizely's. We are not claiming any tool, including EverThread, would have stopped this attack.
  3. If you entered payment card details on an affected site on November 16, watch your card accounts. BleepingComputer advised anyone who entered payment card information to monitor their accounts for unauthorized transactions and to contact the card issuer if they notice suspicious activity. If you made a cryptocurrency transfer on an affected site that day, BleepingComputer advised checking that the destination address was not swapped. (BleepingComputer, Nov 16)

What to send your developer, agency or host

On November 16, 2026, attackers abused a vulnerability in Optimizely Experimentation's account signup flow and added malicious JavaScript to customer projects, according to Optimizely as told to BleepingComputer. Scott Helme, as reported by BleepingComputer, found 188 infected snippets belonging to 178 organizations. BleepingComputer said the injected code was designed to skim payment cards, swap cryptocurrency addresses, and collect cookies, page URLs and screenshots. Optimizely said it fixed the flaw, removed the injected code, and revoked tokens. Please tell us whether any of our sites load Optimizely Experimentation. If they do, follow Optimizely's official guidance, review third-party scripts on our checkout and account pages, and review our Content Security Policy. Source: BleepingComputer, November 16, 2026.

Common questions

Does this mean my site was hacked?

Not by itself. This notice is about malicious code added to Optimizely Experimentation snippets that customer websites load. If your site loaded an affected snippet on November 16, 2026, treat that as a reason to review the site. It is not, on its own, proof of a wider break-in on your own servers.

Can EverThread tell me if I am affected?

No. EverThread does not test for this. We check your home page from the outside, the way a browser sees it. We cannot reliably tell you whether your site loads Optimizely Experimentation, whether a snippet was tampered with, or whether a visitor entered a card number on November 16. A scan without a warning about this incident does not mean your site is safe.

Which sites were affected?

Scott Helme, as reported by BleepingComputer, found 188 infected files belonging to 178 organizations. BleepingComputer named a number of brands where the malicious script loaded, or tried to load, including Zoom, CNN, Fox News, BBC, Salesforce, GitLab, American Eagle and HSBC Insurance. That is not a complete list. Follow official notices from the site or retailer you used.

Was payment card data taken?

BleepingComputer said the injected code was designed to skim payment card numbers, expiration dates and security codes entered on pages. Whether any given checkout on November 16 was captured depends on the site and the visit. If you entered card details on an affected site that day, watch your card accounts.

Is there a CVE?

No CVE has been assigned for this incident as of November 17, 2026.

Is there anything to update?

Optimizely said it deployed a fix and removed the injected code. There is no general patch for you to install on every site. If your site loads Optimizely Experimentation, follow Optimizely's official updates, and review your third-party scripts and Content Security Policy.

Where can I follow official updates?

Follow Optimizely's status page and BleepingComputer's report. All current notices are on our notices page.

Security alerts by email

Hear about the next one first.

When a flaw puts websites at risk, we send one email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.

We email you a link to confirm first, and every alert has a one-click unsubscribe. Alerts can include a short note about EverThread. Already a customer? Use your account email and your alerts include a link to your dashboard. Privacy

Sources

While you are here

Check your site's other basics free. We look at your home page the way a browser does. This scan cannot see whether your site loads Optimizely Experimentation, or whether a third-party script was changed. No account.

Or sign up free and we check it every day and email you when something changes.