A critical flaw in a popular web-experimentation tool has slashed through major websites, leading to exposure of users’ financial and crypto data. Scripts loaded from Optimizely were hijacked to inject malicious JavaScript into projects owned by over 170 organizations—including CNN, BBC, Zoom, HSBC, and Equifax—allowing attackers to swap crypto wallet addresses, harvest card data, and even deliver iOS exploit kits. Optimizely has since removed the compromised code and mitigated the vulnerability.
How the Attack Unfolded
Optimizely’s Web Experimentation platform allows site operators to embed a snippet of JavaScript on their pages. Each snippet contains project-specific code, including “Project JavaScript,” which runs every time the snippet loads. Attackers gained write access to numerous customer projects—likely due to a flaw in Experimentation—allowing them to insert a loader into those projects without altering the rest of the snippet. The tampered snippets, still served from Optimizely’s CDN and under its certificate, delivered malicious payloads to users hitting those sites. Many sites serving snippets from custom domains were affected too, because the underlying project was compromised.
The malicious campaign involved three loader variants: one that loaded payloads directly from a domain known as 1688360[.]cc, another that hid that host inside base64-encoded code, and a version carrying the payload directly—used when the domain was blocked. The payload, “track.js,” replaces genuine crypto wallet addresses with those belonging to the attacker, even if they’re copied or pasted by users. Additionally, a card skimmer harvested credit card numbers, expiry dates, and CVV from relevant form fields. Sites using cross-origin hosted payment fields (e.g. Stripe or Adyen) were less impacted because the skimmer couldn’t access such enclosed fields.
iOS Exploits, Scope & Response
On iPhones and iPads, an additional stage of attack deployed exploit kits dubbed Coruna and DarkSword. Depending on a victim’s iOS version, a boot script (“boot.js”) loaded exploit chains in hidden iframes. That said, no confirmed device compromises have been documented so far. The iOS kits targeted devices running between versions iOS 13 and 18.6; patches for iOS 18.7.3 and iOS 26.3 appear to block the known exploits.
Within roughly nine hours of activity, attackers diverted approximately US$6,600–7,000 worth of cryptocurrency via the substituted wallet addresses. The exact number of credit cards exposed remains unknown. Affected organizations also included Smartsheet, which reported re-infection of its snippet even after initial remediation, a sign attackers retained access.
Recommendations for Sites & Visitors
Security researchers advise organizations using Optimizely to immediately review all project-level custom JavaScript, especially within experiments. Watch for telltale signs like references to “1688360,” calls to atob( indicating base64 obfuscation, or unexpected script sources. Audit access rights—API tokens, integrations, and user permissions—and rotate credentials. Sensitive form fields should use cross-origin hosted payment tools so that skimmers can’t access card data directly.
End users who visited affected sites on that Monday should take specific precautions: update iPhones and iPads to the latest patched versions (iOS 18.7.3 or iOS 26.3 or newer), monitor card statements, verify crypto payment addresses before sending anything, and consider seeking security review if their device is unpatched. Site owners are urged to scan logs back to early Monday and check script hashes, domains, and modification times for indicators of compromise.
Optimizely issued a security notice confirming the attack, stating that the vulnerability stemmed from Experimentation. The company said it cleaned affected accounts, blocked unauthorized code deliveries, and incorporated additional safeguards. Still, it hasn’t clarified how many projects were altered in total, how the attacker gained write access, or whether all unauthorized access has been eliminated.
This incident—the campaign dubbed by some researchers as “OPTIMJACK”—spans 178 organizations across sectors worldwide. It underscores massive risk in third-party script dependencies, especially in platforms that integrate deeply with customer infrastructure.
Why This Matters & What to Watch
This attack lays bare the threat posed by supply chain vulnerabilities—third-party services like Optimizely are powerful but become attack vectors when control over custom code is compromised. The ability to manipulate script content server-side—and for that code to run in browser contexts across multiple high-profile domains—demonstrates that trust in CDNs and certificate chains can be exploited.
Moving forward, platforms like Optimizely must offer stronger isolation of customer projects, stricter access controls, and more transparency when incidents occur. Organizations should assume that any shared dependency could be compromised and adopt defense-in-depth: zero-trust for scripts, strict content security policies, minimal permissions, and vigilant monitoring. Users handling crypto or performing payments on any site should verify wallet addresses independently and keep devices updated. This breach is a reminder that no corner of your tech stack is too small to secure.