On 16 November 2026, attackers exploited a vulnerability in Optimizely’s Experimentation account signup flow and injected malicious JavaScript into customer projects. Researchers identified 188 compromised scripts belonging to 178 organizations, with malicious code loading or attempting to load on sites including CNN, Fox News, the BBC, Zoom, Salesforce and GitLab. The payload was designed to swap cryptocurrency wallet addresses, skim payment card details, and deliver exploit kits to iPhones and iPads. Optimizely says it fixed the vulnerability, removed the injected code, and notified affected customers. Vendor scripts are powerful, and managing them deliberately gives businesses a practical way to reduce their exposure.

What happened in the Optimizely supply-chain attack?

Optimizely is a digital experience and experimentation platform. Its customers embed Optimizely’s JavaScript in their own pages to run tests and personalization. That architecture made this a supply-chain attack: malicious changes in a vendor’s script could reach visitors through websites that trusted it.

According to BleepingComputer’s reporting, security researcher Scott Helme identified 188 infected Optimizely JavaScript files belonging to 178 organizations after analyzing 1,611 scripts. The earliest observed injection was early morning on 16 November; how long the vulnerability existed before that remained unclear. The injected code loaded an additional payload from an attacker domain, with some variants hiding the address in Base64 and one carrying an embedded fallback copy of the malware in case the remote script was blocked.

Which websites were affected?

BleepingComputer independently confirmed the malicious script loaded, or attempted to load, on sites including Zoom, CNN, Fox News, the BBC, Salesforce, GitLab, KLM, Air France, HSBC Insurance, Smartsheet, Stamps.com, Bitly, Change.org, American Eagle, Mutual of Omaha and UNICEF USA.

The BleepingComputer report and Optimizely advisory reviewed on 17 November 2026 do not name a Japanese organization as affected. This article connects the incident to Japan’s vendor-risk pattern, not to a confirmed Japanese victim of this attack. If your website uses Optimizely Web Experimentation, check your exposure wherever you operate.

What did the malicious JavaScript do?

The analyzed payload had three main capabilities, plus surveillance. It watched pages for cryptocurrency wallet addresses and replaced them with attacker-controlled addresses. The identified wallets had received about $7,000 as of 16 November, though some were active before this campaign, so that figure is not a confirmed theft total for this attack.

It searched for payment card numbers, expiration dates and security codes entered into webpages and attempted to transmit them to the attackers. It also loaded secondary payloads against iPhones and iPads: Helme identified the Coruna and DarkSword exploit kits, targeting different iOS versions. The script contained functionality to collect browser cookies, page URLs and screenshots. Those capabilities do not establish how many visitors lost information or were successfully exploited.

How did Optimizely respond?

Optimizely told BleepingComputer it blocked the vulnerable signup path, deployed a fix, removed the injected code from affected projects, ended active sessions, revoked tokens, reset access for affected accounts, and blocked code delivery through Cloudflare. It said it notified all affected customers and is posting updates on its status page.

Salesforce said it was confirming Optimizely scripts were disabled across preview and production instances as a precaution. By 21:52 UTC on 16 November, Helme found only one of the 188 previously compromised files still containing malicious code. Detection, cleanup and clear customer communication are useful standards to ask about when assessing your own vendors.

Is JavaScript itself the problem?

This is why third-party JavaScript draws so much scrutiny from a security point of view. A script running directly in your page can read and change that page, making a compromised dependency a route into the experience your visitors trust. JavaScript is difficult to remove from many modern websites, but you can decide whose code runs and how changes reach production.

Self-hosting suitable scripts is a very good alternative to accepting live changes from a vendor’s server. You control the version and when to update it. It also brings maintenance work: reviewing updates, applying fixes and testing that the script still works. A locally hosted copy still needs to be trustworthy. Where a dependency supports stable files, Subresource Integrity lets a browser check a fetched file against an expected hash before running it.

What should you do if you visited an affected site?

If you made a cryptocurrency transfer while using an affected site on 16 November, verify the destination address was not swapped. If you entered payment card details, monitor the account for unauthorized charges and contact the issuer if anything appears. On iPhone or iPad, install the latest iOS or iPadOS updates, since the delivered exploit kits target vulnerabilities in older versions. Watch for suspicious account activity as well.

How do you get ahead of the next one?

Inventory every third-party script your site loads and decide, one by one, whether it earns its place. If you use Optimizely Web Experimentation, review the company’s incident updates and your affected-project notifications, check what your pages are serving, and coordinate any temporary removal with the people responsible for the site. Consider self-hosting suitable dependencies and monitoring changes to those you keep. Treat vendor JavaScript as part of your own codebase, because it runs in the experience you deliver.

And keep one eye on the horizon. A sufficiently capable quantum computer could threaten widely used public-key cryptography, including mechanisms used for encryption and digital signatures. NIST has already finalized post-quantum standards and urges organizations to begin the transition. We ought to be preparing for the risks that come with that kind of power. Knowing your dependencies and who maintains them is useful groundwork for asking vendors how they will handle that transition, alongside the script controls you can improve today.

Watch: NIST’s introduction to quantum-resistant algorithms, published 13 August 2024. This is background on the cryptographic transition, not footage or analysis of the Optimizely incident.

Why do vendor attacks keep working?

The entry point here was a supplier whose code other websites trusted. That is the dominant pattern in the Japan data I maintain: of 1,641 cyber incidents publicly disclosed since June, 63.0% came through a vendor, with 120 compromised vendors named as of 16 November 2026. These are disclosure records, not a census of every attack in Japan.

The Arara Message page lists 59 organizations confirmed through their notices, alongside the vendor’s figure of up to about 380 client companies. The full record is on the Japan Cybersecurity Tracker, and the dataset page explains its scope, sources and CC-BY 4.0 license. Reviewing the dependencies behind those incidents is a practical place to start improving your own operation.

Bring me the problem this article describes

We can spend 45 minutes, live, on your systems and the decision in front of you: which scripts you load, which vendors you trust, and what a compromise at one of them could mean for your business. Or get a written review of the setup. Tell me what you need to decide.