Optimizely Flaw Injected Malicious Code Into Customer Sites: Check Your Email Landing Pages
Optimizely says an attacker abused a signup flaw to inject JavaScript into some Web Experimentation projects on 16 November. Salesforce asks customers to check Marketing Cloud landing pages.

Optimizely has confirmed that an attacker abused a flaw in its Web Experimentation product on 16 November 2026 to insert malicious JavaScript into some customers' projects. In its incident report, the company says the attacker exploited the account signup flow to impersonate users on targeted customer accounts, then added code that was served to visitors of those customers' websites.
Salesforce, one of the affected organisations, has published a response to the incident, which it calls OPTIMJACK. It says Optimizely-provided scripts on certain Salesforce websites were modified, and it asks its own customers to check Marketing Cloud landing pages, Experience Cloud sites and Commerce Cloud storefronts for Optimizely snippets.
That last point is why the incident concerns email teams. Landing pages, preference centres and signup forms that campaigns link to often carry A/B testing scripts. If one of those scripts was compromised on 16 November, visitors arriving from an email click may have loaded the malicious code.
Key facts
- Product: Optimizely Web Experimentation only; Optimizely says no other product was affected
- Date: 16 November 2026; Salesforce puts the exposure window at roughly 04:00 to 21:00 UTC
- How: a flaw in the account signup flow let the attacker impersonate users and inject JavaScript into projects
- Scale: fewer than 5% of Optimizely customers, according to Optimizely
- Status: Optimizely says the flaw is closed, the injected code removed, and it was not a credentials breach
What Optimizely and Salesforce have confirmed
Optimizely says it detected the activity on the day it began, blocked delivery of the malicious code and closed the vulnerability within three hours of detection. It removed the injected code from every affected project, says no malicious code remains in its systems, and has contacted every Web Experimentation customer to tell them whether they were affected. Customers who do not use Web Experimentation have nothing to do.
Salesforce says it has no evidence that the incident affected the Salesforce platform or its subscription services. It disabled Optimizely scripts across its preview and production sites and will keep them off until Optimizely's remediation is verified. Salesforce also cites a security researcher who counted 188 compromised Optimizely JavaScript files across 178 organisations; that count comes from the researcher, not from Optimizely.
Why marketers should check their landing pages
The injected code was placed in the project-level JavaScript, which runs on every page where the project is installed, and it was delivered from Optimizely's own content delivery network. To browsers and many security tools it looked like the normal testing script. Salesforce advises customers whose own teams embedded Optimizely Web Experimentation to review application logs for 16 November, watch for tampering with payment forms, and look for unusual session activity such as logins or token use from unfamiliar locations.
For email programmes, the exposure is on the click side rather than in the inbox. Campaign landing pages, signup forms and preference centres hosted in marketing clouds or on the brand's own site are common places for testing scripts. Only pages that loaded an affected Optimizely project during the window are concerned.
What it means for senders
What changes
Email landing pages, signup forms and preference centres that loaded an affected Optimizely Web Experimentation project on 16 November may have served malicious code to visitors who clicked through from campaigns.
Who is affected
Brands using Optimizely Web Experimentation on pages linked from email, including Salesforce Marketing Cloud, Experience Cloud and Commerce Cloud customers who embedded it themselves.
When
16 November 2026, roughly 04:00 to 21:00 UTC according to Salesforce; Optimizely says the flaw is now closed.
Action checklist
- Check Optimizely's notice to your account to confirm whether your projects were affected.
- Inventory third-party scripts on landing pages, signup forms and preference centres linked from your emails.
- Review logs for 16 November on any page that loaded an affected project, including form submissions.
- Watch payment and signup forms for tampering, and sessions for logins from unfamiliar locations.
- Keep testing scripts off sensitive pages such as login, payment and preference centre flows where possible.
Sources
- Optimizely: Web Experimentation Security Incident
- Salesforce: Our response to the Optimizely OPTIMJACK supply chain compromise
Related on SMTPedia
SMTPedia News follows our editorial standards. Spotted an error? See how we correct it.
Get SMTPedia news first on Google
Add us as a preferred source to see our stories in Top Stories and Discover.
Add as preferred sourceUseful story?
SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.
Buy SMTPedia a coffeeNewsletter