The injected JavaScript targeted cryptocurrency transfers and payment information while attempting to exploit vulnerable iPhones and iPads.
SAN FRANCISCO, Calif. — An attacker exploited a flaw in Optimizely’s Web Experimentation service to insert malicious JavaScript into customer projects, allowing harmful code to reach visitors to websites tied to 178 organizations, according to the company and security researchers.
The Nov. 16 incident affected a widely used service that lets organizations test and change website content. Security researcher Scott Helme and his team at Report URI said they examined 1,611 Optimizely snippets and found malicious code in 188 snippets associated with 178 organizations. The list included major companies and organizations such as Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock. Optimizely later said fewer than 5% of its customers were affected.
Optimizely said an unauthorized third party exploited a vulnerability in the signup process for its Web Experimentation product. The flaw allowed the attacker to impersonate users on targeted customer accounts and add JavaScript to customer projects without obtaining those users’ passwords. The company said the incident was not caused by a compromised Optimizely administrator account and that it found no evidence customer passwords were exposed.
Because affected websites normally loaded Optimizely code as part of their operations, visitors could receive the malicious software while browsing legitimate sites. The attack did not require the intruder to separately break into each organization’s network. Optimizely said the exposure occurred through websites using affected projects rather than through those organizations’ internal networks, making the episode an example of the broader risk created by trusted third-party software embedded across many unrelated sites.
Report URI said the malicious code was built to interfere with cryptocurrency transactions, collect payment-card information, take screenshots and capture browser cookies that were accessible to JavaScript. Researchers said it could replace cryptocurrency wallet addresses with an address controlled by the attacker, potentially redirecting transfers. It also attempted to send additional exploit code to some iPhones and iPads. Reuters reported that Apple said the iOS vulnerabilities targeted in the campaign had already been fixed for users running current software.
The available evidence does not show that every visitor who received the code lost information or money. Reuters said it could not determine how many people were affected or whether all of the malicious functions succeeded. Researchers could identify cryptocurrency transactions connected with wallets associated with the operation, but those records could not establish how many payment-card details, cookies or screenshots may have been collected. No successful compromise of an iPhone or iPad through the campaign had been publicly confirmed.
Optimizely’s initial incident report said the first malicious code in its investigation was written at 7:51 a.m. UTC on Nov. 16. The company detected the activity at 1:34 p.m. UTC, closed the exploited vulnerability at 4:10 p.m. UTC and removed the injected code from affected projects by 10:24 p.m. UTC. Optimizely said it also blocked delivery of the code and added protections intended to prevent similar unauthorized changes.
The company said the attack was limited to Web Experimentation and that it found no indication other Optimizely products were affected by the same incident. It contacted Web Experimentation customers directly to tell them whether their projects were involved. Optimizely also said outside experts were assisting with its investigation and that the malicious code had been removed from its systems.
Several organizations named in reporting on the incident began their own reviews after the attack became public. Reuters reported that Equifax and Zoom were among companies that said they had found no evidence their systems or customer data were compromised. Other organizations disabled Optimizely-related scripts or investigated their exposure. Those findings do not establish the result for every organization whose website may have loaded an affected project because configurations and visitor exposure differed from site to site.
The attack also showed how a weakness in one widely trusted website service can create exposure across many industries at once. Web experimentation and analytics tools commonly run code inside visitors’ browsers, giving attackers a potentially broad delivery path if they can alter that code. Report URI said some websites with restrictive browser security controls were able to block portions of the attack even though the initial Optimizely script came from a trusted source.
Optimizely said in its latest advisory that the vulnerability had been closed, the injected JavaScript had been removed and no malicious code from the incident remained in its systems. The attacker has not been publicly identified, and the total number of visitors who may have had information accessed remains unknown as affected organizations continue reviewing their exposure.
Author note: Last updated November 21, 2026.