Big-Name Websites Hit By Cyberattack
A hijacked testing tool from a company called Optimizely put card-skimming and crypto-stealing code on the sites of 178 organizations, including Zoom, CNN, HSBC and Alaska Airlines.

From Sunday night through Monday afternoon, some of the world’s most-visited websites handed visitors malware. Their own servers weren’t necessarily hacked. They had trusted an outside vendor.
The vendor is Optimizely, which sells tools companies use to test changes to their websites. Each customer’s site loads a small piece of code, a “snippet,” from Optimizely’s servers on every page. Customers can add their own code to a field called “Project JavaScript.”
Attackers wrote their own code into that field. According to security researcher Scott Helme of Report URI, who uncovered the attack, his team checked 1,611 Optimizely snippets and found 188 infected ones belonging to 178 organizations. The names on his list include Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock. Banking and finance was the biggest group, with 32 organizations.
Names that hit close to home include hawaiianairlines.com, alaskaair.com, and zoom.com. Alaska flies from Redding to Seattle, and many people connect via Hawaiian Air to book their getaway vacations to the Islands. Also, countless remote workers and Redding businesses regularly use Zoom to stay connected. Being on the list doesn’t mean any particular visitor was harmed, but if you booked a flight Monday or connected to Zoom, read on. Researchers have nicknamed it “OPTIMJACK.”
What the code did
Helme says the malware was “a multi-purpose kit.” It did four things:
Swapped crypto addresses. Copy a wallet address, and the code could paste the attacker’s instead.
Skimmed cards. It grabbed card numbers, expiration dates and security codes typed into a site’s own checkout forms. Cards entered in hosted payment boxes, such as Stripe’s, were out of its reach.
Stole cookies and screenshots. Cookies can keep you logged in.
Went after iPhones and iPads. It tried to load two known iOS attack kits, Coruna and DarkSword, on older devices. Successful break-ins on devices haven’t been demonstrated.
Report URI counted about $7,040 in crypto reaching the attacker’s wallets by late Monday morning Pacific time. That number comes with an asterisk. Some of the wallets were in use before the attack, and one blockchain-analysis firm puts confirmed victim payments closer to $2,260. There’s no way to see how many cards were skimmed.
Who did this, and what are the feds doing?
No one has publicly attributed the attack. Report URI, Hudson Rock, and other researchers have not named a specific group or nation-state. The payload’s focus on crypto clipping, card skimming, and opportunistic iOS exploits points to financially motivated criminal activity rather than classic espionage or disruption. The same actor’s infrastructure appeared in an earlier wave starting November 13, through other third-party scripts (Kissmetrics, StorifyMe, and Minute Media), suggesting an ongoing campaign against web supply-chain tools rather than a one-off hit on Optimizely.
As of Tuesday morning, there are no public statements from the FBI, Department of Justice, CISA, or the Department of Homeland Security specifically addressing this incident. That silence is notable given the scale—websites belonging to major banks, tech companies, and media outlets were involved—but it is also consistent with how many supply-chain attacks played out in the first 24–48 hours. Attribution and federal response often lag behind the technical discovery, especially when the primary victims are website visitors rather than the companies’ internal systems. Local readers and businesses should not wait for a press conference to take the practical steps below.
Optimizely’s explanation
Optimizely said an unauthorized party exploited a vulnerability in the Experimentation account signup flow to add the code to customer projects. The company says it fixed the flaw, removed the injected code, ended active sessions, revoked tokens, reset affected accounts, and notified all affected customers. Report URI says every infected file it was tracking was clean by 3:11 p.m. Pacific Monday. Optimizely hasn’t said how many customers were hit.
Think about that: a bug in how new accounts get created let a stranger write code into other companies’ projects. Optimizely owes everyone a full explanation.
Commentary
Here’s what should bother everyone. Big companies put their own code through reviews, testing, and approvals, then let a browser fetch and run whatever code a third party provides. The only reason worse things didn’t happen is that the attackers simply chose not to do it.
Small businesses do the same thing with tracking pixels, chat widgets, analytics, and review badges, often with one pasted line of code. A Redding boutique on Shopify, a contractor on Wix, or a restaurant on WordPress probably isn’t using Optimizely, but it’s very likely using something that loads code from someone else’s server. Trust in big platforms is supposed to be earned. Monday showed that “big name” and “safe” aren’t the same thing.
What you should do
If you used an affected site from Sunday evening through Monday afternoon:
Update your iPhone or iPad. iOS 18.7.3 or later, or 26.3 or later, is patched against the exploit kits.
Watch your card statements and call your bank or credit union about anything strange.
Double-check any crypto transfer. Compare the address you pasted with the one you meant to pay, and confirm it with the recipient another way.
Watch for odd account activity on sites you were logged into.







