Web security

Optimizely Hack Hits 178 Sites: What to Check

Lumia beaver in a suit and headset analyzes a green code window infected by a magenta thread and a broken chain

What happened: malicious code in 178 organizations

On Monday, November 16, 2026, security researcher Scott Helme spotted something serious: JavaScript files delivered through Optimizely, a platform many companies use for A/B testing and website personalization, had been modified with malicious code. According to press reports, 188 files tied to 178 organizations were tampered with, including Zoom, HSBC, Equifax, CNN, Salesforce, IKEA and ABN AMRO.

Optimizely acknowledged that an unauthorized third party exploited a weakness in the platform's account sign-up process to inject the code. The company said it fixed the flaw and removed the malicious code. Salesforce investigated unauthorized modifications and disabled Optimizely as a precaution; Equifax suspended its use and said it found no evidence that its own systems were compromised.

Important: it is not confirmed how many users were affected or whether all of the code's goals were achieved. HSBC, Zoom, CNN and IKEA had not responded to requests for comment at the time of the reports we reviewed.

What the code was after

According to reports, the code was designed to do several things at once:

  • Capture card data typed into payment forms.
  • Divert cryptocurrency by swapping the wallet addresses users pasted.
  • Collect cookies and screenshots from the session.
  • Try to compromise iPhones and iPads using tools that exploit iOS vulnerabilities.

Researchers traced about US$7,040 in cryptocurrency received by wallets linked to the code during the day of the attack, although that figure does not establish the total amount stolen. Anyone who visited one of those sites on November 16 and paid by card may, as a precaution, review their account activity.

How a supply chain attack works

It is the same pattern we saw with Polymarket in our analysis of the Binance and DreamHost cyberattacks: they do not attack your site, they attack something your site uses. An A/B testing tool, an analytics script, a chat widget, a payment gateway or a library. Your page loads that code from the provider's server; if the provider is compromised, the malicious code reaches your visitors under your own domain and your security padlock.

The most uncomfortable part of this kind of attack is that your site can be perfectly up to date and still deliver dangerous code. That is why the defense is not just "keep everything updated": it is knowing what third-party code your page loads and why.

A week of failures: which were attacks and which were not

This week several incidents came together and fed suspicions of a coordinated attack. As of November 17 there was no evidence that they were related. It helps to separate them:

DateIncidentWhat was reported
November 12Microsoft 365 outageTechnical failure; no signs of malicious activity
November 13Impact on banks and governments in Asia-PacificEmail-dependent services temporarily affected
November 13Ground stop of departures in the US (FAA)Data overload on old communication equipment; malicious activity ruled out
November 16Outages at JPMorgan Chase, Bank of America, Wells Fargo and US BankJPMorgan cited a software error and ruled out a cyberattack
November 16-17Malicious code in 178 organizationsIt is an attack: Optimizely confirmed an unauthorized third party injected the code

The difference matters: facing a failure, your response is a backup plan (the guide is in this article). Facing an attack, your response is to contain, change access and notify.

What to check on your website today

  1. Inventory your third-party scripts. Google Tag Manager, pixels, chat, analytics, A/B testing, maps, reviews. Write down what your page loads and who is responsible for each one.
  2. Remove what you do not use. A testing tool nobody has opened in six months is still loading on your site and is still a door.
  3. Protect payment pages. Use the payment gateway's own window (an iframe or a page hosted by the provider) instead of in-house card forms with third-party scripts.
  4. Define where your page can load code from. A content security policy (CSP) limits the allowed origins and reduces the damage if one is compromised.
  5. Control the accounts of your tools. Two-step verification, unique passwords and a review of who has access, including on marketing platforms.
  6. Prepare the response. Who decides to disable a tool, how customers are notified and which number gets called.
Simple rule: every third-party script on your site is trust you lend to another company. Lend it only where there is a clear benefit.

What this has to do with your digital marketing

The tools that most often slip into a page are marketing ones: pixels, A/B tests, chat widgets, heatmaps. Each one helps measure and sell, but each one widens the attack surface. The key is balance: keep the ones that deliver results and remove the rest.

At LumIA MKT we build websites with as few third-party scripts as possible, protected forms and regular reviews, and we measure with the tools we actually use to optimize your paid media and your SEO.

Frequently asked questions

Can my site fall victim to an attack like this? Yes, if it loads third-party scripts. Company size does not matter: if a provider is compromised, its code reaches your page. That is why the script inventory is the first step.

What is Optimizely? It is a platform that companies worldwide use to run A/B tests, personalize content and manage experiments on their websites.

What do I do if I bought on one of these sites on November 16? As a precaution, review your card and wallet activity, and change passwords if you used the same one on several services. It is not confirmed how many users were affected.

Is a technical failure the same as an attack? No. A failure is a provider error (like the Microsoft 365 outage). An attack is a malicious action by a third party, like the code injected through Optimizely.

Do you know what third-party code your page loads?

In a free 30-minute strategy session we review your site's scripts and access with you and tell you what to fix first. Shall we review it together this week?

Sources: El Mostrador (Chile) · El Diario (Ecuador). Information current as of November 17, 2026; investigations remain open and figures may change.

Turn the idea into action

Shall we talk about applying this to your business?

Leave your details and we will reach out to book a free session. You can also subscribe to our newsletter in the footer.

What do you want to light up? (pick as many as you like)

The light is on!

We got your message and will reach out very soon. Want to move faster? Message us on WhatsApp.

Open WhatsApp