HSBC UAE Optimizely website-script compromise

Malicious Optimizely project code was associated with HSBC UAE’s listed web properties on November 16, 2026. The evidence separates website exposure, cleanup observations and confirmed consequences.

Last modified

Summary

  • Environment: Website JavaScript on www.hsbc.ae
  • Operational impact: Observed website-script exposure; service downtime is not established
  • Financial impact: Visitor-level losses for this organization remain unquantified
  • Record status: Developing record. Reviewed November 17, 2026; updated as evidence emerges.

What happened

On November 16, 2026, malicious code in Optimizely website-experimentation scripts was associated with HSBC UAE. Report URI’s investigation lists www.hsbc.ae in its banking & finance inventory. [4]

This is the HSBC UAE entry and its named regional web properties. The inventory does not establish exposure across every country site, mobile application or authenticated customer journey operated by the wider brand. [4]

The supplier later identified a vulnerability in its Experimentation account signup flow. Attackers used that path to add JavaScript to customer projects. Report URI found 188 poisoned snippets across 178 named entries in its sample of 1,611; those are script and inventory counts, rather than a count of affected visitors. [2] [4]

Impact

  • The shared wallet-substitution module could change validated cryptocurrency destinations in accessible page content, clipboard activity and browser requests. Whether a visitor lost funds depended on what the page displayed and what the visitor subsequently did. [1]
  • The card module sought a valid card number, expiry and security code in accessible forms and outgoing requests. Payment fields isolated inside a cross-origin provider frame were outside that module’s reach. The reviewed material does not identify the payment-field design of every affected HSBC UAE page. [1]
  • Cookie and screenshot collection was conditional on an address swap. It could include a page image, original addresses, the page URL and JavaScript-readable cookies; HttpOnly cookies were outside document.cookie access. [1]
  • Apple mobile user agents could trigger additional exploit-kit loading. A recorded script or HTTP response does not prove a successful device infection. Counts of stolen cards, affected sessions, compromised devices and losses attributable to HSBC UAE remain unquantified. [1] [4]

Timeline

  1. Researcher records clean snippet

    Report URI’s affected-host table marked the observed HSBC UAE snippet entry clean at its 21:52 UTC checkpoint on November 16. Research timeline.

    [4]
  2. Observed Optimizely set is clean

    Report URI’s November 17 follow-up says every poisoned file in its observed Optimizely set had been clean since 23:11 UTC on November 16. This does not give an individual cached-page clearance time. Research timeline.

    [4]
  3. Optimizely confirms remediation

    The provider’s incident notice confirms that it fixed the vulnerability, removed injected code, secured affected accounts and added protections against unauthorized delivery. Incident notice.

    [3]
  4. Briefing updated

    This briefing was last reviewed and updated on November 17, 2026.

Threat Group & Attack Vector

Optimizely’s signup-flow flaw supplied the disclosed access path. The public statement does not explain the code-level bug or how the path permitted changes across unrelated projects. Report URI located the injection in the customer-controlled Project JavaScript field: the normal experiment code stayed present, and trusted delivery served the modified content. [2] [4]

Hudson Rock independently recovered the poisoned Optimizely asset cdn.optimizely.com/js/20350660683.js associated with HSBC UAE. Its sample report preserves SHA-256 295f2ff6b934e7be8c07d501b0561a9a7da29e0fa775b742613a6edb0d0b6069 for that specific version; a later clean file at the same URL would have different bytes. [5]

Hudson Rock decoded an identical 24,392-byte embedded financial payload from the BBC and HSBC UAE project files. The loader attempted that local copy if the remote script failed or took about 2.5 seconds. Blocking the remote hostname alone could therefore leave address-substitution code available, subject to browser execution policy. [5]

The campaign used several loader forms, including an explicit remote URL, a Base64-encoded URL and—in some projects—an embedded fallback copy. Those variants explain why a simple search for one external hostname could miss affected project content. The reviewed evidence does not identify the variant used on every HSBC UAE page. [4]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

Response

Report URI’s affected-host table marked the observed HSBC UAE snippet entry clean at its 21:52 UTC checkpoint on November 16. The checkpoint concerns the fetched snippet; already-open pages and cached copies have no published clearance time. [4]

Optimizely said it closed the vulnerable path, removed the injection, ended active sessions, revoked tokens, reset affected account access and notified affected customers. Those measures concerned affected Optimizely accounts; downstream visitor sessions required their own exposure assessment. [2]

StepSecurity reported the main payload domain on registry hold at 00:37 UTC on November 17. Optimizely’s 01:02 UTC notice confirmed its remediation. Those shared containment milestones do not resolve HSBC UAE’s individual visitor exposure or prove that previously collected information was recovered. [1] [3]

The public material reviewed for this briefing did not provide an additional HSBC UAE incident statement, a visitor notification count or a quantified loss assessment.