0x7e8416667e84…7e841669

ConfirmedSecurity545 vB78 sat/vB3 min decode

Optimizely Hack Served Wallet-Swapping Code to 178 Organizations

An unauthorized party exploited a vulnerability in Optimizely's Experimentation product, injecting wallet-swapping and card-harvesting code into customer sites at 178 organizations.

Optimizely Hack Sent Wallet-Swapping Code to 178 Organizations
WitnessOptimizely Hack Sent Wallet-Swapping Code to 178 OrganizationsStockSnap / pixabay

Outputs

  1. Customer websites at 178 organizations were reached through compromised Optimizely Experimentation scripts, with no breach of each site's own systems

  2. An examination of 1,611 Optimizely scripts on Nov. 16 found 188 infected scripts, roughly 12% of the sample

  3. Injected code swapped displayed and clipboard wallet addresses and searched payment forms for card numbers, expiration dates and security codes

  4. Payment fields hosted in Stripe and Adyen iframes were outside the malicious code's reach

  5. Optimizely's status notice posted at 8:02 p.m. ET Nov. 16 (1:02 a.m. UTC Nov. 17) listed the incident as "Monitoring"

An unauthorized party exploited a vulnerability in Optimizely's Experimentation product and used the vendor's own infrastructure to serve wallet-swapping code to customer websites at 178 organizations, according to Optimizely's status notice posted at 8:02 p.m. ET on Nov. 16 (1:02 a.m. UTC Nov. 17), which listed the incident as "Monitoring."

An examination of 1,611 Optimizely scripts carried out on Nov. 16 found 188 infected scripts, about 12% of the sample. The delivery path explains the reach: because the malicious code was served through Optimizely's infrastructure, the affected websites did not each need to have their own systems breached.

What did the injected code do?

Two functions ran inside the injected code, both operating in a visitor's browser rather than on the host server:

  • Wallet-address substitution. The code could change the cryptocurrency wallet address shown on a page, or the one copied to a visitor's clipboard, replacing it with an address controlled by the attacker.
  • Payment-card harvesting. The script also searched some websites' payment forms for card numbers, expiration dates and security codes.

One boundary held. Payment fields hosted in Stripe and Adyen iframes sat outside the code's reach, Optimizely reported, since those elements load in a third-party frame rather than in the page an Optimizely script can read.

How did a single vendor compromise reach 178 sites?

Optimizely sells testing software that customers embed in their own websites to run experiments on page content and layout. Its scripts load from the vendor's servers into every site that installs them, so a compromise of that delivery path fans out to all customers at once — no breach required at any of the 178 organizations.

Two figures define the scale, and they are not interchangeable. The 188 infected scripts count compromised code units reviewed on Nov. 16; the 178 organizations count the customer sites those scripts reached. Multiple scripts can sit on a single site, and the sample of 1,611 scripts reviewed was larger than the number found infected.

What did Optimizely do?

The company disclosed three remediation steps:

  • Removed the injected code from affected projects and fixed the underlying vulnerability.
  • Secured affected accounts.
  • Added new protections.

"We've fixed the vulnerability and removed the injected code from affected projects," Optimizely said.

What does the "Monitoring" status leave open?

The Nov. 16 notice classified the incident as "Monitoring" rather than resolved, which points to continued observation of the compromised delivery path. Optimizely's disclosure does not state how many visitors loaded the infected scripts, whether any wallet transfers followed, or whether card data reached the attacker, and it publishes no loss figure.

That silence matters for two audiences with different exposures. For the 178 affected sites, the remediation burden sits with the vendor, since none had its own systems breached; for crypto users who paid on those pages, the substitution happened in the browser at the moment of payment, and the address a customer sent to may have belonged to someone else.

The next checkpoint is a root-cause report and a move off the "Monitoring" label. Until Optimizely publishes that, and until any exchange or card processor files its own incident record, the accounting of what moved stays unclosed.

via tokenpost.com (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles