The Optimizely cyberattack is a supply chain attack discovered on November 16, 2026, in which malicious JavaScript reached the websites of 178 organizations through Optimizely, a platform businesses use to test versions of their web pages. Security researcher Scott Helme of Report URI found 188 compromised scripts, which reportedly ran for about 19 hours. Optimizely confirmed the incident the next day.
Last updated: November 17, 2026
In this article
What happened in the Optimizely cyberattack?
The Optimizely cyberattack was uncovered on Monday, November 16, 2026, by Scott Helme of the security firm Report URI, according to the Mediaite report. Helme examined more than 1,600 files tied to Optimizely and identified 188 compromised scripts across 178 organizations. Reports say the attack began early Monday and ran for approximately 19 hours before the infected scripts were removed.
Optimizely sells software that companies use to compare different versions of a web page or feature. Reuters reported that the hackers used that platform to distribute malicious JavaScript through otherwise legitimate pages. TMZ, as cited by FOX5 Las Vegas, reported that visitors could be exposed simply by loading an affected page, without clicking a suspicious link.
| Fact | Reported detail | Source |
| Discovery date | Monday, November 16, 2026 | Mediaite |
| Discovered by | Scott Helme, Report URI | Mediaite |
| Organizations affected | 178 | Mediaite |
| Compromised scripts | 188, found among more than 1,600 files | Mediaite |
| Reported duration | About 19 hours | Mediaite |
| Vendor confirmation | Tuesday, November 17, 2026 | Yahoo News, citing Newsweek and Gizmodo |
| Reported entry point | A vulnerability in the Experimentation account signup flow | Optimizely statement to Gizmodo |
Which brands did reports name?
Newsweek, summarized by Yahoo News, named Zoom, CNN, Fox News, HSBC, IKEA, Equifax, Paychex, Bitly, Salesforce, American Eagle and Alaska Airlines among the affected websites. Mediaite and FOX5 also listed the BBC. Report URI's analysis, not a statement from each company, is the basis for these names.
Being named in a researcher's list is not proof that a particular company's customers lost data. The sources reviewed for this article did not include statements from most of these brands, so this article does not describe any single brand's response. That gap is itself the communications story, and the later sections show how affected brands can fill it.
What did Optimizely say, and what is still unknown?
Optimizely said it identified a security incident in which an unauthorized party exploited a vulnerability in its Experimentation account signup flow, according to its statement to Gizmodo as reported by Yahoo News. The statement names the product area and the type of weakness. That detail gives customers, reporters and security teams something specific to repeat and to check.
The reports reviewed do not say how many people were affected, and Optimizely has not been quoted giving a count. Report URI's findings describe code with several goals. Newsweek reported the following:
- Replacing cryptocurrency wallet addresses that users copy, so payments could be redirected to the attackers.
- Collecting credit card details stored in web browsers.
- Targeting some iPhones and iPads that run older versions of iOS.
TMZ, again as cited by FOX5, added that the code also attempted to collect browser cookies and screenshots. These are researcher and press descriptions of what the code was built to do, not confirmed totals of stolen data.
Why does a vendor attack hurt brands that did nothing wrong?
A vendor attack hurts the brands involved because visitors see the brand's own web address and hold the brand responsible for whatever loads on its pages. The Optimizely scripts ran inside pages that CNN, Zoom, HSBC and others control, so a reader has no visible way to tell vendor code from the brand's own.
The brand also chose the vendor. A statement that says only "this was a third party" can sound like deflection, even when it is accurate. Customers ask a simpler question: is my money or my data at risk after I visited your site?
The cryptocurrency angle sharpens that question. A swapped wallet address can send funds to an attacker, and a transfer of that kind generally cannot be undone. For that reason, a brand's first message should focus on what a customer can check, not on who is to blame.
Scale adds a second pressure. When 178 organizations are named in the same news cycle, reporters compare their statements side by side. A brand that publishes a clear, dated notice early gives journalists a ready quote and a link to cite, while a brand that stays silent is described by what researchers say about it.
What should an affected brand say in the first 24 hours?
An affected brand should publish one dated statement that confirms whether its pages loaded the compromised scripts, gives the time window, names one customer action and promises a specific update time. The steps below follow that order.
- Confirm whether your pages loaded the affected scripts, using the vendor's information or the researcher's published findings.
- State the window in plain terms, such as the part of November 16 when the scripts ran, so customers can tell whether they visited.
- Describe what the code was reported to target, and avoid guessing about stolen data until your own review is complete.
- Give customers one concrete action, such as checking recent card statements and confirming any wallet address before sending funds.
- Name one owner for updates and state when the next update will appear.
Sample holding statement for a brand whose site loaded the scripts
On November 16, a third-party website testing service we use was compromised, and malicious code ran on some of our pages for part of that day. We have removed the service from our pages and are reviewing what visitors may have been exposed to. If you visited our site on November 16, please check your recent card statements and confirm any cryptocurrency wallet address before you send funds. We will post our next update on this page at a time we state here.
The Optimizely attack combines three situations that Everything-PR has covered before: a hack that touches payments, a vendor failure and a fast news cycle. The first 45 minutes in the crypto hack communications playbook apply directly when wallet addresses are involved.
The 72-hour window in crisis communications explains why the first statement matters so much, and how to build a crisis communications plan covers the pre-approved statements that let a team publish within hours. The wider crisis communications guide links the full set of playbooks and cases.
What should communications teams do this week?
Communications teams should check whether their sites load Optimizely or any other third-party script, and agree on a holding statement before an incident, not during one. Four checks fit into a single meeting:
- List every third-party script that loads on payment, login and account pages, and name an owner for each.
- Ask each vendor how quickly it will notify you of an incident and what it will say publicly.
- Pre-approve the holding statement language with legal and security, including the customer action line.
- Decide who speaks if a researcher publishes findings about your site before your vendor does.
Optimizely confirmed its incident within a day of discovery and named the weakness. That sequence, a quick confirmation with a specific cause, is the version of the story that affected brands can build on while the full count of affected visitors is still being established.