WordPress maintenance Hacked site cleanup Security plugin Pricing Security tips
Home / Security tips / Website security
November 17, 2026

Optimizely Attack: What WordPress Shops Should Check

BBC, CNN and Zoom appeared in Report URI’s investigation of malicious JavaScript delivered through Optimizely on 16 November 2026. The uncomfortable detail for shop owners: the code arrived through a trusted outside service, not necessarily through altered files on the brands’ own servers.

Optimizely provides experimentation tools, including A/B testing - showing visitors different versions of a page to compare results. Useful marketing plumbing. Also another source of code running in a visitor’s browser.

What the incident actually establishes

In its 17 November notice, posted at 01:02 UTC, Optimizely said an Experimentation vulnerability allowed an unauthorized party to add malicious JavaScript to some projects. It reported fixing the vulnerability, removing injected code, securing affected accounts and adding delivery protections. The incident remained at Monitoring, not fully resolved.

Report URI found 188 infected snippets among 1,611 examined, associated with 178 organizations. Its investigation described code designed for payment-card skimming, cryptocurrency-address swapping and other visitor attacks. Those are sample findings and code capabilities, not a count of people whose money was stolen.

They don’t establish card theft on every named website. Nor does this report establish that BBC, CNN or Zoom run WordPress.


Why this matters to a WordPress shop

Your server sends a page. Then the browser may fetch analytics, chat, consent tools, experiments and scripts managed through a tag manager. Some arrive through plugins; others come from a theme, header snippet or marketing agency’s integration.

Those outside scripts can affect what visitors see and do. Depending on the integration and browser boundaries, they may interact with page content or form fields.

This wasn’t a WordPress-core or plugin vulnerability, and it wasn’t limited to WordPress. The connection is the dependency: your shop can have clean local files while trusted external JavaScript introduces risk.

And HTTPS? It protects the connection. It doesn’t certify that the delivered script behaves kindly.

A clean scan answers a narrower question

File scanning still matters. Please don’t abandon it because browsers have another layer to inspect.

But checking installed PHP and JavaScript files isn’t the same as observing everything a browser executes. Outside resources may load only on checkout, after consent, for certain visitors or through a later tag-manager action.

Our explanation of what a malware scan actually checks - and what it misses covers that boundary. A result needs a scope attached to it, not a reassuring green badge interpreted as permission to stop looking.

The same caution applies when using a Malware scanner: don’t assume it automatically detects this incident or reconstructs yesterday’s browser activity.


First, establish whether you use Optimizely

Ask whoever manages your website and marketing tags. A missing WordPress plugin doesn’t settle it; the integration might sit elsewhere.

If you use Optimizely Web, have your developer or agency identify the exact projects, review current vendor guidance, inspect custom project JavaScript and examine relevant account-access and integration records. Preserve available deployment, access and monitoring evidence with timestamps before routine changes erase useful context.

Follow recovery instructions for the confirmed scope. Don’t indiscriminately rotate every unrelated key or delete every script.

StepSecurity’s analysis makes a useful distinction: a clean snippet fetched now doesn’t establish that it was clean earlier. It also cautions that simple string or domain blocks aren’t complete remediation.

Not using Optimizely? There’s no basis here to say this incident compromised your shop. Audit the scripts you actually load instead.

Build a small script inventory

A spreadsheet is enough. For each integration, record:

  • The script or provider and its business purpose.
  • Who added it, who owns it now and who controls account access.
  • Which pages and conditions load it, including consent choices.
  • How updates and security alerts reach you.
  • How changes or removal are tested, and who approves them.

Include analytics, chat, experiments, consent tools and tag managers. Their presence isn’t evidence of compromise.

A hypothetical example: an outdoor-equipment shop stopped running a product-page experiment months ago, but its experiment tag still loads on checkout. That deserves a dependency check and planned removal, not an accusation against the provider.


Put controls around the browser, too

Remove genuinely abandoned integrations after checking what depends on them. Review account access, especially old agency logins. Ask your developer about monitoring browser-loaded scripts and changes in where they send data.

My preference is fewer justified scripts over a dashboard full of forgotten ones.

MDN describes Content Security Policy, or CSP, as a way to control browser resources and actions. Start with report-only observation; it doesn’t block. Test before enforcing rules so payments, analytics and needed scripts keep working. Allowing a provider’s domain isn’t proof everything served from it stays safe.

MDN also documents Subresource Integrity: supported static resources can be hash-pinned so browsers refuse changed content. Dynamic vendor scripts need a supported integration and update strategy. Pinning everything blindly can break legitimate changes.

Verify checkout without creating another problem

Use staging or an agreed safe payment-gateway test. Cover mobile, guest and signed-in purchases, different consent choices, forms and payment confirmation. Don’t open malicious resources or simulate theft against customers.

If evidence suggests checkout data exposure, involve your payment provider and an incident specialist. Work from confirmed facts, not an automatic breach declaration.

Our WooCommerce card-testing guide covers a different problem: criminals trying already-stolen card details. A skimming script is built to steal details from a page. Failed orders alone don’t prove skimming.

Bearmor is based in Estonia and works internationally. If you need help coordinating routine updates and checkout checks, discuss the scope through WordPress maintenance.

Open your script inventory and find the checkout integrations without a named owner. Give each one an owner and a review date. An unexplained tag shouldn’t get a permanent place beside your payment button.