A recent cyberattack dubbed OPTIMJACK has compromised visitors of prominent websites through malicious JavaScript designed to intercept cryptocurrency wallet addresses and payment information. The attack was identified on November 16, 2026, when third-party scripts on trusted sites allowed harmful code to infiltrate web browsers.
Websites Affected by OPTIMJACK
Evidence of the malicious script was captured during visits to CNN and Zoom. However, while Salesforce, Fox News, and Fox Sports were listed among affected sites, specific evidence for these websites has not been independently verified, leaving open questions about breaches in their systems.
Researchers from Cynet discovered the attack through alerts from endpoint detection systems, which flagged unusual browser connections. Their findings, published on November 17, highlighted the attack’s potential for financial theft and its selective device targeting, although they noted that successful data theft or system compromise has not been confirmed.
Technical Analysis of the Attack
The investigators connected suspicious endpoint alerts with browsing histories, ultimately tracing the malicious code to a JavaScript resource hosted by Optimizely. This resource was found to embed additional scripts into web pages, a method reminiscent of previous ad-script abuses like the Adform case. However, the exact cause of OPTIMJACK’s initial entry remains unknown, as it is unclear whether it involved account compromise, tag setting alterations, or another form of integration abuse.
The main script reportedly included features to replace wallet addresses in web content or clipboard interactions, posing a risk of redirecting payments if users unwittingly accepted changed payment details. The attack also involved collecting payment form data, potentially exposing card details externally, though evidence of successful theft is lacking.
Preventive Measures and Security Implications
Researchers noted that the attack’s behavior mirrors that of JavaScript skimmer attacks, which harvest financial information via scripts embedded in web pages. Although Cynet reported possible data collection methods like cookie capture and HTML rendering, these capabilities are limited by browser permissions, leaving certain data like HttpOnly cookies and desktop access unaffected.
The investigation highlighted the necessity for website operators to review third-party dependencies and configurations to mitigate risks. Responders are advised to correlate DNS and endpoint records with browser activity to discern between blocked and executed scripts. A follow-up check did not find the malicious scripts, but this does not assure their complete eradication.
To stay secure, users and organizations should keep browsers and systems updated and respond based on concrete exposure evidence rather than domain alerts. The case underscores the critical need for ongoing vigilance against sophisticated cyber threats exploiting trusted web platforms.
