New ebook: Before You Borrow, how lenders decide and how to get your business loan approved. Get it for $7.99 →
New ebookHow to Research Like a Wall Street AnalystFind original sources, analyze trends, build your own insightsGet it now →
Markets
Real businesses. Bigger perspective. · Tue, Nov 17, 2026News. Tools. Scores. Games. Free.The Morning Chronicle
Donate BTCOpen dDashboard

U.S. News

Visited Zoom, CNN or HSBC on Nov. 16? What to check now after the Optimizely attack

A script on 178 sites could swap crypto addresses, copy card numbers typed into forms and target older iPhones. Most people were not affected, and a few checks settle it.

Bar chart of crypto received by attacker wallets: Bitcoin about $5,489, Litecoin $760, USDT on TRON $719, Ether $101, USDT on BSC $82
About $7,100 in crypto reached the attacker wallets, per Report URI. Chronicle graphic.

On Monday, Nov. 16, a malicious script ran on 178 organizations' sites, including Zoom, CNN, HSBC and the BBC, after attackers tampered with code delivered by Optimizely, according to Report URI. The code is gone, and being on the list does not mean you were affected. Here is how to tell whether you might be, and what to do. The full account of what happened is in our news report.

First: were you in the window?

Report URI's timeline is in UTC. Converted to Eastern time (EST), the first infection was seen at 11:21 p.m. Sunday, the crypto-swapping code went live about 3:28 a.m. Monday, and the card-capturing part was added at 8:43 a.m. Monday. Mass cleanup came between roughly 3:40 and 4:10 p.m. Monday, with one site still infected at 4:52 p.m. Each site was fixed at a different time. If you did not visit an affected site on Monday, you are very unlikely to be involved.

1. Card statements

If you typed a card number into a form directly on an affected site on Monday, watch that card. Report URI says the code captured card number, expiry and security code from forms, but not from payment boxes hosted by providers such as Stripe or Adyen, which sit in a separate frame. Check recent charges now and again next week. If anything is unfamiliar, call the number on the back of the card; a replacement card is free and quick. Nobody has published how many cards were taken.

2. Crypto addresses

This is where the confirmed losses are: about $7,100 across the attacker's wallets, per Report URI's tally, and Galaxy Digital's Alex Thorn estimated victims sent about $2,300 (Cointelegraph). If you sent crypto on Monday after copying an address from an affected site, compare the address you sent to with the one you meant, in full, on a second device or in your exchange's withdrawal history. If they differ, contact the exchange and the receiving service immediately. A hardware wallet's own screen is the check that does not depend on your browser.

3. Update older iPhones and iPads

The code tried to run exploit kits on Apple devices. Per Report URI, the kit's own comments say iOS 18.7.3 and later, and 26.3 and later, are patched. A visible symptom on iOS 18.6 or earlier was the page reloading every 60 seconds. Update in Settings, General, Software Update. Devices that cannot run the newer versions are the real exposure; Report URI lists iOS 13 to 17 as targeted too. There is no public report of a device being compromised, and checking for one is hard, so treat an update as the sensible step. If the phone did anything odd on Monday, or holds banking apps and cannot be updated, consider a reset.

4. Sessions and cookies

Report URI says the script also sent some cookies that scripts can read, along with the page address and a screenshot, when it swapped an address near payment or wallet wording. If you were logged in to an affected site on Monday, sign out everywhere, sign back in, and change that password if you reuse it. Turn on two-factor authentication where offered. Clearing cookies in your browser does the sign-out for all sites at once.

How to know if you were exposed

You will probably not see a sign. The honest answer is that exposure needs three things together: you visited an affected site during the window, you did something the code watches for (typed a card, copied a crypto address, used an unpatched iPhone), and that site had not yet been cleaned. Companies may notify customers; Report URI suggested affected companies consider it. Beyond that, watch statements, not headlines.

Business owners who load third-party scripts on their own site can read our small-business checklist.

Sources: Report URI; Cointelegraph. Times converted from UTC by the Chronicle. Information, not security advice.

Want your business to be the answer?

Get a full package of articles about your business, built so customers, Google and AI assistants can find you.

Get featured
New ebook from The Company ChronicleHow to Research Like a Wall Street AnalystFind original sources, analyze trends, and build your own insights. 36 pages with worksheets.Get the ebook · $29Instant PDF download
New ebook from The Company ChronicleHow to Research Like a Wall Street AnalystFind original sources, analyze trends, and build your own insights. 36 pages with worksheets.Get the ebook · $29Instant PDF download

Business Spotlight

Want us to publish your business?

Our team writes and publishes articles about your business on The Company Chronicle every month, with a link to your website. Plans from $30 a month, cancel anytime.

Publish with us

The Chronicle directory

What are you into?

The Chronicle, coast to coast

Every corner has a story.

The full Chronicle illustration