The Library

Optimizely Vulnerability: Malware Injected Into 178 Organizations' Websites, a Card Skimmer, iPhone Exploit Kits and What to Check This Week

Attackers exploited a flaw in Optimizely Experimentation to plant malicious code in 188 snippets belonging to 178 organizations, including the BBC, CNN, Zoom and HSBC. What is confirmed, what is not known, and what to check this week.

Elite Performance Exclusive LLC 6 min read

Where Worldwide

Optimizely Vulnerability: Malware Injected Into 178 Organizations' Websites, a Card Skimmer, iPhone Exploit Kits and What to Check This Week
On this page 7 sections

Attackers exploited a vulnerability in Optimizely's Experimentation product. They used it to plant malicious JavaScript in 188 Optimizely snippets belonging to 178 organizations, including the BBC, CNN, Zoom, HSBC and Equifax. If your website loads code from an outside company, plan for this: your own code can be untouched while a trusted vendor's script steals from your visitors.

Optimizely says the flaw is fixed and the injected code has been removed. What has not been published yet matters just as much. Below, we separate what is confirmed from what is still unknown, then list what to check this week.

What happened with the Optimizely vulnerability

According to SecurityWeek, attackers exploited a vulnerability in Optimizely Experimentation. The malicious code then showed up inside the Optimizely snippets that organizations load on their websites.

The researchers at Report URI published the most detailed account. They fetched 1,611 distinct Optimizely snippets, found mostly through their own crawl data. Of those, they report that 188 snippets belonging to 178 organizations were infected. The organizations they name include Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock.

Their timeline puts the first injection at 04:21 on November 16, when the BBC's snippet was seen loading code from the domain webshell.lol.

In a statement reported by SecurityWeek, Optimizely said: "We’ve fixed the vulnerability and removed the injected code from affected projects."

What the Optimizely malware did

Report URI describes three kinds of harm to people visiting the affected websites.

A payment card skimmer

The script watched form submissions and every fetch or XHR POST request for a card number, expiry date and CVV. It sent what it caught to a domain the attacker controlled. It ran card numbers through a Luhn check, a basic validity test, so it was looking for real card numbers rather than any string of digits.

Because it watched background POST requests as well as ordinary forms, it could catch card details from checkouts built as modern web apps, not only from classic page forms.

Money sent to crypto wallets

Report URI says the attacker's wallets received about $7,040, all within roughly nine hours on November 16. The sources do not explain in detail how that money was taken from visitors.

iPhone and iPad exploit kits

On iPhones and iPads, the injected code delivered the Coruna and DarkSword iOS exploit kits. The sources do not say which iOS versions these kits work against or how many devices were compromised.

Optimizely hack: confirmed vs not known

Question What the sources show
Was an Optimizely flaw exploited? Yes. SecurityWeek reports it, and Optimizely says it has fixed the vulnerability
How many organizations were hit? Report URI found 188 infected snippets belonging to 178 organizations, out of 1,611 snippets it fetched
When did it start? Report URI first saw an injection at 04:21 on November 16
Has the injected code been removed? Optimizely says it removed the code from affected projects
What exactly was the flaw? Not published in the sources
Is there a CVE? None given in the sources
How many card numbers were stolen? Not known
How many iPhones were compromised? Not known

One caution on the numbers: Report URI's count covers only the snippets it was able to fetch. The true number of affected organizations could be different, and the sources do not give a complete list.

Why this matters for a business website

Most business websites load scripts from other companies: testing tools, analytics, chat widgets, ad tags, payment helpers. Each one runs in your visitor's browser with the same power as your own code. It can read what customers type, change what they see, and send data anywhere.

The malicious code here did not come from these companies' own developers. It arrived through a trusted vendor's snippet. Checking your own code and server would not have caught it, because the change sat in the vendor's script. The customers who typed their card numbers, though, were on the brand's website, and that is where they will direct their questions.

If you take payments, run a login page, or hold customer accounts, every outside script on those pages is part of your security.

What to do this week: Optimizely checklist

Optimizely fixed the flaw on its side. The sources name no version or setting for customers to change. Your work this week is checking and limiting.

Action How to check
Find out whether your site loads Optimizely Open your site in a browser, open developer tools, and look for requests to Optimizely in the Network tab. Check checkout and login pages too
Review your Optimizely projects Look through the code in your projects and snippet for anything your team did not add
Ask Optimizely directly Ask in writing whether your project was one of the affected ones, and when the injected code was removed
Search your logs for the known domain Search any web, proxy or security logs for webshell.lol, the domain Report URI saw in the first injection
Assess payment exposure If you take card payments on pages that loaded Optimizely around November 16, talk to your payment processor and advisers about whether customer card data may have been exposed
Trim third-party scripts List every outside script on payment, login and account pages and remove anything you do not need there
Check work iPhones and iPads Keep company Apple devices updated and managed

Optimizely vulnerability questions people are asking

Was Optimizely hacked?

Attackers exploited a vulnerability in Optimizely's Experimentation product and injected code into customers' snippets, according to SecurityWeek. Optimizely says it has fixed the vulnerability and removed the injected code.

Which websites were affected by the Optimizely malware?

Report URI counts 178 organizations and names Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock among them. A full list is not in the sources.

Is it safe to visit those websites now?

Optimizely says the injected code has been removed from affected projects. The sources do not include an independent check of each site.

Was my credit card stolen?

That is not known. The script was built to capture card numbers, expiry dates and CVVs, but no count of stolen cards has been published. If you paid on one of the named sites around November 16, watch your statements and contact your bank if anything looks wrong.

Is there a CVE for the Optimizely vulnerability?

No CVE is given in the sources, and the flaw itself has not been described publicly.

Do I need to install an update?

No customer update is named in the sources. Optimizely fixed the flaw on its side. Your part is to review your projects and the scripts your site loads.

Did the Optimizely attack target iPhones?

Yes. On iPhones and iPads, the injected code delivered the Coruna and DarkSword iOS exploit kits. How many devices were affected is not known.

The bigger lesson

Scott Helme of Report URI put it this way: "The important lesson here is that trusted JavaScript doesn't always remain trustworthy." A vendor you vetted last year can serve different code tomorrow. Know every script your site loads, keep outside scripts off payment and login pages unless they need to be there, and have someone actually watching for changes.

If you want your website's third-party scripts reviewed and locked down, see security hardening or request a quote.

Get security alerts like this by email, with our free checklist, at /security-alerts.

Sources: Report URI; SecurityWeek.

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.