The Media Trust observed the campaign before its expansion through Optimizely. Our Threat Intelligence Brief examines the attack, its delivery paths, and what businesses should check.
A website does not have to suffer a direct breach to deliver malicious code to its visitors. Hydra-Cart demonstrated how attackers can exploit third-party scripts to introduce payment theft, cryptocurrency diversion, and targeted mobile payloads into otherwise routine browsing sessions.
The Media Trust’s Malware Desk first observed the attack on November 13, 2026, before its delivery through Optimizely-hosted JavaScript on November 16. Early observations involved other website integrations and third-party scripts. The subsequent Optimizely phase substantially expanded the campaign’s distribution as businesses prepared for Black Friday and holiday shopping.
The incident has implications for publishers, retailers, Commerce Media networks, AdTech platforms, and other businesses that depend on third-party code to support their digital experiences.
An attack that preceded Optimizely
The Media Trust’s investigation identified and blocklisted infrastructure associated with the campaign before the Optimizely delivery phase. Early activity appeared through multiple delivery paths, with Kissmetrics-related scripts frequently present in the integrations investigated by our Malware Desk.
That sequence matters. Treating Hydra-Cart solely as an Optimizely incident would overlook earlier exposure and other distribution routes. Businesses assessing their potential exposure should account for activity preceding November 16 and examine relevant third-party integrations beyond a single provider.
One injected bundle, four theft paths
The code analyzed by The Media Trust combined several malicious capabilities:
- Payment card skimming: Capturing card details entered into accessible fields on affected pages.
- Cryptocurrency address swapping: Replacing intended wallet destinations with attacker-controlled addresses.
- Session theft: Collecting JavaScript-accessible cookies, including a Hootsuite-specific stealer in an earlier variant.
- Targeted iOS delivery: Identifying Apple mobile visitors and selecting additional payloads based on their operating system version.
The Malware Desk also identified explicit
DarkSword references and infrastructure similarities to previously documented activity, making the mobile delivery chain a significant part of the investigation.
Not every visitor encountered every capability. The behavior depended on the payload variant, device, page content, and visitor activity. However, a purchase or ad click was not required for the mobile loader to run. Exposure could begin when an affected page loaded.
Why a trusted provider is not enough
Third-party scripts support analytics, personalization, experimentation, and other functions that businesses use every day. Their reach also creates opportunities for attackers: a change to a shared dependency can introduce malicious behavior across many unrelated properties.
Hydra-Cart illustrates the limits of evaluating a script primarily by its source. A recognized domain and an established vendor relationship cannot establish that every subsequent version of the code will behave as expected.
For businesses, the consequences extend beyond the immediate security investigation. Payment theft can disrupt transactions and create response costs. Exposed sessions can put customer accounts at risk. Malicious activity on a publisher’s pages can damage audience trust, regardless of where the code originated. Protecting those relationships requires visibility into what executes in the visitor’s browser, what additional content it retrieves, and where it sends information.
What businesses should examine
The Malware Desk reports that the delivery activity described in its investigation has since been shut down. Historical exposure still warrants review. Security and web operations teams should establish which integrations and pages delivered affected code, and during what period. Checkout, sign-in, subscription, account, and cryptocurrency-related pages deserve particular attention.
Teams should preserve relevant evidence, investigate potentially exposed sessions, and involve payment security specialists where checkout flows were affected. They should also review monitoring for unexpected script changes, new dependencies, outbound connections, and hidden frames.
The Media Trust continues to investigate additional payloads and the extent of potential data exposure, sharing verified findings and indicators as the analysis progresses.
Get the Hydra-Cart Threat Intelligence Brief
Our brief brings together The Media Trust’s detection timeline, an explanation of the attack’s components, code excerpts supplied by the Malware Desk, and practical guidance for assessing exposure.