Sunday, November 22, 2026Sun, Nov 22 AboutRSSSubscribe

Awesome B2B

Everything B2B marketing, every day

Martech & AI

Optimizely Breach Exposes Software Supply Chain Vulnerability

Attackers exploited a flaw in Optimizely Web Experimentation, delivering malicious JavaScript to customer websites, according to Forrester. This incident highlights the need for companies to treat marketing technology as part of their software supply chain.

Original reporting · forrester.com

Original: “Optimizely-ing For Trouble: When A Marketing Tool Becomes A Software Supply Chain Attack”

Read “Optimizely-ing For Trouble: When A Marketing Tool Becomes A Software Supply Chain Attack” at Forrester →
Optimizely-ing For Trouble: When A Marketing Tool Becomes A Software Supply Chain Attack
Image: Forrester

How this was written. Awesome B2B wrote this article with a language model from Forrester’s reporting (model: @cf/meta/llama-3.3-70b-instruct-fp8-fast); it describes that reporting rather than adding to it. The original, linked above, is the full story.

Key points from Forrester’s report

  • The Optimizely breach exposed a software supply chain vulnerability, highlighting the need for companies to treat marketing technology as part of their supply chain.
  • CISOs must assess supplier criticality based on what code can be executed and whose customers can be exposed, not just service availability or sensitive data stored.
  • TPRM teams should tier marketing third parties based on blast radius, privileged access, and downstream dependencies, rather than just spend or sensitive data.
  • CMOs must understand where marketing technology touches the customer journey and design campaigns to degrade safely with disabled martech.
  • Digital engineering leaders should extend change governance beyond their own deployments, accounting for third-party code that can change after their application has been reviewed and released.

Marketing teams seeking to improve customer journeys may inadvertently create vulnerabilities, as seen in the Optimizely incident, Forrester reported. The breach turned a website experimentation tool into a delivery channel for malicious JavaScript, exposing a gap between intended experiences and actual code received by customers.

On November 16, attackers exploited a flaw in Optimizely Web Experimentation’s signup flow, allowing them to impersonate administrator users and modify customer Project JavaScript without stealing passwords or compromising an Optimizely administrator account. The malicious scripts targeted payment information and cryptocurrency transactions.

The Optimizely breach shows that even optional services can be consequential for protecting customers, according to Forrester. Chief Information Security Officers (CISOs) must assess not only what data a supplier holds but also what code it can execute and whose customers it can expose. This requires a shared responsibility approach to governing the technology powering customer experiences.

CISOs should require Software Bill of Materials (SBOMs) and software supply chain transparency from suppliers whose technology executes code in sensitive environments. They should also enforce controls, such as Content Security Policy (CSP), to limit the consequences of a supplier compromise. Additionally, webpage integrity and client-side code protection tools can detect changes in trusted scripts and restrict unauthorized access.

Third-party risk management (TPRM) teams need to rethink how they identify and tier marketing third parties, considering factors such as blast radius, privileged access, and downstream dependencies. They should also build containment and exit rights into relationships with suppliers, including emergency suspension and credential revocation.

Chief Marketing Officers (CMOs) must understand where marketing technology touches the customer journey and design campaigns to degrade safely with disabled martech. They should work with digital and security teams to identify which martech capabilities can be temporarily disabled during an incident. Digital engineering leaders should extend change governance beyond their own deployments, accounting for third-party code that can change after their application has been reviewed and released.

The Optimizely breach highlights the importance of limiting when optional scripts run in sensitive interactions. Digital engineering leaders should minimize the duration and authority of code used to optimize high-value interactions, such as checkout and payment pages. They should also monitor the code and behavior delivered to visitors, rather than assuming an approved integration remains unchanged.

Questions and answers

What happened in the Optimizely breach?

Attackers exploited a flaw in Optimizely Web Experimentation’s signup flow, delivering malicious JavaScript to customer websites, according to Forrester.

What can CISOs do to prevent similar breaches?

CISOs should assess supplier criticality, require SBOMs and software supply chain transparency, and enforce controls such as CSP to limit the consequences of a supplier compromise.

How can CMOs mitigate the risk of marketing technology breaches?

CMOs should understand where marketing technology touches the customer journey, design campaigns to degrade safely with disabled martech, and work with digital and security teams to identify which martech capabilities can be temporarily disabled during an incident.

Read the full story at Forrester More from Saturday, November 21, 2026’s edition