Visitors to some of the world's most recognizable websites spent roughly 17 hours on Monday exposed to malicious code that could steal their payment cards, swap their cryptocurrency wallet addresses, and attempt to exploit unpatched vulnerabilities in their iPhones, after attackers quietly modified JavaScript snippets served by marketing platform Optimizely.
The campaign, which researchers at Cynet and StepSecurity have named OPTIMJACK, touched at least 178 organizations including CNN, the BBC, Zoom, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, and Peacock. Optimizely's own main site and login page were also affected.
How the Attack Got In
Optimizely Web Experimentation works by having client websites load a small JavaScript file, known as a snippet, from cdn.optimizely.com. Each snippet then executes what Optimizely calls "Project JavaScript," a customizable field that site operators can populate with their own code for A/B testing and personalization experiments. The attacker used a flaw in Optimizely's account signup flow, according to the company's incident notice, to gain write access to that field across unrelated customer projects and planted a loader inside it.
Because the modified snippets still came from Optimizely's own domain over a valid certificate, nothing about the delivery chain flagged the change. Organizations that cached and served the snippet from their own infrastructure were also affected, since the payload content came from the same compromised project fields.
The loader itself came in three forms: one that fetched the payload directly, one that encoded the payload domain in base64 to avoid string-matching detection, and a third that bundled a full copy of the payload inline as a contingency if the domain was blocked.
A Tight, Eventful Timeline
The first injection appeared at 04:21 UTC on Monday in the BBC's snippet, loading a domain researchers identified as webshell[.]lol, an injector already linked to this actor. That same injector had previously appeared through scripts belonging to Kissmetrics, StorifyMe, and Minute Media starting the prior week, and first showed up on Turkish websites as far back as September 17.
The card skimmer component went live at 13:43 UTC. Between 17:13 and 17:57, every visitor arriving from iOS 18.6 or earlier was served a hidden iframe pointed at known exploit kits. Mass cleanup began around 20:40. TalkTalk's snippet was the last to be cleared, at 21:52.
What the Payload Actually Did
The injected code carried four distinct capabilities. The crypto address swapper monitored page text, form fields, links, the clipboard API, and outgoing network requests. When it found a valid wallet address near payment-related words like "wallet," "deposit," or "send," it replaced that address with one controlled by the attacker. The swap was precise enough to pass checksum validation for each blockchain, meaning it only substituted addresses that the page or the user's application would have accepted as legitimate.
The card skimmer captured payment card numbers, expiration dates, and CVVs submitted through a site's own form fields, then transmitted them to 1688360[.]cc. It could not read card data entered into cross-origin payment iframes, which covers hosted fields from providers like Stripe and Adyen.
After any crypto address swap, the payload also harvested the page's cookies and took a screenshot of the visible content, sending both to the attacker's server. HttpOnly cookies, which are inaccessible to JavaScript by design, were not captured.
The iOS component loaded a second-stage script that checked the device's software version and routed it to one of three exploit chains: Coruna targeting iOS 13 through 17.2.1, DarkSword targeting iOS 18.4 through 18.7, and a third chain for iOS 26 that researchers say currently only collected device fingerprints. Affected pages reloaded every 60 seconds to retry the exploit, a behavior that observant users might have noticed. No confirmed device compromises on physical iPhones have been reported.
The Money
By 19:25 UTC Monday, the attacker's cryptocurrency wallets had received roughly $7,040 across a window of about nine hours, according to Report URI. StepSecurity put the figure at approximately $6,600. Researchers noted that two of the wallet addresses were already in use before Monday's injections started, so it is not possible to attribute every incoming transfer directly to victims of this campaign.
What to Do Now
Security firms advise anyone who entered payment card details on Monday on a major commercial website to treat the card as potentially compromised. Crypto payments made that day should be compared against intended recipient addresses on a hardware wallet screen rather than from copied text, since clipboard contents may have been silently altered.
Site operators using Optimizely should inspect every Project JavaScript field for strings like "1688360", `atob(`, or scripts they do not recognize, and audit all
[…]
Content was trimmed to protect the source. Please visit the original article for the full text.
Read the original article:
