Optimjack Malware Hit 178 Sites: India Crypto Safety Guide

On Monday 16 November 2026, visitors to some of the most trusted websites on the internet — the BBC, CNN, Zoom, Salesforce, HSBC and the hardware-wallet maker Ledger among them — were served malware without any of those companies being breached. The Optimjack malware attack, named by independent researcher Amirul Iman and disclosed the same day by security researcher Scott Helme of Report URI, hid inside Optimizely, the A/B-testing tool those sites load on every page. For more than 13 hours it swapped cryptocurrency wallet addresses for the attacker's own, skimmed payment cards typed into checkout forms, and stole cookies and screenshots. For Indian readers the lesson is blunt: the danger was not a shady website. It was an ordinary one.
> Educational content only. This is not financial advice. Crypto markets are volatile — never invest money you can't afford to lose. This guide explains a reported security incident; it does not recommend any product or service, and it does not claim that any Indian website was affected.
What Happened: The Facts at a Glance
The story broke on 16 November 2026, when Scott Helme, founder of the security-monitoring service Report URI, published a detailed analysis after checking 1,611 Optimizely snippets and finding 188 of them infected, belonging to 178 organisations. The facts, as reported on 16–17 November 2026 by Cointelegraph, BleepingComputer (via Dealroom), StepSecurity, SecurityOnline, CyberKendra and KuCoin News, are:
| Fact | Detail |
|---|---|
| What happened | Malicious JavaScript injected into Optimizely customer projects, served to visitors of 178 organisations' websites |
| Who found it | Scott Helme, founder of Report URI; campaign named "OPTIMJACK" by researcher Amirul Iman |
| First infection seen | The BBC's snippet, at 04:21 UTC on 16 November 2026 |
| How it got in | An unauthorised party exploited a vulnerability in Optimizely's Experimentation account signup flow |
| What it did | Swapped crypto wallet addresses, skimmed payment cards, stole cookies and screenshots, pushed iOS exploit kits |
| Crypto stolen | About $7,040 in crypto confirmed on-chain by 19:25 UTC on 16 November (Report URI); StepSecurity counted about $6,600 |
| How long it ran | More than 13 hours; 187 of 188 infected scripts cleaned by 21:52 UTC on 16 November |
| Who was affected | 178 organisations including Zoom, BBC, CNN, Fox News, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM and Ledger |
| Optimizely's response | Confirmed the flaw, said it fixed it, removed the code, ended sessions, revoked tokens and notified affected customers |
How the Attack Worked
To understand why this attack reached so many people so fast, it helps to know what Optimizely is. It sells A/B-testing software: websites load a small Optimizely script on every page so they can try out different designs and measure which one works better. Browsers and security allowlists treat that script as legitimate, because it comes from Optimizely's own domain, cdn.optimizely.com, with a valid Optimizely certificate.
The attacker did not need to breach the BBC, or CNN, or Ledger. Instead, the attacker got code into the custom JavaScript field of many Optimizely customer projects. Every visitor to those sites then downloaded the poisoned script automatically, straight from Optimizely's own servers, with no warning and nothing visibly wrong on the page.
The timeline, reconstructed by Report URI and CyberKendra from the attacker's own infrastructure, shows how quickly it moved. The first Optimizely injection Report URI found was in the BBC's snippet at 04:21 UTC on 16 November, about two hours after the last clean capture of that file. The attacker registered the domain 1688360[.]cc at 05:23 UTC, built the first version of its payload file, track.js, at 08:10 UTC, and added a card-skimming component later in the day. The injected loader added a script tag pointing at that domain and left the rest of each snippet untouched, which is why the tampering was hard to spot: the legitimate Optimizely code still ran normally around it.
The cleanup was almost as fast as the attack. Report URI recorded a mass clean-up between about 20:40 and 21:10 UTC on 16 November, with infected scripts falling from 169 at 20:56 UTC to just one at 21:52 UTC — a snippet belonging to UK broadband provider TalkTalk. Ledger's snippet was cleaned at about 8:41 pm UTC. BleepingComputer independently confirmed the malicious script had loaded on many of the affected sites.
There is also a link to earlier attacks. SecurityOnline's analysis notes a confirmed technical link between this incident and an earlier injector-wave actor that operated through Kissmetrics, StorifyMe and Minute Media, and that the earliest Optimizely tampering caught on the BBC's snippet loaded that same earlier injector domain. The attacker is described as an unattributed, financially motivated group. No government, company or named hacking group has been blamed.
What the Malware Did to Visitors
The payload was a roughly 30 KB multi-purpose JavaScript file, and it did four distinct things to anyone whose browser loaded it.
The first and most important for crypto users was the address clipper. Whenever the script detected a valid, checksum-verified cryptocurrency address near payment words such as "wallet", "deposit" or "send", it replaced it with an attacker-controlled address. It recognised eight chains: Bitcoin, Ethereum and other EVM chains, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin. It did not only swap the address shown on the page. It also swapped the address in the visitor's clipboard, in forms, in links, in outgoing network requests and in the iOS share sheet. That is the detail that matters most: even if you copied an address from a completely different, trustworthy source while an infected tab was open, the clipboard swap could still have replaced it before you pasted it into your wallet.
The second component was a payment-card skimmer. It watched for card numbers typed into the website's own payment forms, validated them with the Luhn checksum — the same arithmetic banks use to check a card number is well-formed — and sent them to the attacker using sendBeacon, a browser feature that quietly transmits data in the background. The skimmer ran on the sites' own checkout pages, so a visitor typing card details into a familiar, trusted brand's payment form had no reason to suspect anything.
The third component stole cookies and screenshots. It used html2canvas, a library that renders a copy of the visible page, to capture screenshots, and it exfiltrated browser cookies alongside them. Cookies matter because they can carry logged-in sessions: with a stolen session cookie, an attacker can sometimes act as the logged-in user on a website without knowing the password.
The fourth component targeted iPhones and iPads. The script loaded a hidden iframe carrying two iOS exploit kits, Coruna and DarkSword, which Google's Threat Intelligence Group documented in March 2026. These kits target older iOS versions, roughly iOS 13 to 18.x. They are the same kits behind a separate iPhone wallet-drain investigation reported earlier in November, in which funds were stolen from TRON wallets. The Optimjack payload delivered them to visitors of ordinary websites — a reminder that the kits are now being distributed through mainstream web traffic, not only through malicious apps or links.
How This Differs From the DarkSword iPhone Thefts
Regular readers may recognise the names Coruna and DarkSword. On 7 November, this site published a guide about a Bitquery investigation into at least $4.06 million in USDT stolen from 365 TRON wallets between 5 October and 4 November 2026, in which the same two exploit chains were used to steal seed phrases from iPhones. That post covered the thefts themselves: the wallets drained, the amounts, the vulnerability chain in iOS 18.4 to 18.7, and the fixes in iOS 18.7.7 and 26.3.
This post is about something different: the delivery mechanism. The Optimjack attack is a web supply-chain incident. Nobody's phone was the target, and no seed phrase was stolen by the Optimizely script itself. The iOS exploit kits were one component of a payload that also swapped crypto addresses, skimmed cards and stole cookies — and they were delivered to visitors of the BBC, CNN, Zoom and 175 other mainstream sites. The DarkSword post explains what the kits do once they reach a phone. This post explains how they reached ordinary web users at all.
Why the Confirmed Losses Look Small — and Why That Is Misleading
The on-chain figures are small. Report URI counted about $7,040 in the attacker's wallets by 19:25 UTC on 16 November, most of it Bitcoin, with Litecoin, Ethereum, BSC and TRON making up the rest. Cointelegraph's own check of blockchain records put the figure at about $7,100. StepSecurity's separate analysis put funds received or held across the wallets at roughly $6,600, while noting that some of those addresses had activity predating the attack. Galaxy Digital's head of research, Alex Thorn, went further in a forensic follow-up reported on 17 November: only 19 fraudulent transactions across 18 addresses, with the real losses revised down to about $2,266, including roughly $600 from victims on the Bitcoin blockchain — most of the other transfers, he said, were the attackers moving money between their own wallets. SecurityOnline adds that the funds were swept toward HitBTC deposit addresses starting at 13:03 UTC.
Those numbers are reassuring only if you stop there. Three things make them misleading as a measure of the incident.
First, the exposure was enormous and the window was long. The 178 affected organisations include some of the most visited sites on the internet, across 20 sectors: 20 retailers such as IKEA, ASOS and American Eagle, 12 entertainment brands, 10 media outlets, nine airlines and six crypto platforms including Ledger. Millions of people loaded those pages during the 13-plus hours the script was live. A clipper that fires only when a wallet address appears near a payment word will miss almost everyone — and still catch the few who happened to be moving crypto at that moment.
Second, the card and cookie theft is unquantified. Nobody knows how many card numbers were skimmed, how many session cookies were taken, or how many screenshots were captured, because that data went straight to the attacker's server and has not been recovered. The $7,040 figure counts only the crypto that arrived in wallets researchers could identify. It says nothing about the cards, and nothing about what the cookies will be used for in the coming weeks.
Third, the iOS exploit kits may have a delayed effect. A phone compromised through a hidden iframe on 16 November does not necessarily lose money on 16 November. The kits are designed to steal seed phrases and credentials that can be used later, quietly. That is why the checklist below includes updating iOS and reviewing wallet activity over the coming days, not just on the day of the attack.
What It Means for Indians
No Indian organisation appeared in the published list of affected sites, and no Indian website has been confirmed as infected. But that is a narrow comfort. Indian crypto users visit the same global sites every day: the BBC and CNN for news, Zoom for work calls, Salesforce for business, and Ledger's website when setting up or managing a hardware wallet. The attack did not care where the visitor lived. Anyone who copied a wallet address or typed card details into one of those sites on 16 November was exposed in exactly the same way, whether they were in Mumbai, Manchester or Melbourne.
There is also a specifically Indian habit that makes clipboard attacks dangerous here. Many Indian users move crypto by copying an address from an exchange app or a chat message and pasting it into another app — often quickly, on a phone, while juggling UPI payments and OTPs. The Optimjack clipper was built for exactly that moment: it swaps the address in the clipboard itself, so the pasted address looks right at a glance. The middle of the address changes; the beginning and end often look similar enough that a quick check misses it. On a small phone screen, under time pressure, almost nobody verifies every character.
The Indian context also includes the tax rules, which are unchanged by this incident. Gains on crypto transfers are still taxed at a flat 30% plus a 4% cess, and sales still attract 1% TDS. Tax note: crypto tax rules can change — the 30% rate and 1% TDS described here were current as of September 2026. Verify the latest rules before filing. A stolen transfer is still a transfer for tax purposes in the sense that the loss itself does not erase the reporting obligation, and victims should keep records of what happened — dates, amounts, addresses, screenshots — both for any police complaint and for their own tax records.
One more Indian angle matters. India has no equivalent of the US or EU incident-disclosure rules that force a company to tell users quickly when its systems are abused. Optimizely is an American company, and it confirmed the incident the same day only after researchers published their findings. Indian users of global services should assume the first reliable warning will come from security researchers and independent reporting, not from the company whose tool was abused.
How to Check Your Transfers: A Safety Checklist
If you visited any of the affected sites on 16 November — the BBC, CNN, Zoom, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, Peacock, Fox News, ASOS, Levi's, Vodafone Australia, Virgin Media, Starbucks Canada, Heineken, Change.org, UNICEF USA, PokerStars, or any of the other 150-plus organisations on Report URI's list — work through these steps.
First, check every crypto transfer you made on 16 November. Open the transaction in a block explorer or in your wallet's history and compare the destination address, character by character, with the address you intended to send to. If the address does not match, the funds went to the attacker, and a blockchain transfer cannot be reversed. Note the transaction hash, the intended address and the actual address, and keep them together — you will need them for any complaint.
Second, check your card statements. If you typed card details into any affected site's payment form on 16 November, watch the statement for small test charges as well as large ones: card thieves often run a tiny transaction first to check the card works. If you see anything you do not recognise, call your bank and ask for the card to be blocked and replaced. Under Indian banking rules, reporting an unauthorised transaction quickly is what protects you, so do not wait to see whether more charges appear.
Third, change the passwords on your important accounts, starting with your email and your exchange accounts, and turn on two-factor authentication everywhere it is offered. The script stole cookies, and a stolen session cookie can let an attacker act as you on a website without your password. Changing the password ends those sessions. If your exchange offers withdrawal allowlisting — a list of addresses that are the only ones withdrawals can go to — turn it on.
Fourth, update your iPhone or iPad. The Coruna and DarkSword kits in the payload target older iOS versions, and Apple has shipped fixes: the DarkSword chain is addressed in iOS 18.7.7 and 26.3. If your device is on an older version, update it now, and check that automatic updates are switched on so the next fix reaches you without delay.
Fifth, change how you copy addresses from now on. Verify the first and last six characters of every pasted address against the source before you confirm a transfer. If you use a hardware wallet, check the address on the device's own screen — the device shows what it will actually sign, and malware on your computer or phone cannot change that display. For a large transfer, send a small test amount first and confirm it arrived before sending the rest.
Finally, report it if you lost money. In India, crypto fraud can be reported on the National Cyber Crime Reporting Portal at cybercrime.gov.in, or by calling 1930, and to your local police station. Keep the transaction hash, the addresses, the date and time, and screenshots of what you saw. Recovery of stolen crypto is rare, but reports help investigators link cases together.
What to Watch Next
Four things will determine how this story develops, and all four are worth watching over the coming days.
The first is the final victim count. Optimizely has said it notified affected customers, but no company has yet said how many of its users were exposed, and no exchange or wallet provider has reported a wave of victim reports. Watch for statements from Ledger and the other crypto platforms on the list: they are the ones whose users are most likely to have lost money.
The second is the full post-mortem. Optimizely says it is still investigating, and it has not yet explained how the attacker got in beyond the signup-flow vulnerability, or whether the attacker still holds access to any customer project. A proper post-mortem should answer both questions, and it should say what changes Optimizely is making so that one compromised signup cannot poison hundreds of customer scripts again.
The third is whether the same actor strikes again. The confirmed link to the earlier Kissmetrics, StorifyMe and Minute Media injector waves suggests this is not a one-off intruder but a group that specialises in poisoning trusted third-party scripts. The pattern to watch for is the same signature — a small loader added to a widely used script, pointing at a newly registered domain — appearing on a different platform.
The fourth is the iOS fallout. The Coruna and DarkSword kits were already the subject of a major investigation earlier in November, and their appearance inside a mainstream web attack widens the population at risk from a few hundred TRON wallets to anyone who visited a popular website on an unpatched iPhone. Watch for Apple's next security notes and for any reports of thefts traced back to 16 November visits — those would show whether the kits actually compromised devices through this route.
The Bottom Line
On 16 November 2026, attackers hid malware inside Optimizely, the A/B-testing tool loaded by 178 major organisations, and served it to visitors of the BBC, CNN, Zoom, Salesforce, HSBC, Ledger and more than 170 other sites for over 13 hours. The malware swapped cryptocurrency wallet addresses for the attacker's own, skimmed payment cards, stole cookies and screenshots, and pushed iOS exploit kits at visitors' phones. About $7,040 in crypto has been confirmed stolen on-chain, though later forensic work suggests the true figure may be closer to $2,266 — and the card and cookie theft remains uncounted. Optimizely confirmed the flaw and says it has cleaned the infected scripts, with 187 of 188 cleared by the evening of 16 November.
For Indian users, no Indian site was confirmed affected, but the sites that were hit are the ones Indians use every day, and the clipboard trick the malware used targets exactly how most people move crypto on their phones. The defence is unglamorous and it works: verify every pasted address character by character, check the address on your hardware wallet's screen, send a test amount first, update your phone, and check your transfers and card statements from 16 November now. Trusted websites can be poisoned without their owners knowing. Your clipboard is the last line of defence — treat it that way.
Keep Learning
Frequently asked questions
I visited one of the affected websites on 16 November. Am I at risk?
It depends on what you did while the malicious script was live. Simply loading a page was not enough to lose money — the crypto clipper only acted when a wallet address appeared near payment words like 'wallet', 'deposit' or 'send', and the card skimmer only captured details typed into a payment form. If you copied a wallet address or entered card details on any of the affected sites on 16 November, check your transfers and card statements now. If you only read an article and typed nothing, your exposure is limited to cookies and screenshots the script may have collected, and changing your passwords on important accounts is a sensible precaution.
How do I know the wallet address I copied is the right one?
Never trust a pasted address on sight. Compare the first and last six characters of the pasted address with the address shown by the recipient, character by character — clipboard malware changes the middle of an address while keeping it looking plausible. If you use a hardware wallet, check the address on the device's own screen before confirming, because the device shows what it will actually sign. For a large transfer, send a small test amount first and confirm it arrived before sending the rest. These habits protect you against every address-swapping attack, not just this one.
Was my Ledger hardware wallet itself hacked?
No. The attack poisoned the JavaScript on Ledger's website, not the Ledger device or its firmware. No hardware wallet was breached, and the attack did not touch the secure chip inside the device or the recovery phrase stored on it. The risk was specific and narrow: if you copied a wallet address from ledger.com — or from any affected site — while the malicious script was running on 16 November, the address in your clipboard may have been swapped for the attacker's. Ledger's own snippet was cleaned at about 8:41 pm UTC on 16 November, according to Report URI's tracking.
Related guides
- GTA 6 Crypto Scams: 8,800 Fake Tokens Target Indians — GTA VI launches today — and scammers are ready. Blockaid flagged 8,800+ fake GTA tokens on Solana. How the drainers work and how Indian gamers stay safe.
- Can You Insure Crypto in India? A Beginner's Guide 2026 — Can you insure your crypto in India? Learn what crypto insurance covers, where protection exists, and the safety steps that matter more today.
- Etherscan Support Hack Attempt: What Indian Users Must Know — Etherscan says attackers tried to break into its Freshworks support system on 18 November. No breach is confirmed — but fake-support phishing is the real risk.