Check a site
Check a website Service status Outages Blog
Theme
All tools
Check a websiteBrowse all tools
An Optimizely snippet loading injected track.js that swaps wallet addresses, skims cards and routes iPhones to exploit kits; 188 of 1,611 snippets, 178 organisations, all cleaned 16 Nov

Server & Security News

Security alert: Optimizely supply-chain attack exposed visitors across 178 organizations

Posted Jimel S.6 min read

Attackers abused Optimizely Web Experimentation to inject malicious JavaScript into 188 website scripts tied to 178 organizations on 16 November. The code tried card skimming, crypto-address swaps and iOS exploits. Here’s what happened and what to do.

Illustration: UtiBox

What happened

On 16 November, security researchers found malicious JavaScript being delivered through Optimizely Web Experimentation, a third-party service that businesses use to test, optimize and personalize their websites.

Report URI examined 1,611 Optimizely JavaScript snippets and found 188 compromised snippets associated with 178 organizations. The code came from a service those websites already trusted. That is what makes a supply-chain attack dangerous: visitors can be exposed even when a company’s own servers were never breached.

Optimizely later confirmed that an unauthorized party exploited a vulnerability in its Experimentation account signup flow and used it to add malicious code to customer projects. The company told BleepingComputer it blocked access to the vulnerable path, deployed a fix, removed the injected code, secured affected accounts and put additional protections in place.

Which organizations were named

The researchers’ list covers finance, technology, retail, media, travel and other sectors. Examples named in the research and in independent reporting:

SectorExamples named
TechnologyZoom, Salesforce, GitLab, Bitly
News and mediaBBC, CNN, Fox News
Banking and financial servicesHSBC, Equifax, Paychex
RetailIKEA, ASOS, American Eagle
TravelAir France-KLM, Alaska Airlines / Hawaiian Airlines
Entertainment and other servicesPeacock, Ledger, Change.org

Being named doesn’t mean a company suffered a customer-data breach. Some companies investigated or switched off the affected script as a precaution, and how much harm reached visitors hasn’t been established. The full organization and domain list is in Report URI’s original investigation (opens in a new tab).

What the malicious code could do

Researchers analysed a multi-purpose payload:

  1. Cryptocurrency address swapping. It could replace the wallet address a visitor meant to pay with one the attacker controls.
  2. Payment-card skimming. Later versions tried to capture card numbers, expiry dates and security codes typed into the affected websites’ own forms.
  3. Browser-data collection. It could send the page address, readable cookies and a screenshot of the page. Cookies marked HttpOnly can’t be read by ordinary page JavaScript.
  4. iPhone and iPad exploit delivery. It could send devices to infrastructure linked to the Coruna and DarkSword iOS exploit kits. That confirms an attempt to deliver exploits, not that every device was infected.

Researchers saw transactions involving cryptocurrency wallets tied to the campaign. How much was stolen because of this attack is still unclear, because some of those wallets were active before it. The numbers of exposed cards, stolen sessions and infected devices haven’t been published.

Timeline

All times are UTC (Eastern is five hours behind).

Date and time (UTC)What happened
16 Nov, 04:21Earliest Optimizely injection in Report URI’s timeline (a BBC-related script)
16 Nov, 13:43Card-skimming code added to the payload
16 Nov, about 20:40 to 21:10Widespread clean-up of infected snippets
16 Nov, 23:11Report URI confirms all 188 compromised snippets are clean
17 Nov, 01:02Optimizely posts its security incident update: fixed, injected code removed, monitoring
17 Nov, 09:17Report URI update: still clean; the attacker’s domains are being taken down

UtiBox classification: Mitigated, monitoring. This is a security incident. It isn’t a sign that any named company’s website is down.

What visitors should do

If you visited one of the named websites on 16 November, take the steps that match what you did there:

  • Update your iPhone or iPad. Install the latest iOS or iPadOS update your device supports, especially if you browsed an affected site on an older version.
  • Check your card statements. If you entered card details on a possibly affected page, watch your statements and report anything you don’t recognise to your bank or card provider straight away.
  • Check cryptocurrency transfers. Compare the recipient address and history of any transfer you made while an affected page was open. Blockchain transfers usually can’t be reversed.
  • Watch for unusual account activity. Look out for unexpected sign-in alerts or security changes. If you think a password or session was exposed, change the password and sign out other sessions using the service’s own security settings.
  • Use official channels. Read the organization’s own advisory before acting, and ignore unsolicited messages offering an automatic “security fix”.

