Entertainment WWC APAC Desk

Major Websites Became a Route for Crypto Theft – What iPhone Users Need to Check

Major Websites Became a Route for Crypto Theft – What iPhone Users Need to Check

A security incident involving website-testing software exposed visitors to malicious code across websites linked to 178 organisations, including major international brands. The code was designed to redirect cryptocurrency payments, capture payment-card information and target vulnerable Apple devices, but the number of people actually compromised has not been established.

The key issue is not that every affected company was hacked internally. Rather, attackers reportedly abused a third-party service used to manage website experiments, creating a route through which harmful scripts could reach visitors. That distinction matters: a website can be familiar and legitimate while one of the external tools it loads becomes a security weakness.

How one software provider became the common entry point

Optimizely’s Web Experimentation platform allows organisations to test website layouts, content and other changes. Websites using the service load a JavaScript snippet that can include customer-specific code, allowing experiments to run on visitors’ pages.

The problem emerged when an unauthorised party gained the ability to modify that custom code in customer projects. Instead of breaking into each organisation’s own servers, the attacker used the shared software service to distribute malicious instructions through scripts that visitors’ browsers were already configured to load.

A technical investigation by Report URI identified 188 affected scripts associated with 178 organisations, after examining 1,611 Optimizely snippets. The organisations included businesses and websites in banking, technology, retail, news, travel and other sectors. The researcher cautioned that the number could be higher because the review covered the scripts the team was able to locate. Report URI Blog+1

This is a supply-chain security problem. A company may maintain its own website carefully, but a third-party script can still introduce risk if that provider’s systems or customer projects are compromised.

The distinction is important. The discovery of malicious code on a website does not, by itself, establish that the organisation’s internal network, customer database or entire IT infrastructure was breached.

What the malicious code was designed to do

The injected JavaScript had several functions, depending on the visitor’s device and activity.

One component searched for cryptocurrency wallet addresses and attempted to replace them with addresses controlled by the attacker. This could redirect a payment even when a user believed they had copied the correct destination from a legitimate website.

Another component targeted payment-card information entered into website forms. Report URI’s technical timeline records that card-skimming functionality was added during the incident on Nov. 16.

The code also sought to collect browser cookies that were accessible to scripts and capture screenshots of pages. Such information can expose sensitive details or help criminals target accounts, although the presence of the code does not prove that every visitor’s information was successfully stolen. Report URI Blog+1

For Apple devices, the malicious code attempted to load additional exploit tools identified by the researcher as Coruna and DarkSword. These were intended to target vulnerable iPhones and iPads.

That does not mean every iPhone that opened an affected website was automatically infected. Exploitation depends on factors such as the device’s operating-system version and whether the relevant security weaknesses remain unpatched.

The incident therefore involved several potential attack paths, not one universal outcome for every visitor.

Optimizely says the vulnerability was fixed

Optimizely acknowledged the incident in its service-status notice dated Nov. 17. The company said an unauthorised party had exploited a vulnerability in its Experimentation service to add malicious JavaScript to some customer projects.

The notice said the vulnerability had been fixed, the injected code removed from affected projects, affected user accounts secured and additional protections introduced to prevent unauthorised code from being delivered. Incident History+1

That response addresses the immediate route used to distribute the scripts. It does not, on its own, answer every question about what happened while the malicious code was active.

Affected organisations still need to determine which pages loaded the scripts, how long visitors were exposed, what information may have been collected and whether any accounts or transactions were affected.

The distinction between removing malicious code and completing an investigation is significant. A clean website today does not automatically establish that no visitor information was accessed yesterday.

The incident also raises a broader question for organisations that rely on external website tools: how much control should a vendor have over code that executes inside a customer’s website?

Why this matters to Filipino users and businesses

The incident did not establish that Philippine websites or Filipino users were among the confirmed victims. But the method is relevant to local businesses that use third-party analytics, advertising, payment, personalisation or website-testing services.

