Back
Cyberattack Hits 178 Websites Through Optimizely: What Was Stolen, Who Should Worry, and the Inbox Rule That Limits the Damage

Cyberattack Hits 178 Websites Through Optimizely: What Was Stolen, Who Should Worry, and the Inbox Rule That Limits the Damage

Emily Parker
Written by Emily Parker Editor — email privacy & digital hygiene
Fact-Checked Nov 17, 2026 22 Views
Share article:
TempoMail USA App Get OTPs faster on the app!
Get the App
Advertisement

Cyberattack Hits 178 Websites Through Optimizely: What Was Stolen, Who Should Worry, and the Inbox Rule That Limits the Damage

Yesterday, for about seventeen hours, some of the most trusted websites on the internet were quietly working for criminals. Not hacked websites in the usual sense — the sites themselves were fine. The poison was in a third-party script they all loaded, from a company called Optimizely, and it arrived with a valid certificate from Optimizely's own domain. Your browser had no reason to distrust it. That is the whole story, and it is why this one matters more than the average breach headline.

The numbers, as counted by Scott Helme's security monitoring service Report URI: 188 infected scripts across 178 organisations, found by checking 1,611 Optimizely scripts. The list reads like a roll call of the mainstream web — Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, Peacock, Fox News. Banking and finance was the largest group with 32 organisations, then technology with 23, retail with 20, streaming with 12, news with 10. Helme says the real total is probably higher, because the 1,611 scripts his team checked are not every Optimizely customer.

The code did three things to visitors: it swapped cryptocurrency wallet addresses for the attacker's own, it skimmed payment card details typed into a site's own checkout forms, and on iPhones and iPads it tried to run exploit kits. The confirmed crypto haul is small — about $7,040 by Report URI's count, about $6,600 by StepSecurity's. Do not let that number fool you: it counts only the crypto the researchers could see move into the attacker's wallets. The card numbers and cookies leave no trace on a blockchain, so nobody knows that half of the damage yet.

Here is the short version, because it decides whether you need to do anything tonight: the attack is largely over. The injected code was mostly cleaned up on the evening of November 16, and Optimizely confirmed the incident on November 17. If you only read pages on a desktop browser yesterday and never typed a card number or pasted a crypto address into one of the affected sites, the clipper and the skimmer had nothing to take from you. If you did either of those things, or you browsed on an iPhone, work the checklist below. And if you want the one habit that makes the next attack like this one cheaper for you, it is near the end: stop giving every website the same email address.

What Actually Happened on November 16

The first infected script Report URI found was in the BBC's Optimizely snippet at 04:21 UTC on November 16 — 11:21 p.m. Eastern on November 15 — two hours after the last clean capture of that file. The attacker had registered the domain the malware would phone home to, 1688360.cc, at 05:23 UTC. The first version of the payload, a file called track.js, was built at 08:10 UTC. A card skimmer was added at 13:43 UTC. Over the day the attacker rebuilt the payload 26 times, tuning it as researchers started to notice.

The clean-up came fast once the campaign was public. Report URI recorded a mass clean-up between about 20:40 and 21:10 UTC, with infected scripts falling from 169 at 20:56 UTC to one at 21:52 UTC — 4:52 p.m. Eastern. The last one belonged to TalkTalk, a UK broadband provider. Optimizely confirmed the incident in a post on X at 01:21 UTC on November 17, about 8:21 p.m. Eastern on November 16, saying the vulnerable path was blocked and the injected code removed. So the exposure window for any given site runs from its first infection, as early as 04:21 UTC, to the clean-up roughly seventeen hours later.

One detail worth sitting with: the poisoned files were delivered from Optimizely's own domain, cdn.optimizely.com, with a valid Optimizely certificate. Browsers and most security allowlists treated them as legitimate, because by every technical check they were. Report URI's Helme put it plainly: trusted JavaScript doesn't always remain trustworthy. That sentence is the lesson of this whole incident — and it is why the usual advice, stick to sites you know, failed everyone who followed it yesterday.

