A Hijacked Optimizely Script Served Card-Skimming and iPhone Exploit Malware on 178 Big-Brand Websites, Proving Your Vendor’s Code Is Your Breach
For most of Monday, November 16, some of the most visited websites in the world were quietly handing their visitors malware, and none of those companies had been hacked. The code came from Optimizely, a popular website experimentation and personalization platform whose JavaScript sits inside thousands of corporate web pages. An attacker abused a flaw in Optimizely’s account signup process, slipped malicious code into customer projects, and let Optimizely’s own trusted delivery network do the rest.
By the time the injected code was cleared, security researcher Scott Helme’s team at Report URI had found it in 188 of the 1,611 Optimizely scripts they examined, belonging to 178 organizations, according to BleepingComputer. On November 17, Optimizely published a detailed incident report with a timeline, and the security community has spent the past day arguing about what it means for every business that loads third-party code on its site.
What Happened, Hour by Hour
Optimizely’s report says the first impersonated user account was created at 00:37 UTC on November 16, and the first malicious code was written into a customer project at 07:51 UTC. The company detected the activity at 13:34 UTC, blocked the malicious outbound code at Cloudflare at 16:06, closed the vulnerability at 16:10, and removed the injected code from all affected projects by 22:24 UTC. That is an exposure window of roughly 14 and a half hours for the worst-hit sites.
The company stresses that this was not a password breach. The flaw let the attacker act as administrator users without their credentials, and only the Web Experimentation product was involved; Feature Experimentation, the SDKs and legacy Full Stack were not affected. Optimizely has brought in Mandiant to run an independent forensic investigation and says it has contacted each affected customer directly.
A Who’s Who of Victims
BleepingComputer confirmed through urlscan.io records that the malicious script loaded, or tried to load, on sites run by Zoom, CNN, Fox News, the BBC, Salesforce, GitLab, KLM, Air France, HSBC Insurance, Mutual of Omaha, American Eagle, Smartsheet, Stamps.com, Bitly and UNICEF USA, among others. The Record reported that the code landed on 32 finance or banking websites, and that Helme had first seen the same injected code on Turkish websites back in September, suggesting this was not the attacker’s first run.
Salesforce told BleepingComputer it had disabled Optimizely scripts across its preview and production instances as a precaution while it investigates.
What the Malware Did
The tampered Optimizely files pulled in a second script, track.js, from an attacker-controlled domain. According to BleepingComputer’s and Report URI’s analysis, it was a multi-purpose kit:
- Crypto clipping: it watched pages for cryptocurrency wallet addresses and swapped them for the attacker’s, hijacking transfers.
- Card skimming: it captured card numbers, expiry dates and security codes typed into the sites’ own forms.
- Data theft: it could collect cookies, page URLs and screenshots.
- iPhone exploitation: on iPhones and iPads it loaded the Coruna and DarkSword exploit kits, which target different iOS versions through the browser.
The money trail that can be measured is small. Wallets embedded in the script had received about $7,000 as of November 16, BleepingComputer reported, though some of those wallets were active before the attack. The damage that cannot be measured is the bigger worry. Peter Lowe, threat research lead at ZeroFox, told TechTarget that “money is only the part we can count,” pointing to stolen cookies, cards typed into sites’ own forms, and exploit chains served to unpatched iPhones. The Record notes that iVerify recently found about 75% of its detections of this kind of mobile spyware involve criminal groups using Coruna or DarkSword.
Why It Matters for Business
The uncomfortable lesson, as Helme put it to TechTarget, is that none of the victims were breached in the usual sense. Their servers were untouched. A vendor’s script turned hostile, and their websites served it to every visitor anyway. George Gerchow, CSO at Bedrock Data, summed up the liability question bluntly in the same report: “When it runs on your page and skims your customer’s card, it’s your breach, not your vendor’s.”
In a blog post on November 17, Helme argued that most companies apply strict review, testing and approval to the code they deploy on their own servers, then let a single script tag fetch and run whatever a third party serves, with no review at all. Tools like Optimizely are dynamic by design, built so marketing teams can change a live site without a code release. That convenience is exactly what made this attack possible. TechTarget also reported that some victims who served Optimizely’s snippet from their own domains were still infected, because they proxied the live file rather than pinning a reviewed copy.
There is a regulatory edge too. Any company that took card payments through its own forms on an affected page may have to treat every card entered during the window as exposed, which brings breach notification, card-brand rules and customer trust into play. Optimizely notes that cards entered in hosted payment iframes, such as Stripe or Adyen, were out of the skimmer’s reach, which is a strong argument for keeping card entry off your own page entirely.
What to Do Now
- If you use Optimizely Web Experimentation, confirm with your account team whether you were affected, review your Project JavaScript, and rotate the users, tokens and integrations that can write to it.
- Pull logs for November 16 between 07:51 and 22:24 UTC, check content security policy reports and outbound traffic, and block the indicator domains Optimizely published.
- Deploy a Content Security Policy. Lowe suggested starting in report-only mode, which breaks nothing and builds an inventory of what actually loads on your pages. Optimizely says sites with a strong CSP were protected.
- Move card entry into a hosted payment field, and alert on any new or changed script on login and checkout pages.
- Tell customers who use iPhones and iPads to keep them fully updated.
The Same Week, Another Trusted-Software Trick
Optimizely is not the only story about trusted software being turned into a carrier. On November 18, Help Net Security detailed ReversingLabs’ research into BubbleLoader, a loader that patches legitimate Windows programs such as WinRAR, Windows Media Player and the Firefox launcher, hiding its encrypted code inside a fake PNG image and changing its payload’s fingerprint every time it runs. ReversingLabs recommends strict application allowlisting and code-signing checks. The common thread is clear: attackers increasingly hide inside things businesses already trust.
The Bottom Line
The Optimizely attack was contained within a day, and the stolen crypto so far is modest. But it showed that an attacker with one vendor flaw could run code on the BBC, Zoom and dozens of banks at once. Every script your website loads is part of your attack surface, and your customers will hold you, not your vendor, responsible for what it does.
Never miss a customer call during a security scare. When an incident hits, worried customers phone in all at once. MAJ.COM Voice AI puts 24/7 AI voice agents on every inbound call and handles outbound sales and support, so your team can focus on the fix while no lead or customer goes unanswered. Learn more about MAJ.COM Voice AI.
Edited by Coron @QUE.COM
Website: https://QUE.COM Intelligence
Sponsored by: https://MAJ.COM AI Autonomous
Discover more from QUE.com
Subscribe to get the latest posts sent to your email.
