CyberSIXT reportingUpdated
Suspected Optimizely breach planted card stealer on 186 websites
Part of the Optimizely story · since 16 Nov
- Mon 16 Nov, 21:41 UTC. cybersixt, first report. Suspected Optimizely breach planted card stealer on 186 websites. This article, 1st of 1.
Updated 16 November, 22:15 UTC. Hudson Rock says four script providers served the code, some from as early as 13 November, and that blocking the attackers' domains does not stop it.
Malicious JavaScript served through third-party scripts reached at least 186 widely used websites, stealing card details, cookies and screenshots and swapping cryptocurrency addresses so that payments went to the attackers, security researcher Scott Helme, founder of the website script-monitoring service Report URI, said on X on Monday. Threat intelligence firm Hudson Rock has since published an analysis tracing the code to the servers of four script providers: Optimizely, Kissmetrics, StorifyMe and minute-ly.
Hudson Rock says it recovered eight poisoned Optimizely project files and the malicious minute-ly loader itself, and that archived captures supplied by Kirk from Ohey showed the same loader on Kissmetrics and StorifyMe responses. It names 21 affected websites as "a documented subset", including the BBC, Zoom, CNN, Fox News, Salesforce, HSBC UAE, Mutual of Omaha, the Sydney Morning Herald and about.gitlab.com. The earliest capture in its set is from 13 November at 05:42 UTC. Optimizely, which sells A/B testing and website experimentation tools, has not commented, and its status page lists no security incident.
What the malicious script did
According to Helme, the payload stole card numbers, cookies and screenshots, swapped crypto addresses on the page and in the clipboard, and served exploits he named as DarkSword or Coruna iOS exploits. About $7,000 had reached the attackers across Bitcoin, Litecoin, Tron and Ethereum, all checked on-chain, he said. Hudson Rock's analysis says the card skimmer watched forms and web requests for valid card numbers and sent them to 1688360[.]cc/card.php, while a separate branch sent iPhones through loaders on webshell[.]lol to exploit-kit servers. It found evidence of delivery only, not of any iPhone being compromised.
Why blocking the domains is not enough
Helme published seven domains for defenders to block: 1688360[.]cc and six .icu domains. Hudson Rock says that does not remove the threat on its own. The poisoned scripts on the BBC and HSBC UAE carried a full copy of the payload, which runs if the attackers' server cannot be reached within 2.5 seconds, so address swapping continues even when the domain is blocked. The poisoned code itself has to be removed from the provider's script.
The clean-up
Helme said at 21:32 UTC that the provider was aware and cleaning the files, with 41 of 188 infected script files still infected. A second researcher, who posts as @0x627269616e and had flagged GitLab at 18:36 UTC, wrote that "it looks like Optimizely may have fixed the compromise". We fetched the Optimizely snippets used by GitLab, Zoom, Optimizely, Stamps.com, Hootsuite, Smartsheet, Tricentis and American Girl: none contained the domains any longer, and every one had been republished between 20:56 and 21:38 UTC, while archived copies show GitLab's snippet unchanged throughout 15 November. Public urlscan.io scans record pages on bbc.com, zoom.com, salesforce.com, cnn.com and optimizely.com itself contacting 1688360[.]cc on Monday.
What to do
Sites that load Optimizely, Kissmetrics, StorifyMe or minute-ly scripts should check what their script serves now, keep copies of the responses and project revisions before restoring anything, review recent project changes, account activity and API keys with each provider, and block the attackers' domains as well, Hudson Rock advises. Anyone who sent cryptocurrency after copying or pasting an address on a large website since 13 November should check that it reached the intended address, and anyone who entered card details on such a site should watch their statements.
What is not known
None of the four providers has said how the code got into its scripts. No one has established how many visitors were affected, how much was stolen in total, or who is behind the attack.
How the story developed
1 article from 1 outlet since 16 Nov. Still developing; the latest report was 1 hour ago. This was the first report.
- Mon 16 Nov, 21:41 UTC. cybersixt, first report. Suspected Optimizely breach planted card stealer on 186 websites. This article, 1st of 1.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Mon 16 NovDay 01
- Suspected Optimizely breach planted card stealer on 186 websites21:41 · cybersixt · First report · This article, 1st of 1
Sources
- Hudson Rock (InfoStealers): poisoned scripts on BBC, Zoom and other major websitesPrimary sourceinfostealers.com
- Scott Helme on X: 186 sites confirmed infectedPrimary sourcex.com
- Scott Helme on X: malware capabilitiesPrimary sourcex.com
- Scott Helme on X: about $7k received on-chainPrimary sourcex.com
- Scott Helme on X: IOC 1688360[.]ccPrimary sourcex.com
- Scott Helme on X: additional IOCsPrimary sourcex.com
- Scott Helme on X: first payloads about six hours earlierPrimary sourcex.com
- Scott Helme on X: provider cleaning files, 41 of 188 remainPrimary sourcex.com
More reporting
- BundID cyberattack locks German accounts, email codes now required16 Nov
- Trezor data breach at shipping partner exposes 27,000 orders16 Nov
- Fugaku supercomputer hit by cyberattack, users' SSH keys stolen16 Nov
- Lighter DEX exploit drains $10.4M via a trader's leaked API keys16 Nov
- Coles cyber incident: no evidence of customer data breach so far16 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS