Attackers exploited a flaw in Optimizely’s website testing platform to serve code that tried to swap cryptocurrency addresses, skim card details and infect iPhones on sites of 178 organisations, including Zoom, CNN and Ledger, according to researcher Scott Helme of Report URI.
Apple said the iPhone vulnerabilities targeted were fixed last year, so up-to-date devices would have been protected.
How malicious code put crypto transfers at risk
For someone sending cryptocurrency, the danger lay in the destination address. According to Helme, the malicious code could replace an intended recipient’s wallet address with one controlled by the attackers. A sender could then approve a transfer for the correct amount while directing the funds to the wrong wallet.
That risk is behind the advice to check recent payments directly with recipients. A completed transaction shows that funds reached the address recorded on the blockchain. Someone expecting the payment can confirm whether it actually reached their wallet. The reporting did not put a value on any cryptocurrency diverted through the Optimizely incident.
Helme’s analysis also identified malicious code designed to capture payment card information that visitors entered on a page. The scripts attempted to collect browser cookies and take screenshots as well. That widened the potential exposure beyond cryptocurrency holders to people using ordinary online payment forms.
Shared website software widened the potential exposure
Optimizely attributed the incident to a “vulnerability in its Experimentation” product, according to the report. Businesses use the platform to test changes to their websites. A script supplied through that shared service can run in a visitor’s browser when a participating website loads, giving an incident at one supplier a route into projects run by multiple customers.
The list of organisations linked to the malicious code included businesses with very different services, from video conferencing and retail to banking and credit reporting. It included Zoom, Ikea, HSBC, CNN, Salesforce and Equifax. Their individual accounts show why the list alone cannot establish what happened to visitors on any one site.
HSBC, for example, said unauthorised scripts were not active on its websites. Equifax said it investigated immediately, stopped using Optimizely and found no evidence that its own systems had been compromised. Those statements address different questions. HSBC described which scripts were active on its sites, while Equifax reported what investigators had found inside the company.
Apple points iPhone users to existing security fixes
One part of the malicious code targeted vulnerabilities in Apple’s iOS. Apple said it had fixed those vulnerabilities the previous year and that iPhones running the latest software were protected against that part of the campaign. For visitors unsure whether their phones had received those fixes, Newsweek advised installing available security updates.
Apple’s statement addressed the attempt to compromise the device itself. The malicious code targeting payment details presented a separate concern for anyone who had entered card information or sent cryptocurrency while visiting an affected page. Newsweek advised checking bank accounts for unfamiliar transactions or transfers. Customers who had recently sent cryptocurrency were also advised to confirm receipt with the intended recipient.
Zoom and Salesforce disable Optimizely during reviews
Zoom said it disabled Optimizely across its production environments after learning of the incident. At the time of its statement, the company said it had identified no impact on customer data. Salesforce described its decision to disable Optimizely scripts as a precaution while its investigation continued.
Ikea said it was examining changes made through the platform. CNN did not immediately respond to Reuters’ request for comment. Neither company’s inclusion in the researcher’s findings established whether malicious code had captured information from its visitors.
Optimizely’s confirmation establishes that someone altered customer projects, and researchers have identified what the malicious code was designed to do. The outstanding question for customers is narrower and more consequential: which visitors had payment details exposed, funds redirected or devices compromised? At the time of the report, the investigations had produced no public tally of those outcomes.