← All news
BREAKING

A trusted website tool served a card skimmer

For about 16 hours on 16 November, a popular website testing tool loaded card-skimming code on 178 organisations' sites, including the BBC and HSBC. Your website runs outside code too.

Sophia, HackRisk's AI security analyst, in a cream knit jumper in the back room of a small UK pottery studio, pointing at a glowing red-orange plug-in block on an online shop page while the owner looks on, beside the headline 'A trusted website tool served a card skimmer'

On Monday 16 November, people visiting some of the world's best-known websites, including the BBC, HSBC, IKEA and Zoom, were quietly served code that could swap cryptocurrency addresses and skim card details. None of those companies wrote it. It arrived through Optimizely, a tool many websites use to test different versions of their pages. If your own website loads tools from other companies, and almost every website does, this one is worth ten minutes of your time.

What happened

According to a detailed write-up by StepSecurity, an attacker injected malicious JavaScript into the Optimizely Web projects of 178 organisations on 16 November. Security researcher Scott Helme of Report URI checked 1,611 Optimizely script files and found the code in 188 of them. Named organisations include the BBC, CNN, Fox News, Zoom, Salesforce, GitLab, HSBC, IKEA, Equifax and Air France-KLM. Fish 4 News also lists Virgin Media O2 and ASOS, and points out that a finding on one HSBC site doesn't mean every HSBC service was affected.

The first injection appeared at about 04:21 UTC. Most of it was cleaned up between roughly 20:40 and 21:10 that evening, so for most sites the exposure lasted around 16 hours. The domain hosting the malicious code was taken offline in the early hours of 17 November.

Optimizely says an unauthorised party exploited a vulnerability in its account sign-up process. It says it has fixed the flaw, removed the injected code, ended active sessions, revoked tokens and notified affected customers. Salesforce disabled Optimizely scripts as a precaution, and Equifax has stopped using the service and says it found no evidence its own systems were compromised.

What the code did

Because the code was served from Optimizely's own servers, visitors' browsers trusted it like the rest of the page. StepSecurity found it did three main things.

It swapped crypto wallet addresses. When someone copied a wallet address near words like "send" or "deposit", the code quietly replaced it with one belonging to the attacker.

It skimmed card details. It watched forms and web requests for card numbers, expiry dates and security codes. It could not read payment fields hosted separately by a payment provider.

It went after older iPhones. On iPhones and iPads it tried to load extra code linked to known iOS exploit kits. StepSecurity hasn't verified that link, and Fish 4 News says no individual device has been confirmed as compromised.

Wallets linked to the attack had received roughly $7,000 by the evening of 16 November. Fish 4 News notes that some of those wallets existed before the incident, so the true amount stolen isn't known.

Why this keeps happening

A modern website is rarely just your own code. Analytics, live chat, cookie banners, booking widgets, review badges, marketing pixels and testing tools all load scripts from other companies' servers every time someone visits. Each one runs with the same power as your own code. If one of those suppliers is compromised, your site can serve malware without anyone touching your server, your hosting or your passwords. That's a supply chain attack, and it's hard to spot because your website looks exactly the same to you.

What this means for UK small businesses

Most small businesses don't use Optimizely. But the lesson applies to every tool you've added to your website over the years, including the ones a previous web designer added that nobody remembers. If a supplier's script is hijacked, it's your customers who are exposed, and it's your website they'll remember.

The risk is higher if customers type card details straight into your own pages. StepSecurity found the skimmer couldn't read payment fields hosted separately by a payment provider, which is a good reason to keep card entry on your provider's hosted payment page or fields.

What to do this week

List every outside script on your website. Ask your web designer, or check your site builder's settings, for analytics, chat, testing and marketing tags. Remove anything you no longer use.

Check who can change them. Most tag and testing tools have their own logins. StepSecurity advises reviewing users and API tokens. Remove former staff and old agencies, and turn on two-step verification wherever it's offered.

