HSBC
Incident posture
Timeline
Summary
HSBC was among 178 organizations whose websites served malware after attackers exploited a vulnerability in a digital experience platform to inject malicious JavaScript into customer projects. The tampered code, delivered through a trusted content delivery network, could swap cryptocurrency wallet addresses, skim payment card details, and collect cookies and screenshots, while also serving iOS exploit kits to iPhone and iPad users. Roughly $7,000 in cryptocurrency reached the attacker before the vulnerability was patched and the injected code was removed.
Motives
Detailed motive labels are available to members.
TTPs
Detailed technique labels are available to members.
Description
On November 13, security researchers observed scripts from Kissmetrics, StorifyMe and Minute-ly serving a small loader that led to iOS-targeting infrastructure, though it remained unclear how the code entered those providers' scripts. The Optimizely-specific timeline began on November 16 at 04:21 UTC, when Report URI recorded the first injection of malicious JavaScript into Optimizely customer projects. Optimizely later confirmed that an unauthorized party exploited a vulnerability in its Experimentation product to add malicious code to some customer projects, affecting organizations that use Web Experimentation. Report URI investigated the incident by examining 1,611 Optimizely scripts and identified 188 infected scripts belonging to 178 organizations, with HSBC among the names on the list alongside the BBC, CNN, Zoom, GitLab, Salesforce, Equifax and IKEA. The malicious code was inserted into an optional field intended for a customer's own JavaScript, meaning it executed on every page of the affected websites. Because the tampered files originated from Optimizely's content delivery network, visitor browsers treated them as trusted resources. By 21:52 UTC, Report URI indicated that only one of the infected scripts had yet to be cleaned. Optimizely disclosed the incident in a status page update posted early on November 17 and in a post on X, stating that it had fixed the vulnerability and removed the injected code from affected projects.
The malware embedded in the compromised scripts was capable of swapping cryptocurrency wallet addresses for the attacker's own, skimming payment card details, and collecting cookies and screenshots of affected pages. Report URI stated that by Monday evening roughly $7,000 in cryptocurrency had reached the attacker. Users of iPhone and iPad devices were served the Coruna and DarkSword iOS exploit kits through the malicious infrastructure. Hudson Rock confirmed links between the attack and the exploit-kit delivery infrastructure but noted that successful exploitation had not been demonstrated, and the available evidence did not establish a zero-day, successful device exploitation, or collection of specific device data by unseen downstream stages. Some of the poisoned Optimizely scripts contained a full version of the payload embedded within them, allowing the code to run even if the remote file failed to load. For HSBC and the other affected organizations, the compromise occurred through a third-party dependency without any breach of the organizations' own code or infrastructure.
In response, Optimizely stated that it had taken steps to secure affected user accounts and introduced additional protections, though the company did not disclose how many customers were impacted. Report URI's investigation provided the primary public accounting of the scope, identifying the 178 organizations and 188 infected scripts. The company also referenced a separate incident disclosed in February, when a threat actor accessed its systems through a voice-phishing attack, though that event was distinct from the November compromise. No further details were provided regarding the identity of the unauthorized party or the specific method used to exploit the Experimentation vulnerability beyond the initial unauthorized access.
Sources
Sources available to members: 1 source.