Business WWC APAC Desk

Optimizely Confirms iPhone Crypto Attack Route – But How Much Data Was Actually Exposed?

Optimizely Confirms iPhone Crypto Attack Route – But How Much Data Was Actually Exposed?

Optimizely has disclosed new technical details about a November 16, 2026, security incident in which an unauthorised party inserted malicious JavaScript into selected customer website projects. The injected code was designed to target cryptocurrency transactions, payment-card information and older Apple operating systems, although the company has not confirmed how much information, if any, was successfully stolen.

The incident involved Optimizely Web Experimentation, a service that allows organisations to test website content and layouts. The company’s November 17 security report explains that an attacker exploited a weakness in the platform’s account signup process to impersonate users with administrator privileges and modify JavaScript in customer projects.

This distinction matters: the incident did not establish that every affected organisation’s internal network or customer database was breached. The malicious code was delivered through website pages that loaded the compromised experimentation scripts.

How the Optimizely security breach happened

Optimizely identified the first malicious code written into a customer project at 07:51 UTC on November 16. It detected the activity at 13:34 UTC, blocked malicious outbound code at 16:06 UTC and closed the exploited vulnerability at 16:10 UTC.

The company said it removed the injected code from all affected projects by 22:24 UTC that day.

The attack did not depend on stealing customer passwords. Instead, the unauthorised party exploited a flaw that allowed newly created accounts to impersonate users on selected customer accounts.

Optimizely said this was not a breach of its administrator credentials and that it had no evidence customer passwords were exposed.

The company also confirmed that the incident was limited to Web Experimentation. It reported no indication that other Optimizely products, including Feature Experimentation, software development kits and legacy Full Stack, were affected.

What the malicious code was designed to steal

The security report identifies two principal financial targets: payment-card information entered directly into website forms and cryptocurrency transfers.

The injected code could attempt to replace a cryptocurrency destination address with one controlled by the attacker. This creates a particularly serious risk because a user could believe a transfer is going to the intended wallet while the destination has been changed.

The code also targeted card numbers, expiry information and other payment details entered into forms on affected pages.

Optimizely said hosted payment fields, such as those provided through Stripe or Adyen iframes, were outside the script’s reach because of browser security restrictions.

The company also found that the malicious code could collect certain browser information and screenshots in circumstances involving cryptocurrency wallet-address replacement. Its preliminary analysis said it did not find evidence that the code read session or local storage.

Importantly, the report does not establish that every targeted visitor had information stolen. Optimizely said it could determine when injected code was loaded, but could not independently confirm whether the code successfully extracted information from each visitor.

Why older iPhones faced an additional risk

The incident also involved a separate stage targeting older Apple operating systems.

Optimizely’s preliminary technical findings identified an exploit attempt against iOS and iPadOS versions 18.6 and earlier. This was separate from the code targeting cryptocurrency transfers and payment-card forms.

Apple’s published security guidance says the vulnerabilities involved in the reported web attacks had been addressed through software updates. The company says devices running updated versions of supported iOS releases are protected against those specific attacks.

Apple advises users to install the latest software available for their particular devices. Its guidance also identifies Lockdown Mode as an additional protective measure for users who cannot immediately update.

This does not mean every iPhone that visited an affected website was infected. The presence of malicious code and a successful device compromise are two different findings.

How many organisations and customers were affected?

Security researcher Scott Helme identified malicious scripts associated with 178 organisations after examining Optimizely website snippets. That figure describes organisations whose scripts were identified in the investigation, not 178 confirmed cases of customer-data theft.

Optimizely separately said fewer than 5% of its customers were impacted. It also said it had contacted Web Experimentation customers directly to confirm whether their projects were affected.

The company has not published a verified count of visitors whose payment details or cryptocurrency transfers were successfully compromised.

It has engaged Mandiant to conduct an independent forensic investigation. The final findings, including the complete root-cause assessment and final indicators of compromise, remained pending in the November 17 report.

What website operators and users should do

Optimizely advised Web Experimentation customers to review their websites during the exposure window of 07:51 to 22:24 UTC on November 16.

Its recommendations include checking browser requests to unfamiliar domains, reviewing payment-card and cryptocurrency transactions, retaining relevant server and security logs, and confirming that a strong Content Security Policy is in place.

The company said customers that had temporarily disabled the Web Experimentation snippet could safely restore it following remediation, although organisations may continue their own reviews before doing so.

For ordinary users, practical precautions include installing available device updates, reviewing financial transactions and checking cryptocurrency transfers made during the incident window.

Anyone who notices an unfamiliar card transaction should contact the issuing bank through an official channel. Cryptocurrency users should independently verify destination addresses before approving future transfers.

WWC has previously examined other cybersecurity incidents, including the MoneySmart customer-data exposure and the Fugaku supercomputer security incident. These are separate cases, but they illustrate why organisations must assess risks involving external technology providers as well as their own systems.

What happens next

The immediate vulnerability has been addressed, and Optimizely says malicious code has been removed from affected projects. However, the forensic investigation remains important because remediation does not automatically establish whether information was successfully taken during the exposure period.

The outstanding questions concern the number of visitors who encountered the malicious code, whether any financial information was actually extracted, and whether affected organisations need to notify customers or regulators.

For now, the confirmed lesson is that third-party website software can become a security risk even when the organisation using it has not suffered a direct intrusion into its own network.

Frequently asked questions

Was Optimizely hacked in November 2026?

Optimizely confirmed that an unauthorised third party exploited a vulnerability in its Web Experimentation signup flow and inserted malicious JavaScript into some customer projects.

Were cryptocurrency funds stolen?

The malicious code was designed to redirect cryptocurrency transfers by replacing wallet addresses. The public incident report does not establish how many transfers, if any, were successfully diverted.

Were all iPhone users at risk?

No. The additional exploit attempt targeted older iOS and iPadOS versions, specifically versions 18.6 and earlier. Apple says updated devices are protected against the specific web attacks addressed by its security updates.

Did the attack expose customer passwords?

Optimizely said this was not a credentials breach and that it had no evidence customer passwords were exposed.

Has Optimizely fixed the vulnerability?

Yes. The company said it closed the vulnerability on November 16 and removed the injected code from affected projects by 22:24 UTC that day. Its forensic investigation was still continuing in its November 17 report.

Get our stories first on Google

More in Business

See all in Business