
Hijacked Optimizely Scripts Served Card Skimmer and iOS Exploit Kits to CNN, BBC and Zoom Visitors - The Hacker News
An attacker exploited a vulnerability in Optimizely Web Experimentation to inject malicious JavaScript into customer websites, serving card skimmers and iOS exploit kits to visitors of major organizations.
The attack began at 04:21 UTC yesterday, when the first malicious script was injected into the BBC's Optimizely project. By 21:52 UTC, the attacker had successfully planted code in 188 of 1,611 snippets checked by Report URI, affecting 178 organizations.
The code was served from the vendor's own CDN, cdn.optimizely.com, using Optimizely's legitimate certificate, making it difficult to detect. Report URI researchers traced the loader to a file served from this host and captured the code on CNN and Zoom pages.
How the Attack Worked
Optimizely customers load a script called a snippet to run experiments on their pages. The attacker exploited a vulnerability to add a loader into the Project JavaScript field of customer projects, leaving the rest of the snippet untouched.
The loader came in three versions, with the most common version loading 1688360[.]cc/track.js directly. A second version hid the address in base64, and a third carried a full copy of the payload that runs if the domain is blocked.
The payload, a file called track.js, replaced valid crypto wallet addresses with the attacker's in page text, forms, links, the clipboard, and outgoing requests. It could also swap an address that passes its chain's checksum and sits near a payment word such as wallet, deposit, or send.
Copying is not safe either: an address a visitor copies from one of these pages may already be the attacker's by the time it is pasted into a wallet.
Card Skimmer and iOS Exploit Kits
A card skimmer added at 13:43 UTC captured the card number, expiry date, and CVV when they were submitted via the site's form fields and sent them to the attacker's server. It could not read cards entered in a cross-origin payment iframe, such as Stripe's hosted fields or Adyen's.
On iPhones and iPads, the code loaded a script called boot.js from two .icu domains, which read the iOS version and opened an exploit chain in a hidden iframe. The firm identifies the iOS exploit kits as Coruna and DarkSword.
The Coruna exploit kit targets iOS 13.0 to 17.2.1, and the DarkSword exploit kit targets iOS 18.4 to 18.7. Between 17:13 and 17:57 UTC, the attacker added a Coruna iframe to every visit from iOS 18.6 or earlier, causing pages to reload every 60 seconds to retry the exploit.
Cynet's researchers retrieved the second stage using an emulated iPhone browser and describe what they saw as conditional delivery, "not a successful compromise of a physical iPhone or iPad." The firm says crypto has already been stolen.
Impact and Response
The attack affected major organizations including Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, and Peacock. Smartsheet's script was cleaned once and then re-infected with a hidden version of the code, indicating the attacker still had access at that point.
As of 19:25 UTC yesterday, the attacker's wallets had received about $7,040, all within roughly nine hours. Two of the addresses were already in use before the injections began, and its analysts wrote that "the chain does not show which transfers came from victims."
Optimizely said the attacker had "exploited a vulnerability in Experimentation" and used it to add malicious JavaScript to some customer projects. The vendor has taken steps to secure affected user accounts and added protections to stop unauthorized code from being delivered.
What to Do Next
For site owners, Report URI recommends opening the Project JavaScript in every project and the custom code in every experiment to look for 1688360, atob(, or any script you did not write. They should also review which users, API tokens, and integrations can write to their account and rotate their credentials.
For visitors, the firm advises updating iPhones and iPads to iOS 18.7.3 or later, or iOS 26.3 or later. Anyone who paid by card on an affected site on Monday should watch their card statements, and anyone who made a crypto payment that day should compare the address they meant to pay with the one they used.