[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fXGmB2ClPhXq7xi-qQzCt5GECTLSJjF_qCC3_pgdrYg8":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},"4c273f0d-a905-429d-9ae0-4598c4150b9a","trusted-third-party-script-turns-178-sites-into-card-stealing-traps","69aedb0f-bb19-4b5f-9e91-028d93414380","Trusted Third-Party Script Turns 178 Sites into Card-Stealing Traps","Attackers compromised the Optimizely Web platform and injected malicious JavaScript that was then automatically delivered to 178 major websites as a trusted third-party resource — no direct breach of those sites was required. The malware stole payment card details, hijacked cryptocurrency transactions, harvested cookies and screenshots, and pushed exploit kits to iPhone visitors. This incident illustrates how a single point of failure in a widely used SaaS or CDN-delivered script can cascade into a massive supply chain attack affecting millions of end users. Organizations that implicitly trust third-party scripts without monitoring their integrity are effectively outsourcing their attack surface. The damage — financial fraud and credential theft at scale — underscores why third-party code must be treated with the same scrutiny as internally written code.","**Immediate actions:**\n- Audit all third-party scripts currently loaded on your web properties and remove any that are not strictly necessary.\n- Implement Subresource Integrity (SRI) hashes on every externally hosted script so browsers reject tampered versions.\n- Deploy a strict Content Security Policy (CSP) that whitelists approved script sources and blocks inline execution.\n\n**Long-term improvements:**\n- Establish a formal third-party vendor risk management programme that includes periodic security assessments of SaaS and CDN providers.\n- Maintain a software bill of materials (SBOM) for all web assets, including external scripts, and review it on a scheduled basis.\n- Contractually require key third-party vendors to notify you of security incidents within a defined SLA.\n\n**Detection measures:**\n- Continuously monitor browser-side telemetry and real-user monitoring (RUM) data for unexpected script behaviour or unusual network calls.\n- Configure web application firewall (WAF) rules and client-side security tooling to alert on new or modified JavaScript payloads from third-party origins.\n- Correlate payment-page anomalies (e.g., unexpected form field submissions to unknown domains) in your SIEM to detect skimming activity early.",[12,13,14,15,16],"NIS2 Article 21(2)(d)","CIS Control 2: Inventory and Control of Software Assets (v8)","NIST SP 800-53 SA-12: Supply Chain Protection","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,"NIST SP 800-53 SA-12: Supply Chain Protection":20,"OWASP A08:2021 Software and Data Integrity Failures":21,"CIS Control 2: Inventory and Control of Software Assets (v8)":22},"This point explicitly requires organisations to manage security risks arising from dependencies on third-party suppliers and service providers, directly addressing the implicit trust placed in the Optimizely platform.","PCI DSS Requirement 6.4 requires organisations to protect web-facing applications and manage the scripts they load, including maintaining an inventory of authorised third-party scripts and monitoring them for unauthorised changes — controls that would have limited payment card theft in this incident.","SA-12 mandates safeguards against supply chain threats, which would have required vetting and monitoring of Optimizely as a critical third-party component delivering code to production environments.","This category covers exactly the failure mode here: loading third-party JavaScript without integrity verification (SRI), allowing tampered scripts to execute in users' browsers without detection.","CIS Control 2 requires organisations to actively track all authorised software, including third-party scripts loaded on web properties, so that unauthorised or tampered code can be detected and blocked.","published","2026-11-17T02:20:42.500242+00:00","2026-11-17T02:20:42.468+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fcybersecuritynews.com\u002Foptimizely-websites-hijacked\u002F","hackers-infect-178-major-websites-via-optimizely-to-steal-credit-cards-and-targe-6d6b82","Hackers Infect 178 Major Websites via Optimizely to Steal Credit Cards and Target iPhones",[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},"security-monitoring-siem","Security monitoring (SIEM)","Logs from everywhere end up in one place, with alerts that someone actually sees.",{"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},"third-party-risk-management","Third-party risk management (TPRM)","You know which suppliers could hurt you, and you hear quickly when one of them is breached."]