Optimizely Cyberattack Explained: How Trusted Websites Delivered Malicious Code
A Familiar Website Can Deliver Malicious Code Through A Service Its Visitors Never See.
Websites associated with HSBC, IKEA and Zoom have been named in a cyberattack involving Optimizely, a service businesses use to test and personalise their webpages. Security researchers identified malicious scripts designed to interfere with payments and target Apple mobile devices.
Optimizely has confirmed that an unauthorised party exploited a vulnerability and added malicious JavaScript to customer projects. The company says it has fixed the vulnerability and removed the injected code.
The central uncertainty is the scale of the damage. Finding malicious code associated with a website does not establish that every visitor lost information, that every attempted device infection succeeded, or that the company’s internal systems were breached.
What Happened?
Security researcher Scott Helme, of Report URI, identified affected scripts associated with 178 organisations on 16 November 2026. The names included HSBC, IKEA, Zoom, Salesforce, Equifax, the BBC and CNN.
His team examined 1,611 distinct Optimizely snippets and found malicious code in 188. Those figures measure the researchers’ findings across the scripts they could locate; they are not a count of infected customers.
The common connection was Optimizely Web, which allows businesses to experiment with how their sites look and behave. A company can use such a service to test a different page layout or change what visitors see.
That arrangement gives externally supplied code a legitimate role inside a familiar website. In this incident, attackers used that route to introduce unauthorised behaviour.
How Could One Service Affect So Many Websites?
StepSecurity’s technical analysis describes malicious code added to customer projects’ custom JavaScript fields. The resulting scripts were delivered through Optimizely’s infrastructure.
This helps explain why the attack crossed industries. A bank, furniture retailer and communications company do not need to share their main computer systems to share a website supplier.
For visitors, the practical problem is that recognising a brand does not reveal every piece of software running on its pages. The address in the browser can belong to the intended business while an embedded component behaves maliciously.
The security question therefore extends beyond who owns the website. It also concerns who can change the code that website asks visitors’ browsers to execute.
That is a different form of exposure from the interference with physical equipment examined in supermarket freezer cyberattacks, but both raise questions about access through connected systems and outside providers.
What Was The Malicious Code Designed To Do?
The technical analysis describes several functions.
One targeted cryptocurrency payments by replacing a legitimate destination address with an attacker-controlled address. That could cause someone to authorise a transfer to the wrong recipient.
Another component sought payment-card information entered into accessible website forms. StepSecurity found an important limitation: the skimmer could not read card fields inside a payment frame isolated on a different origin.
The researchers also described a function that captured a webpage image and accessible cookies after a cryptocurrency-address substitution. Their analysis says cookies protected by the HttpOnly setting were outside that function’s reach.
These details matter because the software’s capabilities and an individual visitor’s exposure are different questions. What happened would depend on the page, its implementation and what the visitor did while the malicious code was present.
Were iPhones And iPads Targeted?
Helme’s investigation identified delivery of exploit kits targeting iPhones and iPads, including software known as Coruna and DarkSword.
An exploit kit attempts to take advantage of software vulnerabilities. Its delivery establishes an attempted route into a device; it does not, by itself, establish that the device was successfully compromised.
Readers should therefore be wary of claims that everyone who opened a named website had their phone hacked. The available evidence does not support that conclusion.
Apple advises keeping devices updated as an important security measure. On an iPhone or iPad, open Settings, select General and then Software Update to check what is available for that device. Back up the device and follow Apple’s installation instructions.
Updating addresses available software fixes. It does not retrospectively establish whether an earlier visit resulted in harm.
What Have The Companies Said?
As of 17 November, the responses included several different positions.
HSBC said unauthorised scripts were not active on its websites.
IKEA said it was investigating the incident involving Optimizely. Salesforce also said it was investigating and had disabled the platform’s scripts as a precaution.
Equifax said it had stopped using the platform and had found no evidence of a compromise to its systems.
These statements should be read within their scope. A finding about a company’s own systems does not necessarily answer every question about code previously delivered to visitors.
Has The Attack Been Stopped?
In a status update published at 01:02 GMT on 17 November, Optimizely said it had fixed the vulnerability, removed the injected code, secured affected accounts and introduced additional protections against unauthorised code delivery.
The incident was listed as being monitored.
Those actions address the delivery mechanism described in the company’s notice. They do not amount to a final assessment of every customer’s exposure or every visitor’s losses.
There are two separate tasks after an incident like this: stopping further malicious activity and investigating what happened before it stopped. Progress on the first can be substantial while the second remains incomplete.
What Should Visitors Check?
For people who used an affected site on 16 November, Helme’s recommendations focus on device updates and payment checks.
Review cryptocurrency transfers made during the relevant period. Check the destination against the address you intended to use, rather than assuming that copying and pasting preserved it correctly.
If you entered card details, watch for unfamiliar transactions. Report suspicious activity through your card provider’s normal, trusted contact route.
Follow notices from the particular service you used. A company-specific notice may identify affected pages, times or actions more precisely than a general list of brands.
There is no basis for assuming that using Zoom for a call, owning an IKEA account or banking with HSBC automatically means you suffered a compromise.
What Remains Unknown?
The reviewed disclosures do not establish a complete victim count, a final financial loss or the number of successfully compromised devices. Nor do they establish who was responsible.
The number of organisations named should not be used as a substitute for those answers. As with claims about the scale of automated hacking, reach and successful exploitation require different evidence.
The most useful next disclosures would identify which pages served the code, when they did so and what investigators found about actual consequences. That would allow visitors to move from a worrying brand name in a headline to a more precise assessment of their own exposure.
Sources
Optimizely — Web Experimentation Security Incident — Confirmation of the incident and the company’s remediation statement.
Scott Helme, Report URI — World’s Largest Brands Infected With Malware Via Optimizely — Researcher findings, affected-script counts and visitor recommendations.
StepSecurity — OPTIMJACK: Optimizely-Hosted Scripts Loaded a Crypto Clipper and Card Skimmer on 178 Organizations — Technical analysis of the delivery mechanism and malicious functions.
Reuters — Popular Websites Compromised in Bid to Steal Crypto, Target iPhone Users — Company responses and uncertainty about resulting compromises.
Apple — Update Your iPhone or iPad — Official software-update instructions.
Next Reads
Why Would Someone Hack a Supermarket Freezer? The Damage Goes Beyond Data — How digital access can create consequences beyond stolen information.
How Much Hacking Can One Person Automate? AI Is Shrinking the Team — Why attempted attacks and demonstrated results need separate measures.
ChatGPT Wallet Explained: How AI Can Shop for You Without Seeing Your Card Number — A separate examination of payment information, permissions and online checkout.