Security firm Report URI says an attacker wrote malicious code into Optimizely customer projects on 16 Nov, so 178 organisations’ websites served a script that swapped crypto addresses, skimmed cards and attacked older iPhones. About $7,000 reached the attacker’s wallets.

SECURITY ALERT

The websites were never breached.

The tool they trusted was.

Visitors to 178 organisations’ websites were served malicious JavaScript on 16 November through Optimizely’s web-testing platform, security firm Report URI said in a post by researcher Scott Helme.

The list includes Ledger, HSBC, the BBC, CNN, Zoom, Salesforce, GitLab, IKEA, Equifax, Air France-KLM and Peacock, Report URI said.

Its crawl found 188 infected snippets among the 1,611 Optimizely files it checked.

Optimizely says an unauthorised party used a flaw in its Experimentation sign-up flow. It says that path is now blocked and the injected code removed.

How the code got there

Optimizely customers load a small JavaScript file from Optimizely’s servers on every page. It carries their A/B tests. It also has an optional field for custom code, which runs on every visit.

The attacker wrote their own code into that field in customers’ projects, Report URI says. The files were still served from Optimizely’s own domain, so the sites had no reason to distrust them.

The added line pulled a second script, track.js, from a domain registered that morning. Report URI says it did four things at once.

It replaced crypto addresses on Bitcoin, Ethereum and other EVM chains, Tron, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin with the attacker’s own, in page text, form fields and the clipboard.

From 13:43 UTC it copied card numbers typed into sites’ own forms. Cards entered in hosted payment frames from Stripe or Adyen were out of reach, Report URI says.

It took cookies and screenshots.

And on older iPhones and iPads it loaded two exploit kits, called Coruna and DarkSword.

Report URI says it does not know how the attacker gained write access to so many unrelated customers’ projects. Optimizely has said it is still investigating.

If one sign-up form could reach 178 projects, how many more were never checked?

The day, in UTC

  • 04:21. Report URI’s first sighting of the injected code, in the BBC’s snippet.
  • 08:10. First build of the address-swapping script.
  • 13:03. The attacker sweeps stolen crypto to exchanges, Report URI says.
  • 13:43. Card skimming is added.
  • About 20:40 to 21:10. Mass clean-up. Ledger’s file was cleaned at 20:41.
  • 21:52. One of 188 files still infected.
  • 23:11. All files clean.
  • 00:37, 17 Nov. The main payload domain is put on hold and stops resolving, Report URI says.
  • 01:21. Optimizely says on X that it contained the incident and contacted customers.
  • 07:42. Ledger Donjon, Ledger’s security team, posts.

Ledger says it has fixed the problem and the code is no longer served from its site. The incident “does not affect the security architecture of Ledger devices,” it said, and private keys “remain protected by your Ledger device.”

It did not say how many visitors loaded the code or whether anyone lost funds.

So who was on the page between 04:21 and 20:41?

Follow the money

Wallets tied to the script had received about $7,000 by Monday evening, Report URI says, across Bitcoin, Litecoin, Tron, Ethereum and BNB Chain. CoinDesk, citing the same figures, put it at $7,040.

Bitcoin was the largest share: 0.08528 BTC in five payments, worth about $5,489 when Report URI counted.

The wallets were drained in the early hours of 17 Nov. Litecoin moved at 04:11 UTC, 116 USDT on Tron at 04:13, and the bitcoin at 05:39, according to Report URI.

Report URI’s update says the Tron address that received that USDT also took cash-outs from the same actor’s March operation and from one on 3 November.

Evidence ledger, as published by Report URI:

  • Bitcoin receiving address: 19g9rZcPeiz8rUvyWpTRyXXhPnjsWrc3kW
  • Bitcoin sweep, 05:39 UTC on 17 Nov: bc1q5fljq9c4g7gsjgg4etpn6k3lyusahcvjfv0u99
  • Ethereum and BNB Chain receiving address: 0xC4026b06D82b0F0B363eda0642D61CfbDc17884e
  • Tron receiving address: THvs6p56XkUiMkJeSc51cAP64u2RsTYqxa

These are on-chain receipts only. Report URI says it cannot see how many cards, cookies or screenshots were taken, or how many iPhones were attacked.

It is not the first week of this. Report URI says the same actor injected a different script through three other web tools, Kissmetrics, StorifyMe and Minute Media, between 13 and 16 November. CryptoWatchDesk reported another third-party script problem in October, in a script swap at Polymarket.

Is a site that sends your copied address to its own page ever your last line of defence?

Protect yourself

  • If you used crypto on any affected site on 16 November, check every transfer you sent that day against the address you meant to pay. Report URI’s advice is to compare each destination with the address you meant to pay.
  • Confirm the full receiving address on your hardware wallet’s screen before approving. A pasted address is only as good as the page it passed through.
  • Watch your card statements if you typed card details into any affected site’s own form on 16 November.
  • Install the latest iPhone and iPad update. Report URI says the exploit kits target older iOS versions, and that releases from 18.7.3 and from 26.3 are patched.
  • Never type your recovery phrase into a website. That is why the recovery phrase is the master key. The same week, Trezor’s shipping-partner breach showed how a supplier’s leak becomes a customer’s problem.

178 trusted sites. One vendor. About $7,000.

If the price of a mistake at the vendor is paid by the visitor, who is checking the vendor?

Corrections and new evidence: [email protected]

This article is for information only and is not investment advice.