Hackers Infect 178 Major Websites via Optimizely to Steal Credit Cards and Target iPhones

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


On 16 November 2026, attackers planted malicious JavaScript inside the Optimizely Web experimentation platform. The code reached visitors of 178 organizations.

The list includes some of the busiest sites on the internet, such as Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock. Researcher Scott Helme of Report URI found the campaign. He confirmed that crypto has already been stolen and traced the transactions to wallets controlled by the attackers.

This was not a simple skimmer. The malware worked as a multi-purpose kit. It swapped cryptocurrency wallet addresses, stole payment card details, grabbed cookies and screenshots, and pushed the Coruna and DarkSword exploit kits to iPhone and iPad users.

What makes the case worrying is that none of the affected websites had to be hacked directly. The bad code came through a trusted third-party script that each site loaded on every page.

Optimizely Snippet Was Abused

Optimizely Web works by having each customer load a JavaScript “snippet” from cdn.optimizely.com. The file holds Optimizely’s code, the customer’s experiments, and an optional field called Project JavaScript. Optimizely’s documentation says Project JavaScript is the first code to run in the snippet and can affect every experiment in a project.

The attacker wrote a small loader into this field and left the rest of the snippet untouched. The file was still served from Optimizely’s domain with Optimizely’s certificate, so browsers and security tools treated it as normal. In Zoom’s snippet, the added code quietly created a new script tag that pulled a file called track.js from the domain 1688360.cc.

Report URI found three versions of the loader. Most snippets used a plain script tag. Others hid the same URL in base64 with atob(), so a simple search for “1688360.cc” would miss it.

A third version carried a full inline copy of the payload and ran it through eval if the attacker’s domain was blocked. Smartsheet cleaned the snippet at one point, then re-infected it with the base64 version, showing the attacker still had access. Sites that serve the snippet from their own domain, such as Scheels and Vodafone Australia, were also affected because the content came from the same Optimizely project.

What the Malware Stole

The crypto clipper scanned each page for wallet addresses on Bitcoin, Ethereum, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin. It swapped them for attacker addresses in page text, in the clipboard, and in outgoing web requests. By 19:25 UTC, the attacker’s wallets had received about $7,040. Stolen funds were moved to exchanges at around 13:03 UTC.

The attacker added a card skimmer at 13:43 UTC. It watched form submissions for a card number, expiry date and CVV, then sent the details to 1688360.cc/card.php. Cards typed into hosted payment frames such as Stripe or Adyen were out of its reach.

Cards entered into a site’s own form fields were not. The script also sent page URLs, readable cookies and html2canvas screenshots to 1688360.cc/hit.php.

iPhones Targeted With Coruna and DarkSword

On Apple mobile devices, the script loaded a router file from .icu domains and chose an exploit chain based on the iOS version. Devices on iOS 13 to 17 received Coruna. Devices on iOS 18 received DarkSword. A separate chain for iOS 26 only fingerprinted the device.

Google’s Threat Intelligence Group says Coruna contains 23 exploits across five full chains. DarkSword links six vulnerabilities against iOS 18.4 to 18.7. Readers can find more background in our earlier reports on the Coruna exploit kit and the DarkSword iOS exploit chain.

Indicators of Compromise

Indicator Role
1688360.cc (136.113.106.136) C2 hosting track.js, card.php, hit.php
5vobauua3ojpklx.icu (34.96.213.201) iOS router boot.js
eil786npto9u5bq.icu (34.87.36.58) iOS router and Coruna pages
l7bcsnwc7nzr3uo.icu Coruna telemetry
webshell.lol Injector from an earlier wave
f7b84b9a94f749f8ced3f0112d0a66894e8bbc3b4aa5592021d1b8976a9bad40 SHA-256 of the latest track.js build

Report URI says it does not know how the attacker got write access to so many unrelated customer projects. The researchers ruled out CDN cache poisoning. The snippets for Optimizely’s own sites, including login.optimizely.com, also carried the malicious code.

Report URI said it had not heard back from Optimizely when it published its findings. Most of the code was gone by 21:52 UTC, when only TalkTalk’s snippet was still infected, down from 169 at 20:56 UTC.

Optimizely Web customers should open every Project JavaScript field and every experiment’s custom code. They should look for 1688360.cc, atob( and any script they did not write.

Optimizely’s change history logs all Project JavaScript changes. It also shows whether each change came through the REST API or the web interface. Teams should review users, API tokens and integrations, then rotate their credentials. Cards entered on 16 November, and any secrets stored in non-HttpOnly cookies, should be treated as exposed.

Content Security Policy made a clear difference. Of the affected organizations whose own websites Report URI checked, 68 had no CSP at all, and only 24 blocked the payload completely. Allowing ‘unsafe-eval’ or ‘strict-dynamic’ let the code through. Users should update to iOS 18.7.3 or later, or iOS 26.3 or later. They should also double-check any crypto transfers and card statements from that day.

The post Hackers Infect 178 Major Websites via Optimizely to Steal Credit Cards and Target iPhones appeared first on Cyber Security News.