How One Signup Flaw Reached 178 Companies

Advertisement

Optimizely Web is an A/B testing platform. Its customers add a single script, called a snippet, to their pages. The snippet is hosted by Optimizely and carries the platform's code, the customer's experiments, and an optional field called Project JavaScript, which holds custom code that runs on every page. It is a convenient design, and a single point of failure for every site that uses it: poison the platform, and you poison all of them at once.

That is what happened. According to Report URI, the attacker wrote a short loader into the Project JavaScript field of many unrelated customers' projects. The loader added a script tag pointing at the attacker's server, and the rest of each snippet was left untouched — which is why the infection was hard to spot at a glance. This was not CDN cache poisoning, because the content delivery network served exactly what Optimizely's platform gave it. The problem was write access inside the platform itself.

Optimizely has confirmed that an attacker exploited a vulnerability in its Experimentation account signup flow to plant the code. A spokesperson, Victoria Johnson, told Gizmodo that an unauthorized party used a flaw in the signup flow to add malicious JavaScript to some customer projects, and that the company blocked the vulnerable path, deployed a fix, and notified every affected customer. The company also says it ended active sessions, revoked tokens, reset access for affected user accounts, and blocked delivery of the injected code at Cloudflare.

What Optimizely has not said is the part I actually want to hear. It has not said how a flaw in a signup flow gave an outsider write access to existing customers' projects, how many customers were affected, when the attacker first got in, or whether any customer data held by Optimizely was accessed. It has not published a technical description of the vulnerability. Until those answers exist, every Optimizely customer is guessing about the same question you are: was my site one of them? The snippets for Optimizely's own website and its login page carried the code too, which tells you something about how little the attacker cared about staying subtle.

Some snippets also carried a full copy of the malware inside the trusted file itself. Hudson Rock recovered BBC and HSBC UAE scripts with an identical 24,392-byte Base64-encoded payload that runs if the remote download fails or takes longer than 2.5 seconds. That matters because blocking the attacker's domain did not stop it. The backup copy was already sitting inside a file your browser trusted.

What the Code Did to Visitors

A phone showing a generic payment screen with a red swap icon and a cracked padlock, representing the crypto address swap

Every visitor to an infected page received the same track.js script with all of its components active. The main component is a crypto clipper — malware that replaces a wallet address with the attacker's at the moment the victim uses it. It recognises Bitcoin, Ethereum and other EVM chains, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin addresses, checks that each one is valid, and swaps it in page text, forms, links, the clipboard, outgoing network requests and the iOS share sheet. StepSecurity, which read the code independently, says the swap happens only near payment words such as "wallet", "deposit" or "send". That is deliberate: it keeps the malware quiet until the exact moment money is about to move.

The card skimmer watches form submissions for a card number, expiry date and CVV, and sends them to the attacker's server. There is one real piece of good news: payment fields hosted by a processor inside a separate frame, such as those from Stripe or Adyen, were out of its reach. Card fields built into a site's own page were not. If you paid on an affected site yesterday and the card form was part of the page itself rather than a processor's embedded frame, treat that card as exposed.

When the script swapped an address, it also sent the attacker the page URL, a screenshot of the page and any cookies that JavaScript can read. Cookies flagged HttpOnly were not exposed. On iPhones and iPads, the script loaded a second stage from attacker-registered .icu domains and ran an exploit chain in a hidden frame, chosen by iOS version. Report URI identifies the chains as Coruna and DarkSword, two iOS exploit kits that Google's Threat Intelligence Group documented in March 2026. Devices on iOS 13 to 17 got Coruna; devices on iOS 18.0 to 18.7.2 got DarkSword; iOS 18.7.3 or later and iOS 26.3 or later are patched against both. Devices on iOS 26.0 to 26.2 got a separate chain that only fingerprints the device.

