The Library

Optimizely Supply Chain Attack: OPTIMJACK Put Card Skimmers and Crypto Clippers in 188 Optimizely Scripts, What Is Confirmed and What to Check This Week

Attackers exploited a vulnerability in Optimizely Experimentation to add card-skimming and crypto-clipping JavaScript to customer projects. Here is what is confirmed, what is not known, and what to check this week.

Elite Performance Exclusive LLC 6 min read

Where Worldwide

Optimizely Supply Chain Attack: OPTIMJACK Put Card Skimmers and Crypto Clippers in 188 Optimizely Scripts, What Is Confirmed and What to Check This Week
On this page 7 sections

Attackers exploited a vulnerability in Optimizely's Experimentation product and used it to add malicious JavaScript to customer projects, which is code that runs inside those customers' websites. The injected code looked for credit card details typed into pages, swapped cryptocurrency wallet addresses for the attackers' own and loaded more malicious code aimed at iPhones and iPads. Any business whose website loads a script from an outside service should pay attention.

What happened in the Optimizely supply chain attack

Optimizely confirmed the main point in a statement reported by BleepingComputer: "They used it to add malicious JavaScript to some customer projects." The "it" in that sentence is the vulnerability the attackers exploited. ReversingLabs, which published its own analysis of the campaign, says the attackers exploited a vulnerability in Experimentation. Independent researcher Amirul Cyber named the campaign OPTIMJACK.

According to ReversingLabs, the Optimizely-specific injection was first observed on November 16, at 04:21 UTC, in a BBC snippet. BleepingComputer reports that 188 infected Optimizely JavaScript files were identified, belonging to 178 organizations. The report names major brands among them, including Zoom, CNN, Fox News, BBC, Salesforce, and GitLab.

This is how a supply chain attack on a website works. None of those companies had to be hacked directly. The attackers changed code at the supplier, and the supplier's normal delivery put that code onto its customers' pages.

What the malicious Optimizely JavaScript did

BleepingComputer's report describes three jobs for the injected code:

  • Crypto clipper: it watched webpages for cryptocurrency wallet addresses and replaced them with addresses the attackers controlled. A visitor who copied an address to send a payment could end up paying the attackers instead.
  • Card skimmer: it searched for credit card numbers, expiration dates and security codes entered into webpages.
  • iPhone and iPad loader: it loaded more malicious JavaScript aimed at iPhones and iPads.

The sources we checked do not say what that extra iPhone and iPad code did once it loaded.

What is confirmed and what is not known

Question What the sources say
Was Optimizely abused? Yes. Optimizely says attackers used a vulnerability to add malicious JavaScript to some customer projects.
Which product? ReversingLabs says the vulnerability was in Experimentation.
When was it first seen? The Optimizely-specific injection was first observed on November 16, at 04:21 UTC, in a BBC snippet.
How many sites? BleepingComputer reports 188 infected Optimizely JavaScript files belonging to 178 organizations.
Is it fixed? A statement quoted by BleepingComputer says: "We have blocked access to the vulnerable path and deployed a fix."
Is there a CVE? None appears in the sources we checked.
Were cards or crypto actually stolen? Not known. The sources describe what the code was built to do, not what it took.
How long were the scripts infected? Not known from the sources.
Is there a full list of affected sites? Not in the sources we checked.

The sources also do not explain the vulnerability in technical detail, and they do not list any steps Optimizely is asking its customers to take. Until those details come out, treat any claim about them with caution.

Why this matters for a company website

A checkout page is only as safe as every script it loads. Your own code can be clean, your server patched and your passwords strong, and a script from a trusted supplier can still read what your customers type. Your customers see your brand on the page, not the supplier's, so a skimmer on your checkout is your problem as soon as they notice it.

Salesforce, one of the brands named, made sure the scripts were not running: "As a precaution, Salesforce is confirming Optimizely scripts are disabled across preview and production instances." It is worth noticing that the response covered preview as well as production. Test and staging sites load the same scripts and are easy to forget.

If nobody at your company is responsible for knowing which outside code runs on your website, that is the same gap we wrote about in Who Is Patching the Software That Runs Your Business?. With a hosted script, being patched also means being checked: you have no version number to update, so the only defence is knowing what is on your pages.

What to do this week

There is no version for you to install. The fix described in the reporting was made on Optimizely's side. Your job is to confirm that your own pages are clean.

Step What to do How to check
1 Find out if your site loads Optimizely Open the page source of your home page and checkout page and search for "optimizely". Check your tag manager too.
2 Review your Optimizely projects Look for JavaScript your team did not write or approve.
3 Consider turning the scripts off until you have reviewed them Salesforce disabled Optimizely scripts across preview and production as a precaution.
4 Check payment pages first Any page that collects card numbers, expiration dates or security codes.
5 Check any crypto wallet addresses you publish From a clean device, compare the address shown on the page with your own records.
6 Watch for customer reports Write down every report of card fraud or a misdirected payment, with dates.
7 Ask the supplier directly Ask your Optimizely contact, in writing, whether your projects were among those affected.
8 List every third-party script on checkout Remove anything that does not need to run on that page.

Optimizely attack questions people are asking

Was my website affected by the Optimizely attack?

Only Optimizely can tell you for certain. The reported figure is 188 infected JavaScript files belonging to 178 organizations, and the sources we checked do not include a full list. If you use Optimizely, ask them directly and review your projects.

What is OPTIMJACK?

OPTIMJACK is the name independent researcher Amirul Cyber gave to this campaign, in which malicious JavaScript was added to Optimizely customer projects.

Has Optimizely fixed the vulnerability?

A statement quoted by BleepingComputer says: "We have blocked access to the vulnerable path and deployed a fix." The sources do not describe the flaw in technical detail.

Is there a CVE for the Optimizely vulnerability?

None appears in the sources we checked.

Were credit card numbers stolen in the Optimizely hack?

The code was built to search for card numbers, expiration dates and security codes entered into webpages. How much was taken, if anything, is not known from the sources.

Does the Optimizely malware affect iPhones?

The injected code loaded more malicious JavaScript aimed at iPhones and iPads. What that code did next is not described in the sources.

Should I turn off Optimizely?

That is a business decision. Salesforce chose to disable Optimizely scripts as a precaution. Turning them off until you have reviewed your projects is the cautious option.

The bigger lesson

Every outside script on your website is a supplier with write access to your pages. You can't patch code you don't host, so the defence is knowing exactly what runs on each page, keeping checkout pages as bare as possible and having someone whose job is to check. For more on keeping a site visible and locked down, see Your Website Is Live. Can Anyone Find It, and Is It Locked?.

Want someone to review what runs on your website? See security hardening or get a quote.

Get security alerts like this by email, with the free checklist, at security alerts.

Sources: ReversingLabs: OPTIMJACK, when trusted JavaScript becomes a supply chain attack; BleepingComputer: Optimizely supply chain attack infects major brands' sites with malware.

Share X LinkedIn Facebook

Was this article helpful?

We only keep the note with this article. No name, no email.

Protected by reCAPTCHA - Privacy and Terms.

Have a question about this article?

Ask it here and we will answer you directly by email. Questions are private, never posted.

Protected by reCAPTCHA - Privacy and Terms.

Security alerts by email

Hear about the next one first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.

Want a result like this?

Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.

Get a Tech Quote

Security alerts by email

The next security hole is already out there. Hear about it from us first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.