CybersecurityVulnerabilities & Patches
Optimizely flaw hit 178 sites with malicious JavaScript
A security flaw in Optimizely allowed attackers to place malicious code on 178 organisations, affecting major retail, media and technology sites.

Key takeaways
- The Optimizely flaw let attackers serve malicious JavaScript to 178 organisations.
- The code targeted crypto wallet addresses, payment-card details and iPhone visitors.
- Optimizely says it blocked the vulnerable path, removed injected code and revoked access.
- Helme says the attackers stole just over $7,000, mostly in bitcoin.
In this article
What happened
According to TechRadar, security researcher Scott Helme found that attackers had broken into Optimizely. The Optimizely flaw allowed them to place malicious JavaScript on many popular websites. JavaScript is code that runs in web browsers. The code reached 178 organisations through 188 snippets.
Affected sites included Salesforce, CNN, BBC, Fox News, HSBC US, Equifax, Zoom, IKEA and ASOS. The incident was reported on 17 November 2026.
Optimizely is used by hundreds of organisations across many industries. The affected list included major companies. The code came from a service that many websites already trust.
How the attack worked
Optimizely is a digital experience platform. Companies use it to manage websites, run experiments and personalise content. Marketing and product teams use it to test changes and improve sales.
Customers can load a JavaScript file from Optimizely's content delivery network. A content delivery network is a system that serves files to visitors. That file can include a field called Project JavaScript.
This field holds custom code written by the customer. The code runs on every page. The field is optional. It lets customers add their own code to Optimizely's main file.
Helme says the attacker placed malicious code into that field. The file was then served from cdn.optimizely.com. It used Optimizely's security certificate and a host that visitors already trusted.
Optimizely says the attacker exploited a weakness in the signup process for Experimentation accounts. This allowed the attacker to add the code to customer projects.
What the code did

The malicious code had several aims. It used clipboard jacking. This means it watched the clipboard for copied cryptocurrency wallet addresses. It replaced them with addresses controlled by the attacker when the victim pasted them.
A user could copy one address and paste another without noticing. The change happened when the victim pasted the address.
The code also searched pages for payment-card numbers, expiry dates and CVV security codes. When it found all three, it sent the details to a server controlled by the attacker. Cards entered through hosted payment iframes were outside its reach.
These are embedded payment forms from providers such as Stripe and Adyen. The card-stealing code did not target every payment flow. It focused on card details entered directly into the page.
Visitors who opened affected sites on iPhones or iPads were served Coruna and DarkSword. These are exploit kits that abuse unpatched iOS vulnerabilities. Helme says they tried to steal sensitive information.
This included wallet credentials. It also included recovery phrases. He also says the attackers stole just over $7,000.
Around $5,300 was in bitcoin. The rest was in litecoin, USDT and ether. The crypto theft relied on changing copied text rather than breaking into wallets.
Who was affected
The affected organisations came from several sectors. Banking and finance accounted for 32. Technology and software-as-a-service firms accounted for 23. Retail and fashion accounted for 20.
Other named victims included Alaska Airlines and Hawaiian Airlines, Virgin Media, Virgin Media O2, Vodafone Australia, O2 and Ledger. The named victims included airlines, telecoms, banks and retailers.
Helme says that in under a day, the number of infected snippets had fallen to one. That remaining snippet belonged to TalkTalk.
Most of the malicious code had been removed by then. One infected snippet remained at that point.
What Optimizely did next
Optimizely says it blocked the vulnerable signup path. It deployed a fix and removed injected code from customer projects. It also ended active sessions.
It revoked tokens used for access and reset access for affected accounts. In addition, it blocked code from being delivered through Cloudflare.
The incident affected many pages because Optimizely code can run across a business's website. A single compromised project can therefore affect a wide group of visitors. Website owners and readers should follow Optimizely's official advisory and vendor guidance for the latest security steps.
Sources
Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.