Nobody has shown that an iPhone was actually compromised through this campaign. Hudson Rock retrieved the exploit delivery pages using iOS 18.6 and 17.5 browser identifiers, but ran the tests in headless Chrome, so the results prove delivery and not successful exploitation. StepSecurity did not retrieve or analyse the iOS files. That is a genuinely open question, not a clean bill of health — and it is why updating your iPhone is the first item in the checklist below rather than an afterthought.

Were You Exposed? Three Questions That Settle It

Forget the headlines for a minute. Whether this attack touched you comes down to three questions, and you can answer all of them from memory.

Did you visit one of the affected sites on November 16? Report URI's list includes Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC in several regions, Equifax, Air France-KLM, Ledger, Peacock, Fox News, ASOS, Levi's, Vodafone Australia, Virgin Media, Starbucks Canada, Heineken, Change.org, UNICEF USA and PokerStars. StepSecurity found the payload itself stored in urlscan.io captures for 17 domains, including CNN, the BBC, Fox News, Zoom, Salesforce, GitLab, Hootsuite, Smartsheet, Air France, KLM and American Eagle. Appearing on a list means the site's Optimizely script was infected; it does not mean the site's own servers were breached. That distinction matters, but not to you as a visitor — the malicious code ran in your browser either way.

Did you paste a crypto address or type card details into the site's own form that day? This is the question that decides your risk. The clipper only fires near payment words, and the skimmer only fires on form submissions. If you only read articles, watched videos, or scrolled, the clipper and the skimmer had nothing to take. If you sent crypto from a page on one of those sites, check the destination address character by character against the one you intended — a completed transfer to a swapped address cannot be reversed. If you typed card details into the site's own payment form, watch your statements and consider replacing the card; StepSecurity advises treating it as compromised.

Were you on an iPhone or iPad? The iOS exploit stage is the one part of this attack where the risk is not tied to something you typed. If you opened an affected site on an iPhone or iPad on November 16, update to iOS 18.7.3 or later, or iOS 26.3 or later, which Report URI says are patched against both kits. Your installed version is under Settings, then General, then About. Do this even if you did nothing else on the site. It costs two minutes and it closes the one door in this story that nobody has proven stayed shut.

Do This Now, In This Order

If you answered yes to any of the three questions above, work this list top to bottom. It takes about fifteen minutes, and the order is deliberate: close the open holes first, then clean up the credentials, then watch for the follow-on fraud.

Update your iPhone or iPad. iOS 18.7.3 or later, or iOS 26.3 or later. This is first because it is the only item on the list where the damage, if it happened, is invisible and ongoing.

Check any crypto you moved on November 16. Compare the destination address character by character with the intended address, and confirm it on a hardware wallet screen where possible. If funds went to the attacker's address, they are gone — but knowing that now beats discovering it when you next open your wallet.

Advertisement

Check your card statements, and replace the card if you typed its details into an affected site's own form. A card you only used through a Stripe or Adyen frame is fine; a card you typed into the site's own checkout page is not. Replacing a card is annoying. Explaining a drained account to your bank is worse.

Change your passwords, starting with your email. Email is the key to every reset link you own, so it goes first, then banking, then shopping. Do this from a device you trust, not the one you browsed the affected sites on if that device is your iPhone and it is not yet updated. Use a password manager rather than your memory — memory reuses passwords, and reuse is what turns one stolen cookie into ten stolen accounts.

Sign out everywhere on the affected sites and sign back in. Optimizely says it ended sessions and revoked tokens for affected accounts, but your sessions on the affected sites themselves are yours to close. Revoking a session kills any cookie the attacker may have copied. It takes seconds per site and it is the cheapest insurance in this list.

Watch for the phishing wave that follows. Stolen data does not get used the day it is stolen; it gets sold, sorted, and used weeks later. Expect convincing emails that mention the sites you use, because the attackers now know which ones those are. Microsoft counted 7 billion phishing emails in a single quarter this year, and the messages built from real breach data are the ones that work — that scale is the context for everything that follows. If an email about one of the affected sites asks you to click, log in, or verify anything, go to the site yourself instead of tapping the link.

