# Optimizely Attack: 178 Websites Served Card and Crypto Stealers

> Hidden code in Optimizely scripts hit visitors of HSBC, Zoom, IKEA, the BBC and 174 more sites with card skimmers, crypto address swaps and iPhone exploits.

Canonical: https://www.phishclean.com/blog/optimizely-supply-chain-attack
Last updated: 2026-11-17

November 17, 2026 - 6 min read

By [Chidambaram](https://www.phishclean.com/author/chidambaram), founder of PhishClean

On 16 November 2026, attackers hid malicious code inside the Optimizely website-testing scripts of at least 178 organisations, including HSBC, Zoom, IKEA, the BBC, CNN, Salesforce, Equifax and Ledger. Visitors to these genuine websites were exposed to card skimming, crypto address swapping and iPhone exploits. Here's what happened, what to do if you visited one, and why the usual "check the web address" advice couldn't help.

## What happened

Optimizely Web is a tool companies use to test changes to their websites. Each customer has a "Project JavaScript" field that runs on every page of their site. According to Report URI, which discovered the campaign, the attacker wrote a small loader into that field for many unrelated customers and left the rest of the snippet untouched. Report URI found malicious code in 188 of the 1,611 Optimizely scripts it examined, belonging to at least 178 organisations. How the attacker got write access is not yet known.

The loader pulled a script called `track.js` from `1688360[.]cc`, sometimes hiding the address in base64, and sometimes carrying the whole payload inline in case that server was blocked. Most of the code was removed by late on 16 November (UTC). Optimizely said on 17 November that it had contained the incident and contacted affected customers.

## What the code did to visitors

- **Crypto address swapping.** It looked for Bitcoin, Ethereum, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin addresses and replaced them with the attacker's: in the page text, in form fields, in what you copied, and in outgoing requests. About $7,040 reached the attacker's wallets within roughly nine hours; later counts put it near $7,150.
- **Card skimming.** From 13:43 UTC, it watched card forms, checked the number with the Luhn test, and sent card number, expiry and CVV to `1688360[.]cc/card.php` with `sendBeacon`. Cards typed into a payment company's own frame (such as Stripe or Adyen) were out of reach; cards typed into the site's own fields were not.
- **Data collection.** Page addresses, cookies that scripts can read, and screenshots of the page went to `1688360[.]cc/hit.php`.
- **iPhone and iPad exploits.** Apple devices were sent to exploit kits (Coruna for iOS 13 to 17, DarkSword for iOS 18) hosted on two `.icu` domains.

Being on the list does not mean a company's own systems were breached. It means code from a third-party tool ran on its website, in visitors' browsers.

## Why "check the address" couldn't help

Almost all phishing advice, and most anti-phishing tools, ask one question: is this the real website? Here the answer was yes. The address bar said hsbc.com or ikea.com, the padlock was there, and the site really was the company's. The attack was in the code the site loaded from a trusted supplier. To catch it, you have to watch what the page *does*: where it sends your card number, and whether the address you see is the one the site meant to show.

## If you visited an affected site on 16 November

- **If you typed a card into the site's own form**, call your bank and ask for the card to be blocked and replaced. Check recent statements.
- **If you sent crypto**, compare the address the payment went to with the one in your account or app. If it matches one of the attacker addresses below, report it to the exchange you sent from straight away; they can sometimes freeze funds that arrive at an exchange.
- **If you use an iPhone or iPad**, update to iOS 18.7.3 or later, or iOS 26.3 or later.
- **If you were signed in**, sign out and back in. Cookies that scripts can read may have been copied; the most sensitive ones usually can't be, but signing out ends any copied session.

Attacker wallet addresses published by researchers:

- Bitcoin: `19g9rZcPeiz8rUvyWpTRyXXhPnjsWrc3kW`
- Ethereum / BSC: `0xC4026b06D82b0F0B363eda0642D61CfbDc17884e`
- TRON (USDT): `THvs6p56XkUiMkJeSc51cAP64u2RsTYqxa`
- Litecoin: `ltc1q3wp7g6ds0ggg6fl6kncpa4sepn0q3qfacgred5`

## For companies that run third-party scripts

- Open every Optimizely Project JavaScript field and experiment custom code. Search for `1688360`, `atob(` and any code your team didn't write. One company was re-infected after cleaning up, so check again.
- Review Optimizely change history, users, API tokens and integrations, and rotate the credentials.
- Treat cards entered in your own fields on 16 November, and secrets in cookies without the HttpOnly flag, as exposed.
- Use a Content Security Policy that lists which servers scripts may load from and send data to. Of the affected sites Report URI checked, 68 had no CSP at all, and only 24 blocked the payload completely. Allowing `'unsafe-eval'` or `'strict-dynamic'` let it through.
- Take card numbers in your payment provider's hosted fields, not your own inputs. That alone kept cards out of this skimmer's reach.
- Block these servers at the network edge: `1688360[.]cc`, `webshell[.]lol`, `5vobauua3ojpklx[.]icu`, `eil786npto9u5bq[.]icu`, `l7bcsnwc7nzr3uo[.]icu`.

## What PhishClean does about it

The next update of the [PhishClean browser extension](https://www.phishclean.com/) adds Hijack Guard, free on every plan. It watches for what this attack did, on any website, including well-known ones:

- **Known attack servers.** If a page loads code from or sends data to a server used in an attack like this one, you see a warning naming it. New servers are added to a downloadable list the day they're published, without waiting for a store update.
- **Swapped addresses on the page.** If a crypto address on the page is replaced by a different one moments after it appears, PhishClean tells you, and shows both.
- **Swapped clipboard.** If the address you're pasting isn't the one you copied a few minutes ago, on any tab, PhishClean stops the paste and asks you first. This also catches clipboard malware on your computer.
- **Swapped fields.** If an address you typed or pasted into a form is changed without you touching it, you're told before you send.

Checkout Guard, in the trial and on Pro, already warns when a card number you type leaves the page for a server that isn't the shop or a payment company. It skips a short list of very large sites to avoid false alarms. From the next update it also warns on those sites when the card is going to a known attack server. In our reproduction of this skimmer, it warned on the press of Pay.

What it can't do: PhishClean is a desktop browser extension, so it doesn't protect against the Safari exploits on iPhone and iPad. Update iOS for that. It also can't see a request the page rewrites on its way out, or an address swapped before the page finished loading on a site that keeps changing addresses, such as a block explorer.

## Is this related to the Chase and Bank of America outage?

No. The same day, Chase, Bank of America, Wells Fargo and U.S. Bank customers reported problems with online banking and ATMs. Chase said the cause was a software bug in on-premise hardware and that there was no sign of a cyberattack. But outages like that are reliably followed by scams: fake "refund" texts, fake support numbers and calls asking you to "verify" your account. Our [outage scams guide](https://www.phishclean.com/blog/outage-phishing-scams-what-to-do) covers what those look like.

## Sources

- [Cyber Security News, 17 November 2026](https://cybersecuritynews.com/optimizely-websites-hijacked/): Report URI's findings, timeline, indicators and the affected sites named.
- [GBHackers, 17 November 2026](https://gbhackers.com/hackers-inject-malware-into-178-major-brands-websites/): the payload's behaviour and attacker wallet addresses.
- [BNO News, November 2026](https://bnonews.com/index.php/2026/11/optimizely-hack-spreads-malware-to-several-websites-including-hsbc-bbc-and-cnn/): affected organisations.
- [Forbes, 16 November 2026](https://www.forbes.com/sites/conormurray/2026/11/16/customers-report-outages-at-major-banks-chase-bank-of-america-wells-fargo-impacted/): Chase's explanation of the bank outage.

[Outage scamsWhat to do when a big service goes down.](https://www.phishclean.com/blog/outage-phishing-scams-what-to-do) [Can AI agents hack systems?What's real in 2026, and what isn't.](https://www.phishclean.com/blog/can-ai-agents-hack-cause-outages) [I clicked a phishing linkA recovery checklist.](https://www.phishclean.com/help/clicked-a-phishing-link) [PhishClean for TeamsThe same protection across your company.](https://www.phishclean.com/business)

## Try PhishClean free for 7 days

Every check on for 7 days, no card or account needed. Hijack Guard and the reported-phishing list stay free after that.

[Add PhishClean to your browser](https://www.phishclean.com/#install)

Last updated: 17 November 2026
