Optimizely

How they got in, as reported. A known flaw in software the victim ran.

← All cases
Date
16 Nov 2026
Place
United States
Who
Optimizely
The way in
Known software flaw
Source
BleepingComputer
01 · What was reported

What was reported.

Attackers injected malicious JavaScript into Optimizely customer projects, so websites of about 178 organisations loaded code built to swap cryptocurrency wallet addresses and skim payment-card data. Optimizely said it blocked the vulnerable path and deployed a fix.

The way in the source reports: a known flaw in software the victim ran.

The company confirmed to BleepingComputer that attackers exploited a vulnerability in its Experimentation account signup flow to inject malicious JavaScript into customer projects, causing websites using the platform to load malware.BleepingComputer, added to these pages on 17 Nov 2026. The source
02 · The way in

What a known software flaw is.

A known software flaw is a weakness the maker has published and fixed in a later version. A system still on the older version keeps the weakness until it is updated.

Once a flaw is public, attackers look across the internet for the version that has it and try the published method on every system that answers. Devices at the edge of a network, mail servers and web software are reached first because they face the internet.

We read the versions a firm's own servers and website state about themselves and match them to public records of known flaws, the government list of flaws used in attacks among them.

A version a server does not state cannot be read. A fix can also be applied without changing the version shown. A match is a reason to check the system. It is not proof the flaw was used.

This part is true of every case of this kind. It says nothing more about Optimizely than the source does.

03 · What we check for it

What we check for it.

Software versions your site advertises and known flaws in them.

For technology companies

What we read for technology companies.

  • The records that tell inboxes whether to refuse email sent as you (DMARC, SPF and DKIM), read externally.
  • Breach records for addresses at your own domain, read externally; nothing inside is touched.
  • Web addresses an attacker could register to look like yours, each checked: is it registered, is it set up for mail.
  • The certificate your website answers with, seen externally: its name, its dates and who issued it.
  • The headers and cookies your website sends to every visitor, seen externally.
  • Read with the assessment. What AI assistants answer about your business. A client who asks an AI assistant about your business trusts the answer it gives. Assistants build those answers from pages they crawl. A look-alike address an attacker could register can be built to be crawled: its robots file invites the AI crawlers in and its page claims your name. Attackers manipulate AI answers to send your paying and enquiring clients to their own look-alike page, web address, sign-in page, phone number or email. In 2025, asked for the sign-in pages of 50 brands, an AI assistant gave addresses the brand did not control one time in three. The check is built to ask six assistants: Claude, ChatGPT search, Gemini, Perplexity, Grok and Copilot, through Bing. Monitoring asks again every week and tells you when an impostor's phone or address is in an answer. Source: Netcraft research, read on 4 November 2026.

The rule, from its source: What does each US state's data breach law ask a business to do?

Request your firm’s reading

See your own firm the way an attacker reads it.

We read your domain from public records and show each way in with a check anyone can re-run.

04 · Source

Source.

Source: BleepingComputer ↗

This page repeats what the source reported, with its date. It says nothing about any firm that is not named in it.