---
title: "Optimizely script attack: what to check on your business site"
description: "Optimizely script attack: malicious code reached some sites on November 16, 2026, through a script they loaded. Check outside scripts on your site this week."
url: "https://webleveling.com/blog/optimizely-script-compromise-third-party-scripts-small-business/"
lang: "en"
published: "2026-11-17"
modified: "2026-11-17"
author: "Cal Hewitt"
tags: ["website-security","small-business","incident-response"]
image: "https://webleveling.com/og/blog-optimizely-script-compromise-third-party-scripts-small-business.jpg"
alternates:
  es: "https://webleveling.com/es/blog/ataque-de-scripts-optimizely-que-revisar-en-su-sitio.md"
---

# Optimizely script attack: what to check on your business site

Optimizely script attack: malicious code reached some sites on November 16, 2026, through a script they loaded. Check outside scripts on your site this week.

![A florist in a green apron stands on the sidewalk outside her shop on an overcast weekday morning, reading her phone held at an angle, with buckets of tulips on the pavement beside her.](https://webleveling.com/blog/optimizely-script-compromise-third-party-scripts-small-business/script-featured.jpg)

On November 16, 2026, an unauthorized party used a flaw in Optimizely's website-testing service to add malicious JavaScript to scripts that some large websites load from it. Optimizely says it has fixed the flaw and removed the injected code from the affected projects.

Your own site probably loads code from other companies too, for analytics, chat, booking, reviews or payments. A script like that runs in your visitors' browsers with privileges similar to your own site's code, so a changed file can reach them while your hosting and your website stay untouched. That is the part of this incident that applies to a small business.

The response is a list of every outside script your site loads, a look at who can change each one, and a few questions for your web designer. It takes time, not a rebuild, and you can start this week.

**Key Takeaways**

**Outside scripts run with your site's trust**

OWASP says third-party JavaScript runs with privileges similar to code supplied by the site itself, so a changed vendor file can reach visitors while your server is never breached.

**The first check is a list, not a rebuild**

Write down every outside script and tag, who added it and who can change it, remove what nobody can explain, and keep card entry on your payment provider's hosted page.

**Ask whether your content security policy is enforced or only reporting**

SRI suits files that never change, CSP limits where scripts load from and where data can be sent, and W3C calls CSP defense in depth, not proof that a trusted vendor is safe.

## What did Optimizely and Report URI say happened on November 16?

Optimizely's [status page](https://status.optimizely.com/) says it identified a security incident in which an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects. Optimizely says it fixed the vulnerability, removed the injected code from affected projects, secured affected user accounts and added protections.

Security firm Report URI investigated and published its [findings on November 16, 2026](https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/), updated on November 17. It explains that each Optimizely Web customer loads a JavaScript snippet from Optimizely's content delivery network, so a site could be affected "without its own code or infrastructure ever being breached." Report URI counted 188 infected snippets in total and says the code tried to swap cryptocurrency addresses and skim payment-card fields.

November 16 and 17, 2026, in UTC

1.  1

    13:43 on November 16

    Report URI observes the injected code skimming payment-card fields.

2.  2

    21:52 on November 16

    One infected snippet is still live, according to Report URI.

3.  3

    23:11 on November 16

    Report URI observes that all infected Optimizely files have been cleaned.

4.  4

    November 17

    The attacker's main domain is taken down, and Optimizely's status page describes the fix.

Zoom has published its own [security bulletin](https://www.zoom.com/en/trust/security-bulletin/). It says Zoom disabled Optimizely across its production environments as a precaution and has not identified any impact to customer data. Other companies you may see named in reports appear on Report URI's list of infected snippets, and each one's own statement is for that company to make.

Treat the payload as what the code tried to do. An attempt to skim a card field is not a confirmed theft from every visitor. If your site loads an Optimizely script, ask Optimizely for details about your own projects instead of guessing.

## How can a website serve harmful code when its own server was never breached?

A website is not one file from one company. Your page pulls in a tag from an analytics tool, a chat widget, a booking calendar, a reviews badge and a payment form, and each of them is a file that lives on another company's servers. Your visitor's browser fetches all of them and runs them on your page.

![A small-town main street at midday in bright sun, with a florist's striped awning, a hand-lettered sandwich board reading "Order online, pick up today", a parked delivery van and a few shoppers walking past.](https://webleveling.com/blog/optimizely-script-compromise-third-party-scripts-small-business/script-main-street-shops.jpg)

Every small shop's website leans on code that lives on other companies' servers.

OWASP's [third-party JavaScript guidance](https://cheatsheetseries.owasp.org/cheatsheets/Third_Party_Javascript_Management_Cheat_Sheet.html) says this gives the outside code privileges similar to code supplied by the site itself, including access to page content and browser-visible data. It names three risks: losing control over changes, arbitrary code execution and disclosure of sensitive information. So, a clean hosting account and a tidy server log cannot tell you what the browser received.

Two common assumptions do not hold up here. HTTPS proves the connection reached the vendor, not that the vendor's current file is safe. A tag manager can publish new browser code without anyone deploying anything to your server, which makes it a place to protect, not a settings screen to ignore.

## Does this apply to your website?

Start with one question: does anyone run A/B tests or experiments on your site? Optimizely Web Experimentation is the product the incident involved, and it works through a snippet your pages load. Ask your web designer, developer and whoever handles your marketing. If the answer is yes, ask for a review of the project's JavaScript, user access, tokens and integrations, and ask Optimizely directly whether your project was among the affected ones.

If the answer is no, the same question still applies to everything else your site loads. The incident shows how the weakness works. Your analytics, chat and booking tools are not suspect because of it, and it is no reason to remove them. It is a reason to know who controls them.

Pages that collect payment details, logins or inquiries deserve the closest look, because a changed script there can read what visitors type. Your home page matters too, but start where visitors hand over information.

## What should you check on your site this week?

Work through these in order. The work is mostly asking questions and reading account settings.

**This week's script check**

**Inventory every outside script and tag**

Include analytics, chat, booking, reviews, payment widgets, advertising pixels, A/B testing and any tag manager container.

**Write down who owns each one**

Record the vendor, the purpose, the pages it loads on and who can publish changes.

**Remove what nobody can explain**

A tag left over from a finished campaign or an old vendor has no business purpose and still runs.

**Lock down who can publish**

Turn on MFA, remove former employees and agencies, and stop sharing logins.

**Confirm where card numbers are typed**

It should be your payment provider's hosted page or frame, not a form your own site controls.

Take the accounts step seriously. CISA's [phishing-resistant MFA fact sheet](https://www.cisa.gov/sites/default/files/publications/fact-sheet-implementing-phishing-resistant-mfa-508c.pdf) explains why a stronger second step protects the accounts that can change what your site runs. OWASP names tag manager access control and two-factor authentication as safeguards for exactly this reason.

![A handwritten page on a clipboard lying on a shop counter under a lamp at night, headed "Outside scripts" with the lines "Analytics", "Chat", "Booking", "Reviews" and "Payments", a pen beside it and a card reader out of focus behind.](https://webleveling.com/blog/optimizely-script-compromise-third-party-scripts-small-business/script-outside-scripts-list.jpg)

The list is the check. A script with no named owner is the first one to chase.

A hosted payment page reduces your site's direct exposure to card data, but the page around it still runs your scripts. The PCI Security Standards Council's [SAQ A-EP document](https://www.pcisecuritystandards.org/documents/PCI-DSS-v4-0-SAQ-A-EP.pdf) requires scripts on payment pages to be authorized, to have their integrity assured and to appear in an inventory with a written reason, including scripts from third and fourth parties. Keep your payment pages as bare as you can.

A short review cannot prove that no visitor was exposed. It can show you an unmanaged script, a forgotten tag or an account with too much access, and those are worth fixing whatever the news cycle is doing. CISA publishes free and low-cost guidance, including [cybersecurity resources for organizations](https://www.cisa.gov/), and the SBA points small businesses to it.

## What do SRI and CSP do, and what should you ask your developer?

Both are web standards that browsers understand. They are not products, and your developer sets them up in how your pages are built. Each one has a limit worth knowing before you ask for it.

Two browser protections and where each one stops

| Standard | What it does | Where it stops |
| --- | --- | --- |
| Subresource Integrity (SRI) | Attaches a fingerprint to a script so the browser runs only the exact file expected | Does not fit scripts that change with every experiment, tag or vendor release |
| Content Security Policy (CSP) | Limits where scripts may load from, what code may run and where data can be sent | A trusted vendor's address can still serve harmful code, so W3C calls it defense in depth |

The [W3C Subresource Integrity draft](https://www.w3.org/TR/2026/WD-sri-2-20260320/) says SRI lets a browser confirm that a fetched file was not manipulated on the way. That helps for stable, versioned files. The [W3C Content Security Policy specification](https://www.w3.org/TR/CSP/) describes CSP as a way to reduce the privilege of applications, and as defense in depth rather than a replacement for secure coding.

Put these questions to your developer or whoever manages the site:

- Which outside scripts load on our checkout and contact pages?
- Who can change each one, and does it have MFA?
- Is our CSP enforced, only reporting, or not set up?
- How would we find out if one of those scripts changed unexpectedly?
- Did my site load Optimizely Web Experimentation on November 16, 2026?

Ask for the answers in writing, and expect "report-only" or "not yet" for some of them. That is a starting point for a plan, not a failure. Adding a strict CSP to a site with many marketing tools can break those tools, so the change is worth testing first.

![A florist in a canvas apron stands on the loading dock behind her shop at dusk, a phone to her ear and a clipboard in her other hand, with buckets of tulips and a van with its rear door open behind her.](https://webleveling.com/blog/optimizely-script-compromise-third-party-scripts-small-business/script-call-to-developer.jpg)

Make the call while the list is still in your hand.

## When does an owner need outside help with this?

The first check is yours to do. A rebuild, a new platform or a new vendor is not the answer to this incident, so hold off on buying any of those.

Outside help makes sense when you cannot name the accounts that control your scripts, when checkout uses card fields your own site controls, when your tag manager is complex, when a CSP change could break marketing tools, or when your site used Optimizely during the incident. It also makes sense if you see an unexpected script or account change. In those cases the work is an inventory and access cleanup, followed by a routine of recurring checks.

![A customer in a rain jacket walks out of a flower shop onto the sidewalk on a bright Saturday morning with a wrapped bouquet, while the florist in the doorway waves and a hanging "Open" sign sits in the glass.](https://webleveling.com/blog/optimizely-script-compromise-third-party-scripts-small-business/script-saturday-pickup.jpg)

When the scripts are listed and owned, a Saturday rush is only a Saturday rush.

If something does look wrong, keep original emails, logs, screenshots, affected addresses and payment records, and contact your payment provider. The FBI's [IC3](https://www.ic3.gov/) takes reports of cyber-enabled crime, and the FTC's breach response guide for businesses covers securing operations and checking notification rules. For related reading, see what to do in the [first 24 hours after a website is hacked](https://webleveling.com/blog/website-hacked-first-24-hours/), what to check after [reports of AI agents hacking websites](https://webleveling.com/blog/ai-agents-hacked-100-websites-what-to-check/), and how to [check WordPress plugins for urgent security updates](https://webleveling.com/blog/check-wordpress-plugins-for-urgent-security-updates/).

**Quiz: How well do you know your site's outside scripts?**

1. According to OWASP, what can a third-party script do on your page?
   - Nothing beyond its own widget
   - Run with privileges similar to code supplied by the site itself **(correct answer)**
   - Only read your server logs
   - Only run while the site's hosting account is hacked
2. Why does Subresource Integrity not suit a script that changes with each experiment?
   - Browsers refuse to read it
   - It only works on payment pages
   - The fingerprint it checks would stop matching whenever the file changes **(correct answer)**
   - It slows the page down too much
3. Your payment provider hosts the card form. What should you still do?
   - Nothing, scripts on the surrounding page no longer matter
   - Keep the surrounding payment page as bare as possible and inventory every script on it **(correct answer)**
   - Remove your analytics from the home page only
   - Move the card form onto your own page

## Frequently Asked Questions About Optimizely Script Attack

**Can a website be exposed without its own server being hacked?**

Yes. When a script your site loads from another company changes, visitors can receive the changed code while your server stays as you left it. Report URI describes this for Optimizely's customers, who load a snippet from Optimizely's network.

**What happened with Optimizely?**

Optimizely says an unauthorized party exploited a vulnerability in Experimentation and added malicious JavaScript to some customer projects, and that it fixed the flaw and removed the injected code. Report URI counted 188 infected snippets and observed all infected files cleaned by 23:11 UTC on November 16, 2026.

**Were card numbers stolen in the Optimizely script attack?**

Report URI says the code tried to skim payment-card fields from 13:43 UTC on November 16, 2026. An attempt is not a confirmed theft for every visitor. If your site used Optimizely that day, ask your payment provider and your developer to review it with you.

**Does a hosted payment page protect card numbers from my site's scripts?**

It reduces your site's direct exposure to card data. The page around the payment form still runs your scripts, so keep that page bare and keep an inventory of every script on it.

**Should I remove Google Tag Manager after this?**

Removal is not the point; control is. A tag manager can publish new browser code without a server change, so review who can publish, turn on MFA and remove old users and agencies.

**What should I do if I find something unexpected?**

Save logs, screenshots and affected addresses, contact your payment provider and report fraud to IC3. A message about this incident that urges you to call a number or install software is a scam signal; contact the vendor through an address you already know, as the FTC advises about urgent security messages.

## What This Means for You

A script from another company runs on your page with your site's trust, so a change on their side can reach your visitors without a breach on yours. That is how the Optimizely incident worked, and Optimizely says it is fixed. The check that matters is the same for every site: know which scripts you load, who can change them, and how you would notice a change.

Once the list exists, it becomes a routine. A short review once a quarter, an MFA check when staff change and a question to your developer about CSP keep the list current, and a vendor's bad day is easier to answer when you can see your exposure in minutes.

If you want help, [Web Leveling](https://webleveling.com/) can build the script inventory, clean up who has access and set up a recurring check. Our [website security audit](https://webleveling.com/services/website-security-audit/) covers scripts, accounts and payment pages, and ongoing [website maintenance](https://webleveling.com/services/website-maintenance/) keeps them watched. We work with small and medium businesses across the country and overseas. [Send us your script list or your questions](https://webleveling.com/contact/), and we will tell you what needs attention and what can wait.

## Terms

Script security words in this post

Tap a term to see what it means.

**Third-party script.** JavaScript your page loads from another company's servers, such as analytics, chat or a testing tool.

**Tag manager.** A tool that lets people add and change scripts on a site without editing the site's code.

**Subresource Integrity (SRI).** A web standard that lets a browser run a script only if it matches an expected fingerprint.

**Content Security Policy (CSP).** A web standard that limits where scripts may load from, what code may run and where data may be sent.

**Report-only mode.** A CSP setting that records violations without blocking anything.

**MFA.** Multi-factor authentication, a second proof of identity, such as a code or security key, beyond a password.

Share this article

[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwebleveling.com%2Fblog%2Foptimizely-script-compromise-third-party-scripts-small-business%2F)[Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwebleveling.com%2Fblog%2Foptimizely-script-compromise-third-party-scripts-small-business%2F)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwebleveling.com%2Fblog%2Foptimizely-script-compromise-third-party-scripts-small-business%2F&text=Optimizely%20script%20attack%3A%20what%20to%20check%20on%20your%20business%20site)[WhatsApp](https://wa.me/?text=Optimizely%20script%20attack%3A%20what%20to%20check%20on%20your%20business%20site%20https%3A%2F%2Fwebleveling.com%2Fblog%2Foptimizely-script-compromise-third-party-scripts-small-business%2F)[Email](mailto:?subject=Optimizely%20script%20attack%3A%20what%20to%20check%20on%20your%20business%20site&body=https%3A%2F%2Fwebleveling.com%2Fblog%2Foptimizely-script-compromise-third-party-scripts-small-business%2F)

- [FBI ARTEX AI hacking tool: what to check with your provider](https://webleveling.com/blog/fbi-artex-ai-hacking-tool-small-business/): The FBI ARTEX warning of November 13, 2026 says some intrusions reached privileged access in under three hours. Check your provider's access this week.
- [Online Store Data Breach: What to Tell Customers and When](https://webleveling.com/blog/online-store-data-breach-tell-customers/): A small online store data breach calls for a set order: secure the store, check state and GDPR rules, call your processor, then send a plain customer notice.
- [Your Website Got Hacked: What to Do in the First 24 Hours](https://webleveling.com/blog/website-hacked-first-24-hours/): A hacked website does not always look broken from your own computer. Learn the real first moves, what to skip, and when cleanup beats a full rebuild.