Simply visiting a named site doesn’t mean your data was stolen or your device infected. The risk depends on the page, when you visited, your device and what you did there.

What website owners and security teams should do

If you load Optimizely Web Experimentation, or any third-party JavaScript:

  1. Find affected projects. List the Optimizely snippets on your public sites and check the Project JavaScript and experiment code for changes you didn’t make.
  2. Review logs and change history. Work out whether malicious code was served during the exposure window. A script that’s clean now doesn’t rule out what it served before.
  3. Review account security. Audit account access, active sessions, API tokens and integrations. Rotate exposed credentials and revoke suspicious sessions.
  4. Assess customer impact. Start with pages that take card details, expose sensitive data to scripts, or show cryptocurrency wallet addresses.
  5. Tighten your Content Security Policy. Enforce restrictive script-src and connect-src rules where you can, avoid unsafe-eval where it isn’t needed, and monitor CSP violations. Test changes so the site doesn’t break.
  6. Monitor third-party scripts. Consider script-change monitoring, browser-side telemetry and alerts for unexpected outbound connections. Static Subresource Integrity hashes rarely suit scripts that change often by design, so choose a control that fits the dependency.
  7. Check your notification duties. If you find credible exposure of customer data, follow the notification rules that apply to you and your incident-response plan.

Check your site’s security headers

Indicators for defenders

These are defanged so they can’t be opened by accident. Use them for threat hunting, searching historical logs and blocking; don’t open them in a browser.

IndicatorReported role
1688360[.]ccMain payload and data-collection host
5vobauua3ojpklx[.]icuiOS exploit-delivery router
eil786npto9u5bq[.]icuSecond iOS router
webshell[.]lolInjector used in an earlier, related wave

Report URI keeps the complete, current indicator list and hashes in its original research (opens in a new tab). Some of this infrastructure was already being taken down by 17 November. Matching your historical logs is still useful even when a domain no longer answers.

What isn’t confirmed yet

So far, public evidence doesn’t establish:

  • how many visitors had payment details or browser data stolen;
  • how many iPhones or iPads were compromised through the exploit kits;
  • exactly how much cryptocurrency this campaign stole;
  • a direct internal breach at any named organization;
  • the full set of affected websites beyond those researchers could examine.

We’ll keep confirmed findings separate from early reports and vendor statements if we update this post.

Sources

  1. Report URI (Scott Helme), original investigation, 16 November, updated 17 November: World’s Largest Brands Infected With Malware Via Optimizely (opens in a new tab)
  2. Optimizely, official status page: Web Experimentation Security Incident (opens in a new tab)
  3. BleepingComputer, independent reporting and Optimizely’s statement: Optimizely hack infected CNN, Fox News, BBC, Salesforce sites with malware (opens in a new tab)
  4. Reuters, 17 November: Popular websites compromised in bid to steal crypto, target iPhone users (opens in a new tab)
  5. Newsweek: Cyber Attack Hits 178 Major Websites: Full List of Affected Organizations (opens in a new tab)

UtiBox security announcements are independently checked and meant to support public awareness and defensive decisions. Incident status and technical findings can change as investigators and vendors publish updates. For authoritative remediation details, follow the affected provider and the primary research linked above.

Related

More from Server & Security News

Most read

Latest

Most read

  1. 01November Patch Tuesday lands on the 10th: what October’s record release tells us19
  2. 02Introducing UtiBox: the Web’s Utility Box2
  3. 03Ivanti Connect Secure zero-days gave attackers root on VPN gateways1
  4. 04“Black October”: attackers raid secrets at cloud and AI developer platforms1

Embed this post

Paste this code into your page. It shows the post as a card that links back here. In WordPress you can also paste the post’s address on a line of its own.

Cookies on UtiBox

UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.