Incident sheet · /security

Filed
Read
3 min · 610 words
Severity
Routine

Optimizely breach hit 178 organisations with card-skimming code

Attackers exploited Optimizely Web Experimentation to plant card-skimming and cryptocurrency-stealing code on sites used by at least 178 organisations, prompting device updates and statement checks.

Hijacked website testing tool plants card skimmer on Australian brands’ sites
FeedHijacked website testing tool plants card skimmer on Australian brands’ sites — waltc / pixabay

Event log

  1. At least 178 organisations had malicious scripts injected through Optimizely Web Experimentation.
  2. Helme found the code in 188 of 1,611 scripts, nearly one in eight he checked.
  3. The first injection appeared at 3:21pm AEDT on Monday; almost every infected script was clean by about 8:10am Tuesday.
  4. The payload targeted card details, cookies, screenshots, cryptocurrency wallets and unpatched iPhones and iPads.
  5. Helme traced about US$7,040 (A$10,464) to the attacker’s wallets.

At least 178 organisations had card-skimming and cryptocurrency-stealing JavaScript planted on their websites through Optimizely Web Experimentation, a service that loads scripts so marketing teams can test different versions of their pages.

The first injection appeared at 3:21pm AEDT on Monday, and almost every infected script had been cleaned by about 8:10am Tuesday. Named victims included Zoom, the BBC, CNN, Vodafone Australia, HSBC Australia and Rest Super.

Security researcher Scott Helme of Report URI found the code in 188 of the 1,611 Optimizely scripts he checked during the attack—nearly one in eight. He also found affected sites from Salesforce, GitLab, IKEA, Equifax, Air France-KLM and cryptocurrency wallet maker Ledger, plus HSBC sites in 11 markets.

Attack path and response

Attackers exploited a vulnerability in the Experimentation account signup flow. Optimizely confirmed:

“Earlier today, Optimizely identified a security incident in which an unauthorised party exploited a vulnerability in the Experimentation account signup flow.”

The company said it had blocked the vulnerable path, deployed a fix, removed the injected code, reset access for affected user accounts and notified all affected customers.

It also said it had blocked code delivery through Cloudflare, without elaborating on the measure. Optimizely did not disclose when the flaw was first exploited or how many customer projects were altered.

Scale and payload

Several Australian organisations also appeared on Helme’s list: TPG Telecom, Betashares, Compare Club, Energy Scout, O’Brien Glass and Levi’s Australia. Levi’s New Zealand was the only cross-Tasman entry.

During the compromise, the payload:

  • Replaced cryptocurrency wallet addresses.
  • Captured payment-card details entered into a site’s own forms.
  • Collected cookies and screenshots.
  • Directed unpatched iPhones and iPads to exploit kits named Coruna and DarkSword.

Helme traced about US$7,040 (A$10,464) to the attacker’s wallets, but he could not see how many cards or cookies had been taken.

What organisations did

TPG Telecom, which owns Vodafone, confirmed Optimizely ran on parts of the Vodafone website. It paused all Optimizely functionality as a precaution.

TPG said its security teams had found no evidence that Vodafone systems or customer data had been compromised. It added that the affected pages did not contain payment, transaction or credential functions, so it did not believe customers’ payment or credential information was at risk.

HSBC had disabled Optimizely across all its websites globally as a precaution, and the unauthorised scripts were no longer active on them. HSBC declined to comment on the record. Rest Super received a request for comment but did not respond before publication.

What does this change for customers?

Helme advised iPhone and iPad users to update to iOS 18.7.3 or 26.3 or later. TPG separately advised customers who visited the affected Vodafone pages on an iPhone or iPad running iOS or iPadOS 18.6 or earlier to install the latest software.

Helme also advised anyone who paid by card on an affected site on 16 November to watch their statements. The immediate customer action is therefore specific: update the devices named in the warning and check card statements after payments on that date.

The incident also echoes a 2018 case Helme uncovered, when a compromised accessibility plugin called Browsealoud served a cryptocurrency miner to more than 4,000 sites, including the Victorian Parliament and the Queensland legislation site. In both incidents, the code arrived through a trusted supplier’s script.

“Trusted JavaScript doesn’t always remain trustworthy,” Helme wrote.

Optimizely has closed the exploited signup route, but it has not disclosed when the flaw was first exploited or how many customer projects were altered, leaving the scale before cleanup unresolved.

via itnews.com.au (Source)

Filed under

  • optimizely
  • supply-chain-attack
  • card-skimming
  • javascript-injection
  • cryptocurrency-theft
Share this article:

More from Olivia Hart

Olivia Hart

Show full bio

News editor covering money, funding and market shifts around enterprise information technology and the leaders who run at CIO Monitor.

207 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›