Skip to content

SEO News

Optimizely Fixes Signup Flaw After Malware Hit Customer Sites

Optimizely says an attacker used a signup flaw to add malicious JavaScript to some customer projects. Businesses using Optimizely Web should review project code, access and logs.

Source Search Engine Journal (opens in a new tab)
Abstract 3D browser window, a shield shape, and gears on a soft light background, with red accent gear.
Illustration for this article. Generated by AI.

Optimizely says an unauthorized party used a vulnerability in its Experimentation signup flow to add malicious JavaScript to some customer projects on November 16, 2026. According to Search Engine Journal, the code was served to visitors through Optimizely Web Experimentation snippets that many affected sites already trusted.

The reported code could swap cryptocurrency wallet addresses, watch site-owned form fields for payment card details, and load exploit kits for iPhones and iPads running older iOS versions. Optimizely said it blocked the vulnerable path, deployed a fix, ended active sessions, revoked tokens and reset access for affected user accounts.

What changed

Optimizely Web works by loading a JavaScript snippet from Optimizely’s CDN. That snippet can include a Project JavaScript section for custom code that runs on every page load. Report URI found the attacker placed malicious code in that section while leaving the rest of the script unchanged, so the script still appeared to come from a trusted Optimizely domain.

Report URI reviewed 1,611 Optimizely snippet files and found 188 with malicious code. It first saw the code on November 16, 2026, and said infected files were clean by later that day. Optimizely has notified affected customers, but its public updates did not say how many customer projects were affected or how the signup flaw allowed changes to existing customer projects.

What it means for your website

If your business uses Optimizely Web Experimentation, this incident matters even if your own website code was not changed. Project JavaScript runs wherever the Optimizely snippet loads, so visitors could be exposed through a third-party tool already present on the site.

This also shows a limit of basic allowlists in Content Security Policy. Report URI found that simply allowing Optimizely’s domain did not stop the attack because the malicious code came from that same domain. More restrictive script and connection rules helped some organizations block execution or stop data from being sent out, but not all sites had those protections.

What to do now

  • Open Project JavaScript in all Optimizely Web projects and review custom JavaScript in experiments for suspicious items, including 1688360.cc, atob(, and scripts your development team did not add.
  • Check each project’s History log and use available filters to review when Project JavaScript changed and whether changes came through the REST API or the Web Experimentation interface.
  • Review who has write access in Optimizely, along with API tokens and integrations, then rotate credentials.
  • If your site collects card details in its own forms, treat cards entered on November 16, 2026 as possibly exposed. Card data entered through hosted payment iframes such as Stripe and Adyen was described as outside the script’s reach.
  • Rotate any session token or secret stored in cookies that are not marked HttpOnly, and monitor Optimizely’s status updates as the company continues its investigation.

More from SEO News

All SEO News