LWA-2026-13760 confirmed malware

tsbwt-hawsi-util@1.0.0

Malicious code in tsbwt-hawsi-util (npm)

Analysis

This package is a placeholder member of a five-name set (nuadg-jhtvh-util, vcnwi-ihpgp-util, jmrwd-gjdob-util, tsbwt-hawsi-util, smfos-bskdz-util) that shares a single structure across all names. The 1.0.0 versions of these names — the ones covered here — contain only a 35-byte index.js that exports an empty object, with no scripts, no dependencies and no encoded payload, so nothing executes on install or require. Sibling versions in the same set are staged loaders: jmrwd-gjdob-util@1.0.1 and smfos-bskdz-util@1.0.1 read a numeric byte array stored in package.json under the key "_b", XOR it with 0x96, and execute the decoded source with (function(){}).constructor('require','__dirname',source)(require,__dirname); jmrwd-gjdob-util additionally stores the decoded string on globalThis.__rc and executes it from lib/runner.js. tsbwt-hawsi-util@1.0.1 stores a zlib-compressed byte array under the key "_bz", inflates it with zlib.inflateSync and executes the result the same way. In these builds the decoded body is the single statement console.log(1), i.e. a placeholder for a second-stage payload. There is no lifecycle hook; the loader runs whenever the package entry point is required, including transitively. No C2 host, IP address, callback URL or credential access appears in any version examined.

analyzed by
Leitwacht
first seen
Nov 9, 2026, 01:20 AM
analyzed
Nov 9, 2026, 01:22 AM

Related advisories

browse all confirmed advisories →

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.