0x12115b751211…12115b78
Crypto Malware Loaded Through Optimizely Website Scripts
Report URI found one of 188 snippets still infected on Nov. 16. StepSecurity confirmed the loading chain on a GitLab page, raising wallet and card risks.

Outputs
Report URI's last detailed check found one of 188 snippets still infected at 4:52 p.m. ET on Nov. 16.
The earliest identified injection appeared in a BBC script at 11:21 p.m. ET on Nov. 15.
StepSecurity confirmed a consent script, Optimizely file and attacker-script loading chain on a GitLab page.
The malware targeted Bitcoin, Ethereum and other networks through substituted wallet addresses.
Helme recommended credential rotation, transfer checks, card-statement monitoring and iPhone/iPad updates.
By Elena Vasquez
The last detailed check in a Report URI report by researcher Helme found one of 188 snippets still infected at 4:52 p.m. ET on Nov. 16. Helme said cleanup “appeared complete” at 5:49 p.m. ET that day, although the report does not say whether another detailed check confirmed the result.
The researchers’ earliest identified injection appeared in a BBC script at 11:21 p.m. ET on Nov. 15. Individual sites were cleaned at different times the following afternoon, so remediation was staggered rather than simultaneous. That cleanup assessment came less than an hour after the last detailed check.
How did the attacker reach customer scripts?
Optimizely lets website operators test changes by loading vendor-hosted JavaScript into visitors’ browsers. Helme’s analysis found the attacker had altered customers’ Project JavaScript, a field for custom code that runs on every page.
The resulting scripts came from Optimizely’s trusted delivery domain but loaded the attacker’s code. Report URI said this was not a delivery-network cache-poisoning attack, and the path to write access on unrelated customer projects remained unknown.
Until that access path is established, one cleaned snippet cannot prove that other projects or accounts are secure.
What did other researchers confirm?
StepSecurity separately reported confirming the loading chain on a GitLab page. There, a consent-management script loaded an Optimizely file, which then loaded the attacker’s script.
Researcher Amirul Cyber dubbed the campaign OPTIMJACK. Helme said Report URI received no response from Optimizely when it published its findings, so the available research accounts did not include the vendor’s explanation of the compromise.
The confirmed loading chain does not explain how the attacker first gained access.
What could the malware steal or alter?
Both research reports said the malware could replace wallet addresses in several parts of an affected page:
- Page text
- Form fields
- Copied text
- Outgoing web requests
The targets included Bitcoin, Ethereum and other networks. An address copied from an affected page could already point to the attacker when pasted into a wallet.
StepSecurity recommended checking the destination displayed by a wallet or hardware wallet against the address the sender intended to use, rather than checking it against copied text. Helme advised visitors to affected sites on Nov. 16 to review transfers for substituted destinations.
The card-skimming component looked for a card number, expiry date and security code in form submissions and outgoing requests. It could not reach card fields inside a payment provider’s separate, cross-origin frame.
Report URI also reported cookie theft, screenshot theft and an iPhone/iPad exploit-loading component. The campaign put address substitution alongside payment-data collection and device exploit code, but the two research accounts did not quantify losses or victims.
In plain terms, copied addresses and ordinary page fields could not be trusted on affected sites.
What should operators and visitors verify?
Helme advised website operators to review project and experiment code, audit account access and rotate credentials. He warned that searching only for the attacker’s domain could miss versions that hid the address in encoded text or embedded the malicious code directly.
Affected visitors should check transfers, watch card statements, and update iPhones and iPads, according to Helme. Those steps address distinct exposure paths: altered payment destinations, card data in ordinary forms, and device exploit loading.
No remediation deadline was specified in the reports, and the access path remains unknown. A clean webpage does not close the investigation while account access remains unexplained. Operators must therefore continue code audits and credential rotation, while visitors must continue transaction checks until full cleanup is verified.
via cryptonews.net (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,525 articles