# Optimizely security incident: What to check

What Optimizely confirmed about the 16 November 2026 Web Experimentation incident, how it reached websites and what site teams can check.

[Tom Cranstoun](https://tityra.com/authors/tom-cranstoun) · Published 2026-11-18

> Optimizely removed malicious JavaScript from affected projects on 16 November. To assess your site, match the affected project and time window to the pages that loaded its script.

## What Optimizely confirmed

On 16 November 2026, Optimizely identified unauthorised changes to some Web Experimentation projects. The company's initial report says a flaw in its account signup process allowed an unauthorised party to impersonate users and alter Project JavaScript. Affected snippets could then deliver that code to visitors' browsers. See [Optimizely's 17 November customer report](https://pages.optimizely.com/rs/947-RKE-048/images/Security%20Incident%20Report%20-%20Optimizely%20Web%20Experimentation%20-%20Nov%2017%202026.pdf).

Optimizely scoped the incident to Web Experimentation and excluded Feature Experimentation, the SDKs and legacy Full Stack. It reported no evidence that customer passwords were exposed. The company said the flaw had been fixed and the injected code removed, with a forensic investigation involving Mandiant continuing. Follow [Optimizely's incident status](https://status.optimizely.com/incidents/ftw0fh9wx43z) for further updates.

## Incident timeline

The times below come from Optimizely's preliminary timeline. For your own review, ask your Optimizely Customer Success Manager for the window that applies to your project or site. The public status update was posted at 01:02 UTC on 17 November.

### Optimizely's preliminary timeline for 16 November 2026

| Time (UTC) | What Optimizely reported |
| --- | --- |
| 07:51 | First malicious code written to a customer project. |
| 13:34 | Optimizely detected the activity. |
| 16:10 | Optimizely closed the signup flaw. |
| 16:53 | Optimizely ended affected sessions and revoked tokens. |
| 22:24 | Optimizely had removed the injected code from all affected projects. |

These are milestones for the vendor's response. The time a particular page served the affected snippet depends on that site's deployment and the project it loaded.

## How the script reached websites

Web Experimentation lets a team compare variations of a page. A website loads a snippet associated with an Optimizely project, and Optimizely can deliver changes to that snippet without a new deployment of the website. If the project is changed, browsers may receive different JavaScript even when the site's own publishing history shows no change. See [Optimizely's documentation on Project JavaScript](https://support.optimizely.com/hc/en-us/articles/39078107867661-Project-Settings-jQuery-and-Project-JavaScript-settings).

Optimizely's preliminary analysis found that the injected code targeted payment details entered on the page and cryptocurrency transfers. It also describes attempts against some older iOS and iPadOS versions. The report says the card fields inside a payment provider's hosted iframe were outside the code's reach. The surrounding checkout page still needs its own review. Use the project window, the payment design and the records you have to assess visitor impact.

## Check what reached your visitors

Start with the project IDs and snippets in use on 16 November. Find them in the templates and tag manager configuration that were live during the reported window. Check production domains, regional versions and journeys such as checkout. A project can have more than one snippet, so record the exact URL where you know it. Use [Optimizely's snippet documentation](https://support.optimizely.com/hc/en-us/articles/39076181533965-Optimizely-Web-Experimentation-JavaScript-snippet) to identify how projects and snippets relate.

For example, imagine a retailer used the same project on its product pages and checkout. The team checks the configuration that was live during the incident, confirms with Optimizely which snippet was affected and looks for that snippet in historical browser records. It then records whether card fields lived on the retailer's page or inside the payment provider's iframe. This gives the incident owner evidence to use for each journey.

- Ask Optimizely which projects were affected, what changed and the delivery window for each project.
- Map the affected snippets to pages and journeys during that window. Prioritise pages that accepted card details or supported cryptocurrency transfers.
- Preserve the relevant CDN and web logs, browser security reports and payment or fraud records. Review them with the teams who own those systems.
- Document gaps where records are missing. A clean test today shows how the page runs today. Use historical evidence to assess earlier visits.

## Verify the current deployment

Optimizely's 17 November report withdrew the earlier direction to disable the snippet. It also advised customers to remove it from sensitive pages that had no experiments. If your team paused it, use the vendor's current notice and your incident owner's review to decide which pages should load the service again.

Test representative journeys in a fresh browser session using test data. Check which approved snippets load, the behaviour of the page and whether the browser reports any blocked requests. Include consent states that change whether the snippet loads. Record the date, URL, configuration and result so another team member can reproduce the check.

## Review which scripts each page needs

Give each third-party script an owner and record which pages need it, why it runs and who can disable it. Start with pages that take payments or collect sensitive information. [PCI SSC's payment page security guidance](https://blog.pcisecuritystandards.org/new-information-supplement-payment-page-security-and-preventing-e-skimming) explains why teams should authorise payment page scripts, check their integrity and monitor for changes.

Content Security Policy (CSP) helps a website control where browsers load scripts and where supported browser requests can go. Check the policy actually sent by the page, including which rules are enforced. Report-only policies observe violations and leave requests running. An allowed script source can still deliver changed code, so use CSP alongside an inventory and review of the scripts that run. See the [W3C Content Security Policy specification](https://www.w3.org/TR/CSP3/).

## Sources and further reading

- [Optimizely initial customer report, 17 November 2026 (PDF)](https://pages.optimizely.com/rs/947-RKE-048/images/Security%20Incident%20Report%20-%20Optimizely%20Web%20Experimentation%20-%20Nov%2017%202026.pdf)

- [Optimizely Web Experimentation status and updates](https://status.optimizely.com/incidents/ftw0fh9wx43z)

- [Optimizely documentation on the Web Experimentation snippet](https://support.optimizely.com/hc/en-us/articles/39076181533965-Optimizely-Web-Experimentation-JavaScript-snippet)

- [Optimizely documentation on Project JavaScript](https://support.optimizely.com/hc/en-us/articles/39078107867661-Project-Settings-jQuery-and-Project-JavaScript-settings)

- [PCI SSC guidance on payment page security and e-skimming](https://blog.pcisecuritystandards.org/new-information-supplement-payment-page-security-and-preventing-e-skimming)

- [W3C Content Security Policy Level 3](https://www.w3.org/TR/CSP3/)

## About the author

### [Tom Cranstoun](https://tityra.com/authors/tom-cranstoun)

Tom Cranstoun is a co-founder of Tityra and a content systems architect. His work spans the BBC's electronic newsroom, Adobe Experience Manager and Edge Delivery Services. He writes about how people and AI agents access and use published content.

## Check Optimizely's incident updates

Use the vendor's current notice and request the records for your project if you use Web Experimentation.

[Read the Optimizely incident notice](https://status.optimizely.com/incidents/ftw0fh9wx43z)

## Keep exploring

- [Java4Shell (CVE-2026-114938): What website teams should check](/blog/java4shell)

- [How AI agents interact with websites](/blog/how-ai-agents-interact-with-websites)

- [What is a content audit?](/blog/what-is-a-content-audit)

[Tityra audit methodology](https://tityra.com/audit-methodology) · [Blog](https://tityra.com/blog)
