CSIDB logo
Incident

GitLab

Incident posture

Attack window
Nov 2026
Location
United States of America
Status
Unknown
CIA posture
Available to members
Updated
2026-11-19 01:22

Linked entities

Victim
GitLab
Threat actors
0 actors
Sources
2 sources

Timeline

Occurred
Pending
Discovered
Pending
Disclosed
Pending
Resolved
Pending

Summary

An unauthorized party exploited a vulnerability in a digital experience platform's experimentation feature to inject malicious JavaScript into customer projects, affecting numerous major organizations including GitLab. The malicious code, delivered through a trusted content delivery network, could swap cryptocurrency wallet addresses, skim payment card details, collect cookies and screenshots, and serve iOS exploit kits to iPhone and iPad users. The platform patched the vulnerability, removed the injected code, secured affected accounts, and introduced additional protections, though the total number of impacted customers was not disclosed.

Motives

Detailed motive labels are available to members.

0 motives

TTPs

Detailed technique labels are available to members.

0 techniques

Description

On November 16 at 04:21 UTC, Report URI recorded the first Optimizely injection in its timeline, marking the start of a campaign in which an unauthorized party exploited a vulnerability in Optimizely Experimentation to add malicious JavaScript to some customer projects. The malicious code was placed in an optional field intended for a customer’s own JavaScript, which executes on every page, and the tampered files were served from Optimizely’s content delivery network, causing visitor browsers to treat them as trusted. Report URI examined 1,611 Optimizely scripts and identified 188 infected ones belonging to 178 organizations, including GitLab, the BBC, CNN, Zoom, Salesforce, Equifax, HSBC, and IKEA. Optimizely confirmed the incident in a status page update posted early on November 17 and in a post on X, stating that some Web Experimentation customers were affected. By 21:52 UTC on November 16, only one of the infected scripts had yet to be cleaned. The company said it had fixed the vulnerability and removed the injected code from affected projects, while also taking steps to secure affected user accounts and introducing additional protections. Optimizely did not disclose how many customers were impacted. The broader intrusion also involved scripts from Kissmetrics, StorifyMe, and Minute-ly serving a small loader that led to the same iOS-targeting infrastructure, with the earliest of these observations dating to November 13, though it remained unclear how the code entered those providers’ scripts. In a separate disclosure, Optimizely noted a February incident in which a threat actor accessed its systems through a voice-phishing attack. The supported conclusion from investigators was a connection to exploit-kit delivery infrastructure, though the evidence did not establish a zero-day, successful device exploitation, or collection of specific device data by unseen downstream stages.

The malware deployed through the compromised Optimizely scripts could swap cryptocurrency wallet addresses for the attacker’s own, skim payment card details, and collect cookies and screenshots of affected pages. By Monday evening, roughly $7,000 in cryptocurrency had reached the attacker, according to Report URI. iPhone and iPad users were served the Coruna and DarkSword iOS exploit kits, and Hudson Rock confirmed links to the exploit-kit infrastructure. Hudson Rock noted that successful exploitation had not been demonstrated. Some of the poisoned Optimizely scripts contained a full version of the payload embedded within them, meaning the code could run even if the remote file failed to load.

Sources

Sources available to members: 2 sources.

CSIDB