[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ftR69-MFa8Dd5OVaFLsFGGsOkMmy4XTaFQhnPVWMloJw":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":44},"ef6693eb-bfa9-4aca-8494-7342a6f4f0a2","malicious-scripts-served-via-trusted-cdn-steal-crypto-and-card-data-from-186-sites","70b4c0ab-c465-41d3-925e-7dbbf9f6a0b5","Malicious Scripts Served via Trusted CDN Steal Crypto and Card Data from 186 Sites","The OPTIMJACK campaign demonstrates how attackers exploit the implicit trust placed in third-party content delivery networks by injecting malicious JavaScript that is then served to end users as if it were legitimate content. Website operators loaded scripts through Optimizely's CDN without adequately verifying the integrity of what was being delivered, allowing a crypto clipper and card skimmer to silently harvest sensitive data. This matters because a single compromised or abused third-party script can instantly affect hundreds of sites and millions of users, with victims having no visible warning. The attack also shows adversaries chaining delivery mechanisms—using .icu domains for a second-stage mobile payload—to maximize reach and evade simple domain-based blocking.","**Immediate actions:**\n- Audit all third-party scripts currently loaded on your site and verify their source URLs against expected, documented values\n- Implement Subresource Integrity (SRI) hashes on every externally hosted script tag so browsers reject tampered content\n- Review Content Security Policy (CSP) headers and restrict `script-src` to explicitly allowlisted origins only\n\n**Long-term improvements:**\n- Establish a formal third-party vendor review process that includes periodic re-evaluation of CDN and tag management providers\n- Maintain a living inventory of all external JavaScript dependencies and monitor them for unexpected changes\n- Adopt a client-side security monitoring solution that detects anomalous script behaviour or exfiltration attempts in real time\n\n**Detection measures:**\n- Deploy website integrity monitoring tools that alert on new or modified script tags appearing in page source\n- Monitor outbound network traffic from browsers (via CSP violation reports) for connections to unrecognised domains such as .icu or newly registered TLDs\n- Implement server-side logging of all CDN resource loads and alert on deviations from baseline script inventories",[12,13,14,15,16],"CIS Control 2: Inventory and Control of Software Assets (v8)","CIS Control 16: Application Software Security (v8)","NIS2 Article 21(2)(d)","OWASP A08:2021 Software and Data Integrity Failures","PCI DSS Requirement 6.4",{"NIS2 Article 21(2)(d)":18,"PCI DSS Requirement 6.4":19,"CIS Control 16: Application Software Security (v8)":20,"OWASP A08:2021 Software and Data Integrity Failures":21,"CIS Control 2: Inventory and Control of Software Assets (v8)":22},"This point requires security measures addressing risks arising from supplier and third-party relationships; the incident stems directly from insufficient vetting and monitoring of a CDN provider's delivered content.","PCI DSS Requirement 6.4 mandates that payment page web applications protect against skimming attacks by managing all scripts loaded in the consumer browser, directly addressing the card-skimming component of OPTIMJACK.","This control calls for securing web-facing applications by validating the integrity of included components; using Subresource Integrity checks on Optimizely-served scripts would have prevented the tampered JavaScript from executing.","This category covers failures to verify the integrity of software and data from external sources; loading CDN-hosted scripts without SRI hashes is a textbook example of the integrity failure OWASP A08 is designed to prevent.","This control requires maintaining an inventory of all software, including third-party scripts; had operators catalogued and monitored their CDN-loaded scripts, the introduction of the malicious payload from 1688360[.]cc could have been detected.","published","2026-11-17T00:20:45.296319+00:00","2026-11-17T00:20:45.262+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.stepsecurity.io\u002Fblog\u002Foptimjack-optimizely-hosted-scripts-crypto-clipper-card-skimmer","optimjack-optimizely-hosted-scripts-loaded-a-crypto-clipper-and-card-skimmer-on-6ad14a","OPTIMJACK: Optimizely-Hosted Scripts Loaded a Crypto Clipper and Card Skimmer on 186 Confirmed Sites",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"c8b843a5-d5a7-41d1-8d3b-cabded09d2ef","Data Protection","data-protection","Unencrypted data, missing DLP, poor classification","#3b82f6",{"id":38,"name":39,"slug":40,"description":41,"color":42},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[],[45,49,53],{"slug":46,"name":47,"problem":48},"dns-web-filtering","DNS filtering and secure web gateway","Users cannot reach known-malicious sites, and malware cannot phone home.",{"slug":50,"name":51,"problem":52},"data-loss-prevention","Data loss prevention (DLP)","Sensitive data cannot quietly leave by email, upload, USB stick or AI tool.",{"slug":54,"name":55,"problem":56},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship."]