Your Email Is the Master Key

Hands typing on a laptop showing a generic email inbox with a green shield icon

Here is the part of this story nobody puts in the headline. The Optimizely attack harvested the things that let an attacker become you: session cookies that keep you logged in, card details, wallet addresses. And the single credential that ties all of them together is your email address, because every password reset, every login alert, every "verify it's you" message flows through it. One email address, used for everything, is a single point of failure in exactly the same way Optimizely's snippet was — poison one thing and you poison all of it.

The fix is compartmentalisation: give throwaway signups a throwaway address, and keep your real inbox for the accounts that actually matter. A disposable address that only exists for one site cannot be used to reset your bank password, because your bank never saw it. A cookie stolen from a news site cannot be chained to your email account, because the two were never linked. The attack still hurts — a stolen card is a stolen card — but the blast radius stops at one site instead of spreading to all of them.

I tested the cheapest version of this myself this morning, on our own homepage, because I do not want to recommend a tool I have not just watched work. I opened tempomailusa.com and it handed me a disposable address immediately — no signup, no login, no payment. The address was a random ten-character string on the rover.info domain, and the live inbox loaded with it, auto-refreshing and empty, waiting for mail. I used the Change button to generate a fresh address, and the site confirmed it with a toast: "The Email has been successfully updated." The countdown next to the inbox read "Expires in 29d 23h 58m 33s" — a fresh thirty-day window for a free inbox, which is far more generous than the site's own FAQ suggests. That FAQ still says a temporary address lasts "several minutes or a few hours", which is out of date against the live countdown I watched. The free tier has limits worth knowing: one active inbox at a time, and your first message is free to read, with Pro needed to read every message. For the job this article describes — a one-off signup on a site you do not trust with your real address — the free tier is enough, and it took less than a minute.

If you want the fuller version of the same test, we put nine disposable services through their paces earlier this month and kept the ones that actually deliver mail. And if you are curious what a rising temp-mail search looks like from the inside, the Tempgmail spike earlier today is the same pattern: a service suddenly everybody is searching for, tested live, inbox and all.

None of this would have stopped the Optimizely attack from running in your browser. That is not the claim. The claim is smaller and more useful: the next attack will harvest whatever your browser and your inbox hand it, and a disposable address hands it less.

The Earlier Wave Nobody Connected

OPTIMJACK, as independent researcher Amirul Cyber named the campaign, was not the attacker's first run at this. Report URI and Hudson Rock both traced an earlier wave, from November 13 to 16, in which the same actor's injector script was served through Kissmetrics, StorifyMe and Minute Media's minute-ly scripts. Hudson Rock tied those to sites including securitybank.com, faz.net, smh.com.au and foxsports.com. Same injector, different delivery platforms, three days earlier. The Optimizely wave was the loud one because of the names involved, but the actor had been working the same trick through smaller pipes all week.

There is also a loose end worth naming so it does not become a rumour: Optimizely confirmed in February 2026 that attackers reached some of its internal systems through a voice-phishing attack. Neither the company nor any researcher has linked that incident to OPTIMJACK. Two incidents at one company in one year is a bad look, but a bad look is not evidence, and I am not going to connect dots the researchers have not connected.

The pattern that does connect, across both waves, is the one from today's malware spike: the way in is almost always something ordinary — a trusted script, a routine signup, an email that looks right. The defences that work are boring ones: update the phone, check the statements, and stop handing your real email to every site that asks.

Why 85% of Sites Couldn't Stop It

If you are wondering why 178 professional organisations, many with serious security teams, all fell for the same trick, the answer is in Report URI's Content Security Policy numbers, and they are grim. CSP is a browser control that limits where a page may load scripts from and send data to. It stopped the attack at only 24 of the organisations Report URI assessed — about 15%. Sixty-eight had no policy at all.

