Optimjack malware reached web scripts used by Ledger, OANDA / Coinpass and many other organizations through a third-party website service, security researchers report. The November 16 campaign could swap cryptocurrency destination addresses and skim payment-card details. The findings concern browser-side code; they do not establish that Ledger hardware wallets, private keys or recovery phrases were compromised.
What happened in the Optimizely script attack?
In its November 16 investigation, Report URI identified 188 infected Optimizely snippets belonging to 178 organizations. Those are different measures: the research did not establish that exactly 178 individual web pages were affected, nor that every visitor suffered a theft.
Optimizely supplies website experimentation and optimization tools. In this campaign, unauthorized JavaScript appeared in customer-project snippets delivered through its infrastructure. That gave malicious code a route into pages that visitors might otherwise recognize and trust. Report URI said the route by which the attacker obtained permission to change those projects remained unknown; it did not describe the incident as CDN cache poisoning.
StepSecurity’s separate technical analysis corroborated the malicious loader on sampled websites. Its findings support a supply-chain delivery problem, not a conclusion that each affected organization’s entire infrastructure had been taken over.
How could Optimjack redirect a crypto payment?
The inspected payload could replace cryptocurrency addresses in page content and copy-and-paste flows with attacker-controlled destinations. A user could therefore believe they had copied the intended address while preparing a transfer to a different one. The malware also included card-skimming functions aimed at details entered into ordinary forms on the same page.
That does not mean every checkout was equally exposed. StepSecurity distinguished same-page fields from payment fields isolated in a different origin’s iframe, which this skimmer could not directly read. The reports also do not establish how many visitors triggered the malicious functions or how many card records were stolen.
Were Ledger wallets or seed phrases compromised?
The cited research does not demonstrate a hardware-wallet, private-key or recovery-phrase breach. Ledger’s name appears because researchers found an affected website snippet. Browser content and a device’s signing environment are different security boundaries, although a wrong destination address can still create a risk if a user approves it.
The practical check is the intended transaction itself: compare the full destination with a trusted source and inspect the address shown by the wallet or signing device before approval. Do not assume an address is correct solely because it was copied from a familiar website, and do not enter a recovery phrase into a webpage offering an incident-related “fix.”
What is known about cleanup and losses?
Report URI recorded broad cleanup late on November 16. It said Ledger’s snippet was cleaned at about 20:41 UTC and only one of its 188 identified snippets remained infected at its 21:52 UTC check. Those observations describe the researchers’ sample at those times, not a guarantee that all exposure had ended or that previously delivered code had done no harm.
The researchers observed funds in attacker-associated wallets, but the reports do not establish a complete, attributable victim-loss total. Some transfers predated the campaign, and wallet receipts alone cannot identify which visitors were victims. Cointelegraph’s November 17 coverage said it had contacted affected businesses; the version reviewed contained no Ledger or Coinpass response.
Why does third-party access matter for crypto security?
The exposure differs from the Luxor Commander incident that redirected mining work, but both show how a management or delivery layer can affect a financial workflow. The earlier GitBook breach postmortem on exposed access tokens concerns another distinct access path. None should be treated as proof of the others’ root cause.
Visitors concerned about payment details entered during the exposure window should follow their card issuer’s official guidance and monitor for unauthorized activity. A cleaned website is useful remediation evidence, but it cannot answer whether a particular earlier session exposed information. That requires incident-specific investigation rather than a blanket claim that every wallet is either compromised or safe.
