Optimjack Supply-Chain Attack Swapped Wallet Addresses on 178 Major Websites

The OPTIMJACK campaign poisoned Optimizely scripts on 178 sites, replacing valid crypto addresses on the clipboard and skimming some payment forms.

7 min read

Researchers disclosed OPTIMJACK on November 16–17, 2026: malicious JavaScript injected into Optimizely-hosted bundles that hit at least 178 organizations, swapping copied cryptocurrency addresses and skimming payment fields on high-traffic sites from news outlets to fintech brands.

Supply-chain mechanism

Amirul Iman named the campaign; Report URI's Scott Helme counted 188 infected snippets among 1,611 checked. Attackers altered Optimizely Web projects so trusted first-party tags served payload from 1688360.cc/track.js. Visitors need not download malware—browsing a compromised page sufficed.

Clipper behavior

The script validates addresses with chain-specific checksums for BTC, ETH, TRX, TON, SOL, LTC, BCH, and DOGE, then replaces them in DOM text, inputs, clipboard APIs, share handlers, and fetch/XHR bodies when nearby text mentions wallets or payments. A user copying an address from CNN or Zoom could paste an attacker wallet into MetaMask or a hardware device unless they verify on-screen.

Card skimming and mobile payloads

Later revisions added card-number, expiry, and CVV capture on first-party checkout fields—excluding many hosted Stripe-style iframes. On iPhones and iPads, reports described secondary loaders tied to exploit-kit routers; vendors stress delivery was observed, not mass confirmed compromise. StepSecurity and others estimated roughly $6,600–$7,100 across attacker wallets—surprisingly small given the blast radius.

Defensive response

Security teams should audit Optimizely bundles for unexpected domains, tighten CSP script-src, and test copy-paste flows on staging with decoy addresses. End users should verify addresses on the signing device, not the browser clipboard. Web3 teams must treat tag managers as critical infrastructure, not marketing accessories.

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Security teams should audit Optimizely bundles for unexpected domains, tighten CSP script-src, and test copy-paste flows on staging with decoy addresses. End users should verify addresses on the signing device, not the browser clipboard. Web3 teams must treat tag managers as critical infrastructure, not marketing accessories.

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Security teams should audit Optimizely bundles for unexpected domains, tighten CSP script-src, and test copy-paste fl

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Fi

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Fi

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Fi

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Fi

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Fi

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Fi

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Fi

Additional context

Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Filings, blog posts, and patch notes often disagree with headline spin within 48 hours. When in doubt, anchor decisions to dated evidence rather than sentiment cycles. Analysts following this story should track primary sources before trading or shipping code on secondary summaries. Fi

More in web3

Cubed

Write about the technologies shaping the future.

For developers, founders, and curious minds exploring AI, crypto, Web3, and emerging tech—signal over noise.

One free account across In Plain English, Stackademic, Venture, and Cubed.

How it works
  • AI, crypto & Web3
  • Software & emerging technologies
  • Analysis & practical resources
  • Thoughtful voices, not hype
1

Sign in

Google or GitHub

2

Complete profile

Takes a few minutes

3

Get approved & publish

Start sharing

Why write for Cubed?

The future deserves thoughtful voices, not just louder headlines.

Comments

Loading comments…

Posts Across the Network