SlowMist Finds Data-Stealing and Address-Swapping Code in Udesk Scripts

SECURITY FLAWSlowMist Finds Data-Stealingand Address-Swapping Code inUdesk Scripts39IMPORTANCEACTIVE2NEWS MEDIA2PIECESOct 27, 2026 10:28blockboard.net

Published Updated 1 new report since it was first published

SlowMist identified malicious JavaScript in Udesk’s customer-service chat widget that collected visitor login data and altered crypto deposit addresses on trading sites. The code was found in routine threat-intelligence work and was reported to affect at least three trading sites.

What this rests on

Claim by claim, with its source
✓
The payload could change both the address shown on screen and the address copied by a user.
✓
The data collection in the payload went beyond three site-specific targeting rules.
✓
SlowMist said JavaScript tied to Udesk’s chat widget collected visitors’ login data.
✓
SlowMist said the same script replaced crypto deposit addresses on at least three trading sites.

What it means

Udesk is a customer-service chat widget that websites embed on their pages, and this case sits at the point where third-party site tools become part of a crypto user’s security surface. SlowMist published its analysis after spotting the code during routine threat-intelligence work, which places the finding in the everyday supply chain of website software rather than in a single exchange or wallet app. For crypto users, that means the trust boundary can extend to ordinary support widgets that sit on a trading site’s page.

The immediate practical impact is on deposit flows at trading sites, where a changed address can send funds to the wrong destination if a user does not catch the substitution. Site operators that embed Udesk would have to review what their pages load and how deposit addresses are rendered and copied. Users would need to treat the address field itself as something that can be manipulated at the interface level, not just in the clipboard. (per thedefiant.io)

This case shows how a small snippet of front-end code can sit between a user and a crypto transfer, which is a direct tension with the idea that users can verify destinations for themselves. The fact that the payload also gathered data beyond the three targeted sites raises the risk that one embedded script can reach beyond a narrow set of victims. That makes third-party web tooling a security and governance problem for exchanges and other trading platforms, not just a browser issue.

Still open is where the compromised code entered Udesk’s distribution path, how many websites loaded it, and whether all affected operators removed it at the same time. It is also not yet clear from these details whether any deposits were actually redirected or only that the code had that capability. SlowMist’s disclosure establishes the presence of the script, but the scope of real-world harm remains unsettled.

Market reaction

TO Total crypto market no single asset in the event: read against the whole market from 2 h before to 4 h after the line marks the first headline
published
-0.40 % before publication
+1.50 % after
$2.7Tmarket cap at publication
12series points

How the story was built

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Oct 27 10:27
+4 h 10 m
Oct 27 14:37
Unchained context
Its angle: intelligence, hexadecimal, udeskqlobal; with quotes