BLOCKBRIEFING
Crypto News

Crypto Cyber Attack Hits 178 Organizations as Wallet Theft and iPhone Risks Emerge

Pop art illustration of crypto cyber attack targeting websites, cryptocurrency wallets and iPhones
Editorial note: This report is for information, not investment advice. Market conditions can change. We identify primary sources and distinguish observations from predictions. Full disclaimer.

A crypto cyber attack spread malicious code through web pages used by at least 178 organizations on November 16, putting cryptocurrency transfers, payment details and some iPhone users at risk. Researchers traced the campaign to scripts delivered through the Optimizely Web Experimentation platform, rather than separate confirmed breaches at every affected company.

Security researcher Scott Helme and his team at Report URI reported finding 188 infected JavaScript snippets after examining 1,611 Optimizely files. Affected projects included those used on sites associated with Zoom, BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax and Ledger. These findings show malicious code was delivered through affected website components, not that each organization’s internal systems was hacked.

How the Crypto Cyber Attack Spread Across Sites

Optimizely provides code that companies add to their websites to test layouts and user experiences. Attackers inserted malicious instructions into a customer-project field called Project JavaScript. That code then reached visitors from an Optimizely web address the websites already trusted.

Optimizely acknowledged the security incident, saying an unauthorized party exploited a vulnerability in Experimentation. The company said it fixed the issue, removed injected code from affected projects, secured affected accounts and added protections. Its statement does not establish how many visitors were harmed.

Crypto Cyber Attack Targeted Wallet Addresses

The malware looked for cryptocurrency wallet addresses and attempted to replace them with addresses controlled by the attacker. Report URI identified support for Bitcoin, Ethereum-compatible chains, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin. It could interfere with copied addresses, payment fields, links and some outgoing browser actions.

This creates a simple but serious risk. Someone intending to send funds could copy a legitimate address, then paste an attacker-controlled one without noticing. Because blockchain transfers are usually difficult to reverse, checking only the first few characters of a destination is not enough. Users should verify the full receiving address using a trusted channel or hardware-wallet display before approving a transfer.

Report URI traced approximately $7,040 in cryptocurrency received by identified attacker wallets as of 19:25 UTC on November 16. That figure was a documented snapshot, not an estimate of the campaign’s final losses or the number of affected people.

iPhones and Payment Cards Were Also Targeted

The injected script also sought card numbers, expiration dates and security codes entered into certain website payment forms. Researchers observed attempts to collect accessible browser cookies and screenshots. Separately, the code tried to load Coruna and DarkSword exploit chains for older iPhone and iPad software. Researchers noted an additional path for iOS 26 that appeared to collect device information; its presence alone does not prove a successful device compromise.

These actions were built into the malware, but they do not prove every visitor lost funds, had a card stolen or had an iPhone infected. The scale of successful intrusions remains uncertain.

What Crypto Users Should Check After Exposure

Anyone who visited a potentially affected site on November 16 should update their iPhone or iPad to the latest compatible security release, review crypto transfers made during the exposure window, and compare transaction destination addresses with the intended recipient. People who entered payment-card details into an affected site’s own form should watch for unauthorized charges and contact their card issuer if anything looks suspicious.

Report URI later said all the infected Optimizely files it tracked had been cleaned by 23:11 UTC on November 16. That is encouraging, but a cleaned script cannot undo transactions already sent or data that may have been captured. The case shows why websites must monitor changes in third-party code, while wallet users must double-check the destination of every transfer.

For related security coverage, read BlockBriefing’s report on FaceStealer crypto theft and our coverage of the Chainalysis data incident.

Sources, corrections and methodology

How this reporting is prepared: BlockBriefing uses AI-assisted tools to support research, content preparation, editing and visual production. Information should be assessed against the original sources cited in each article. Our editorial standards explain our verification, authorship and correction procedures.

Article source links appear in the report above. We aim to distinguish independently verifiable facts, attributed claims, and analysis. If you find an error, please share the article URL and supporting documents.

Corrections policy · Editorial standards