Skip to content
Tityra
Login
Start for free
HomeAboutWho It's For
  • Publishers & Media
  • Ecommerce & Retail
  • SaaS & Technology
  • Agencies
  • Government & Public Sector
  • Financial Services & Insurance
PricingFAQBlog
info@tityra.com
XLinkedIn
  1. Home
  2. /
  3. Blog
  4. /
  5. Web operations

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.

5 min read

Tom Cranstoun · 18 November 2026

Read the article

Used by many

  • Onedio
  • Maçkolik
  • Webtekno
  • Yemek.com
  • Mynet
5/51 review on G2
Start for free

UNDERSTAND CONTENT DELIVERY

Learn what a tested client receives.

FOLLOW THE EVIDENCE

See how observations become findings.

PUT GUIDANCE INTO PRACTICE

Find changes your team can investigate.

Read the article

In this article

What Optimizely confirmedIncident timelineHow the script reached websitesCheck what reached your visitorsVerify the current deploymentReview which scripts each page needs
How we audit
Table of Contents
What Optimizely confirmedIncident timelineHow the script reached websitesCheck what reached your visitorsVerify the current deploymentReview which scripts each page needs
How we audit

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.

Copy linkWhat 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.

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 for further updates.

Copy linkIncident 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:51First malicious code written to a customer project.
13:34Optimizely detected the activity.
16:10Optimizely closed the signup flaw.
16:53Optimizely ended affected sessions and revoked tokens.
22:24Optimizely 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.

Copy linkHow 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.

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.

Copy linkCheck 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 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.

Copy linkVerify 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.

Copy linkReview 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 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.

Copy linkSources and further reading

  1. Optimizely initial customer report, 17 November 2026 (PDF)
  2. Optimizely Web Experimentation status and updates
  3. Optimizely documentation on the Web Experimentation snippet
  4. Optimizely documentation on Project JavaScript
  5. PCI SSC guidance on payment page security and e-skimming
  6. W3C Content Security Policy Level 3
Tom Cranstoun

About the author

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.

More about Tom

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
Share this article

Share this article

Keep exploring

Web operations

Java4Shell (CVE-2026-114938):
What website teams should check

Find out when Java4Shell can affect a website or API, who owns the Java update and how to verify the build in production.

Read article

Agent Experience

How AI agents interact with websites

AI agents can read pages, use browser controls or call tools directly, with each route shaping what they can see and do.

Audit practice

What is a content audit?

Learn how a content audit helps you decide what to change on your website, with a practical review process, an illustrative example and a checklist you can use.

Turn findings into
clear next steps.

Start for free
BlogAudit methodologyAPI docsMCP docsCLIGitHubContact

TITYRA LTD

120 Main Street
Largs, Scotland, KA30 8JN
info@tityra.com
HomeAbout
Who It's For
  • Publishers & Media
  • Ecommerce & Retail
  • SaaS & Technology
  • Agencies
  • Government & Public Sector
  • Financial Services & Insurance
PricingFAQ

© 2026 TITYRA LTD. All rights reserved. Registered in Scotland, company SC908253.

PrivacyTerms and ConditionsCookie informationCookie preferences

We value your privacy

By clicking "Accept all cookies", you agree to the storing of optional analytics cookies on your device to help us understand site usage and improve our website. You may click the customise button to choose which optional cookies you would like to allow.

Strictly necessary (2)

We save your cookie choice in this browser for six months, so you don't have to choose on every visit. This storage is always on.

Show detailsHide details for strictly necessary
  • Name
    tityra_analytics_consent_v1
    Provider
    Tityra (tityra.com)
    Type
    HTML local storage
    Maximum storage duration
    Persistent

    Remembers whether you accepted or rejected analytics. Your choice is valid for 180 days (six months), after which we ask again. The stored record remains until it is replaced or you clear your browser storage.

  • Name
    tityra_analytics_consent_v1_refusal
    Provider
    Tityra (tityra.com)
    Type
    HTML session storage
    Maximum storage duration
    Browser tab session

    Keeps analytics off if your browser can't save a rejection in local storage. This fallback is only used when needed and is cleared when a subsequent choice is successfully saved.

Google Analytics helps us understand page visits, content engagement, interest in audit packages and account signup link clicks. It only loads after you accept. Advertising features are disabled.

Show detailsHide details for analytics
  • Name
    _ga
    Provider
    Google Analytics (tityra.com)
    Type
    HTTP cookie
    Maximum storage duration
    Up to 180 days (six months)

    Distinguishes visitors to help us understand how the website is used. Set only after you accept analytics; advertising features are disabled.

  • Name
    _ga_*
    Provider
    Google Analytics (tityra.com)
    Type
    HTTP cookie
    Maximum storage duration
    Up to 180 days (six months)

    Maintains analytics session information, such as visits and interactions with the website. Set only after you accept analytics. The asterisk represents the identifier in the cookie name.

You control whether optional analytics runs on this website. We remember your choice for six months, and you can change it at any time using Cookie preferences in the footer.

Rejecting or withdrawing consent stops analytics and removes the Google Analytics cookies this website can access.

The details list the name, provider, purpose, type and storage duration of each entry. Contact details and private account information aren't included in website analytics.

Counts describe the entries listed, including the fallback and cookie name pattern, rather than cookies currently stored on your device.

Read our cookie information