Allowing cdn.optimizely.com offered no protection, because the malicious code came from that host. A strict script-src allowlist blocked the download of track.js, while the 'strict-dynamic' keyword let it through. The 'unsafe-eval' keyword, which Optimizely's own documentation tells customers to allow, let the embedded fallback run at HSBC even though the download was blocked. A restrictive connect-src stopped card, cookie and screenshot theft but not address swapping, which happens inside the page.

Read that again, because it is the technical heart of the story: the defences failed in the specific places where the platform's own guidance told customers to leave the door open. This is not a story about lazy site owners. It is a story about a supply chain where the trusted supplier was the vulnerability, and the standard hardening advice assumed the supplier was safe. That assumption is now dead, and the sites that survive the next version of this attack will be the ones that treat every third-party script — including the ones they pay for — as untrusted code running on their pages.

Frequently Asked Questions

Was my data stolen if I visited CNN or the BBC on November 16? Not necessarily. The malicious code ran in your browser when you loaded an infected page, but the clipper and the skimmer only took something if you pasted a crypto address or typed card details into the site's own form. If you only read articles, they had nothing to take. If you were on an iPhone or iPad, update to iOS 18.7.3 or later, or iOS 26.3 or later, regardless of what you did on the page.

Is the attack still active? Largely no. The injected code was mostly removed on the evening of November 16 — infected scripts fell from 169 at 20:56 UTC to one at 21:52 UTC — and Optimizely confirmed the incident and the fix on November 17. Reports published on November 17 that describe the attack as ongoing are relying on the earlier count. A clean script today does not prove it was clean on November 16, so the exposure window is what matters, not today's status.

How much money did the attackers actually steal? Report URI counted about $7,040 in the attacker's wallets by 19:25 UTC on November 16, most of it Bitcoin; StepSecurity's own count came to about $6,600. Neither figure covers stolen cards, cookies or iOS access, which leave no trace on a blockchain. The crypto number is the visible tip, not the total.

What is a crypto clipper, exactly? Malware that replaces a cryptocurrency wallet address with the attacker's at the moment you use it — in page text, forms, links, the clipboard, network requests and the iOS share sheet. It checks that the replacement address is valid, and it only fires near payment words such as "wallet", "deposit" or "send". The defence is unglamorous: compare the address character by character before you send, and confirm it on a hardware wallet screen where possible.

Should I stop using the affected websites? No. The sites themselves were not breached; their Optimizely scripts were poisoned, and the code has been removed. There is no reason to boycott the BBC or Zoom. The reason to change your behaviour is narrower: use a disposable address for signups, keep your real inbox for the accounts that matter, and check the statements for any card you typed into a site's own form on November 16.

How do I know if an email about this attack is real? Assume it is not, until proven otherwise. The attackers now hold data about which sites you visited, which makes their phishing unusually convincing — and the Apple ID security-notice scam we covered today works the same way, dressing a fake message in a real event. A real notice from a bank or a site never asks you to tap a link to verify yourself. Go to the site yourself, type the address yourself, and check there.

The Optimizely attack will not be the last supply-chain breach, because the economics favour the attacker: poison one platform, reach hundreds of sites, and let the victims' own trust do the delivery. You cannot fix that from your side of the screen. What you can do is make yourself a worse target — an updated phone, a card you actually watch, passwords that start with your email, and an inbox that hands strangers nothing they can reuse. None of it is heroic. All of it works.

Need a disposable temporary email?

Protect your real inbox from spam and promotional clutter instantly and free.

Generate Now

Received a suspicious email, text, or charge alert?

Verify whether the sender domain is disposable, spoofed, or unverified before clicking links.

Verify Email Sender

Take TempoMail USA anywhere

Faster OTPs, instant push notifications, and offline inbox access — free on Android.

Get it on Google Play
Advertisement
Emily Parker

Emily Parker

Editor — email privacy & digital hygiene

Emily Parker writes and edits TempoMailUSA's guides on disposable email, account security, and online privacy.

Join the Conversation 0

Join the discussion

Log in to share your thoughts, ask questions, and reply to others.

Log In or Sign Up

Be the first to share your thoughts on this article!