Keep third-party tags off your checkout. StepSecurity recommends removing third-party tags from checkout pages, or using payment fields hosted by your payment provider.

Ask your developer about a Content Security Policy. A CSP tells browsers which sites your pages may load code from and send data to. StepSecurity says a list of allowed hosts helps limit this kind of attack, and Fish 4 News adds monitoring for changes to your JavaScript.

If you use Optimizely, check it properly. StepSecurity advises reading the Project JavaScript field of every Optimizely Web project, rather than just searching for the known bad domain, and checking logs from 04:00 UTC on 16 November.

Sophia Says

What strikes me about this one is that the victims didn't do anything wrong on the day. Their websites weren't hacked in the usual sense; a tool they trusted was. That's the uncomfortable truth about modern websites. The code your customers run isn't all yours, and most small businesses have no idea how many outside scripts are loading on their pages, or who can change them.
You can't protect what you can't see, so that's where HackRisk starts. We give you an outside-in view of your website and the services around it, flag weaknesses before attackers find them, and help you see which suppliers your business depends on. When a supplier makes the headlines, you'll already know whether it's one of yours, and what to check first.
— Sophia, HackRisk AI Security Analyst

Where HackRisk fits

Third-party tools and suppliers: Supply Chain Risk helps you see the suppliers and services your business relies on, and where the risk sits among them.

What your website exposes: Recon Scan shows your website and internet-facing services the way an attacker sees them.

Weaknesses on your site: Vulnerability Scan finds out-of-date software and known flaws before someone else does.

Leaked logins to your website tools: Dark Web Scan tells you when staff or agency credentials turn up in leaks. Optimizely itself was hit by a voice-phishing attack in February, a reminder that tool accounts are targets in their own right.

People and passwords: Security Awareness Training and Phishing Simulations help your team spot the calls and emails that try to steal those logins.

See your website the way attackers do

Find out what's visible, what's vulnerable and which suppliers you depend on, in plain English. Get your free HackRisk report.

Sources

StepSecurity: OPTIMJACK, Optimizely-hosted scripts loaded a crypto clipper and card skimmer on 178 organisations (17 November 2026)

Fish 4 News: Optimizely cyberattack exposes visitors to malware on 178 organisations' websites (17 November 2026)

TechRadar Pro: Optimizely hit by data breach (24 February 2026)

Related stories

All news →
Sophia, HackRisk's AI security analyst, in a black zip-up jacket, crouching in a small UK pottery studio and bolting shut a trapdoor on a model of a website while red-orange robot hands reach in during a 7.1.4 update, as the bearded owner watches from his laptop, beside the headline 'Hackers strike while WordPress updates'
BREAKING6 min read

Hackers strike while WordPress updates

A WordPress flaw fixed in 7.1.4 lets attackers take over a site during the seconds it updates, and scanning is widespread. Here's what UK small businesses should check and how to update safely.

By CyberLab security team
Sophia, HackRisk's AI security analyst, in a cream knit jumper raises a hand to pause a developer on a video interview call at his home desk, beside the headline 'The fake job interview behind a $6.3bn heist'.
BREAKING6 min read

Binance hack: what we know now

Binance says a fake job interview, a tampered installer and an abused internal AI tool led to a $6.3 billion theft. Here is what we know, what is disputed, and what UK businesses should check.

By CyberLab security team
Sophia, HackRisk's AI security analyst, in a navy hoodie holding a tablet and giving a thumbs-up to a studio checklist with two ticks and one pending clock, beside a relieved architect and a network storage box, with the headline 'PHP2Shell: what we know now'.
BREAKING7 min read

PHP2Shell: CISA confirms attacks, what we know now

CISA now confirms PHP2Shell attacks, with some successful. A third flaw has no emergency fix and a big claim was retracted. What's confirmed, and what UK small businesses should check this week.

By CyberLab security team