A website’s reputation is not a guarantee that every script loaded by the browser is safe. External services can become part of the website’s effective security perimeter, even when they are not owned or operated by the organisation itself.

The Philippines has its own ongoing data-protection concerns. WWC previously reported on 10 government agencies that notified the National Privacy Commission of data breaches. Those cases are separate from the Optimizely incident, but both underline why organisations must assess not only their own systems but also the services and devices involved in handling information.

Japan has faced a different type of cybersecurity challenge involving research infrastructure. In WWC’s report on the Fugaku supercomputer security incident, the focus was unauthorised access to an internal operational network. The Optimizely case shows a different exposure route: code delivered to visitors through a service embedded in websites.

For ordinary users, the risks also overlap with familiar scams. A compromised or impersonated website can make a fraudulent payment request look convincing. WWC has explained how courier-themed phishing messages can lead users to fake payment pages.

Crypto users face an additional challenge because blockchain transfers are generally difficult to reverse once confirmed. WWC’s previous coverage of the risks surrounding stolen cryptocurrency and exchange security explains why verifying a wallet destination before sending funds is essential.

What users should check now

People who visited affected websites on Nov. 16 should take reasonable precautions, especially if they entered card information or made cryptocurrency transactions during that period.

First, install the latest software update available for the device. Apple’s security-release page lists the latest iOS and iPadOS versions and the devices they support. As of its Nov. 9 update listing, Apple showed iOS 27.2.1 for supported iPhone models, alongside separate releases for older devices. Users should check the update offered for their particular model rather than assume every iPhone can install the same version. Apple Support+1

Second, review bank and card statements for transactions that are unfamiliar. If card details were entered on a website during the exposure period, contact the issuing bank promptly if anything looks suspicious.

Third, review cryptocurrency transactions and verify wallet addresses carefully before sending additional funds. Do not rely solely on an address copied from a webpage or clipboard; compare the destination against a trusted record before confirming a transfer.

Users should also be wary of unsolicited messages offering refunds, recovery services or special security checks. Never disclose wallet recovery phrases, private keys, passwords or one-time verification codes to someone who contacts you unexpectedly.

These steps reduce avoidable risk, but they cannot establish whether a particular device or account was compromised. Anyone who suspects unauthorised access should contact the relevant bank, exchange or service provider through its official support channel.

What happens next

Optimizely has said it fixed the vulnerability and removed the injected code. The remaining questions concern the full scope of exposure, the number of visitors affected and whether the malicious scripts resulted in successful theft of personal or financial information.

The 178 organisations identified by Report URI should not be treated as 178 confirmed cases of customer-data theft. The figure refers to organisations whose Optimizely scripts were found to contain the malicious code.

For website operators, the incident is a reminder to review third-party scripts, restrict what external code can execute and monitor changes to website projects. For users, the practical lesson is to keep devices updated and independently verify sensitive transactions.

The most important security boundary may not be the website address displayed in the browser. It may be the outside services quietly running behind the page.

Frequently asked questions

Were 178 major websites hacked?

Report URI identified malicious scripts associated with 178 organisations using Optimizely Web Experimentation. This does not prove that all 178 organisations suffered internal network breaches or confirmed customer-data theft.

What information could the malicious code collect?

The code was designed to replace cryptocurrency wallet addresses, capture payment-card details entered into certain forms, access some browser cookies and take screenshots.

Were all iPhone users affected?

No. The exploit tools targeted vulnerable Apple operating-system versions. Visiting an affected website does not establish that a device was successfully compromised.

Has Optimizely fixed the security problem?

Optimizely said on Nov. 17 that it had fixed the vulnerability, removed injected code from affected projects, secured affected accounts and added protections against unauthorised code delivery.

What should someone do after visiting an affected website?

Update the device, review card and bank transactions, check cryptocurrency transfers and contact the relevant financial institution if suspicious activity appears. Never share wallet recovery phrases or passwords with unsolicited contacts.

Get our stories first on Google

More in Entertainment

See all in Entertainment