IntroductionOn November 16, 2026, an attacker exploited a vulnerability in Optimizely's Web Experimentation account signup flow. Optimizely is a platform used to create, manage, test, and personalize digital content and websites. The flaw allowed the attacker to edit the Project JavaScript (projectJS) field. Customers use this field to add custom code that runs on pages that load the Optimizely snippet. By abusing this mechanism, the attacker injected malicious JavaScript into customer projects. The code was then delivered to visitors’ browsers through the Optimizely snippets, including snippets served from Optimizely’s content delivery network (CDN).The attack highlights the continued risk posed by third-party script dependencies and software supply chain compromises, particularly when websites rely on trusted third-party platforms to deliver JavaScript that runs in visitors’ browsers.Optimizely reported that it blocked the vulnerable path, deployed a fix, removed the injected code from affected projects, ended active sessions, revoked tokens, reset access for affected accounts, and notified impacted customers.The malicious payload was designed to replace cryptocurrency wallet addresses, skim payment card details, steal cookies, capture page screenshots, and deliver iOS exploits to iPhones and iPads. Organizations using Optimizely, or similar third-party JavaScript platforms, should treat this incident as a reminder to review third-party script governance, monitoring, and browser-side security controls. ThreatLabz ObservationsThreatLabz identified more than 450 unique domains and more than 3,000 URLs serving the malicious script. These findings suggest a broader impact across organizations and industry verticals than previously reported. The affected domains span industries including the following:Airlines and TravelAutomotiveBanking and FinanceE-commerceInsuranceNews and MediaProperty and Real EstateRetail and FashionSmart HomeSportsTechnology and SaaSTelecommunications RecommendationsFor end users who visited affected sitesMonitor bank and credit card statements for suspicious activity.Review cryptocurrency transactions made on or around November 16, 2026.Be cautious of unexpected account activity on sites visited during the incident.Update iOS and iPadOS devices to the latest available security version.Change passwords for accounts used on potentially affected websites, especially if the same credentials are reused elsewhere.For organizations using OptimizelyReview Optimizely project configurationAudit all Project JavaScript fields for unauthorized or unexpected code.Review recent changes, user activity, account creation events, and administrative access.Confirm whether any project snippets were modified during the exposure window.Verify that production pages load only approved versions of Optimizely snippets.Rotate and reset accessReset credentials for affected Optimizely administrative users.Rotate API tokens, session tokens, and integration keys associated with Optimizely.Enforce multi-factor authentication (MFA) for all users with access to experimentation or web personalization platforms.Deploy Content Security Policy (CSP) in enforcement mode where possibleRestrict script execution to approved domains.Limit where pages can send requests and load images and frames using connect-src, img-src, frame-src, and related CSP directives.Use CSP reporting to identify unexpected browser-side activity.Reduce third-party JavaScript riskMaintain an inventory of third-party scripts loaded across websites.Review whether each third-party script is still required.Apply least-privilege principles to third-party tags and tag management platforms.Monitor third-party script changes and unexpected behavior. How It WorksOptimizely Web Experimentation allows site owners to run A/B tests, personalization logic, and other front-end experiments by loading JavaScript on customer websites. The Project JavaScript field is designed to let customers add custom JavaScript that executes on any page that loads the Optimizely snippet.Public reporting indicates that the attacker injected malicious JavaScript into the Project JavaScript field of affected customer projects. The injected code was then delivered through legitimate Optimizely snippets. As a result, when visitors loaded a page with a modified snippet, the injected JavaScript could run in their browsers.Scope of script activity: The observed JavaScript activity is primarily limited to the browser context of the website where the scripts are loaded. The wallet replacement, clipboard manipulation, form monitoring, card-skimming, screen capture, and network-hooking behaviors operate inside the current page, its accessible DOM, same-origin frames, page-initiated requests, and JavaScript-accessible cookies or browser APIs. By design, this JavaScript cannot directly inspect other browser tabs, unrelated websites, other sites’ cookies, local files, or global browser activity. The
[…]
Content was trimmed to protect the source. Please visit the original article for the full text.
This article has been indexed from Security Research | Blog
Related