LWA-2026-13755 confirmed malware

jmrwd-gjdob-util@1.0.1

Malicious code in jmrwd-gjdob-util (npm)

T1059.007 · JavaScriptT1027 · Obfuscated Files or InformationT1140 · Deobfuscate/Decode Files or Information

Analysis

Three names — jmrwd-gjdob-util@1.0.1, smfos-bskdz-util@1.0.1 and tsbwt-hawsi-util@1.0.1 — ship an entry point that decodes a script hidden in package.json and executes it. jmrwd-gjdob-util and smfos-bskdz-util read a numeric byte array from the package.json key "_b", XOR each byte with 0x96, and run the decoded source through the Function constructor: jmrwd-gjdob-util stores the decoded text on globalThis.__rc and executes it from lib/runner.js via (function(){}).constructor('require','__dirname',globalThis.__rc)(require,__dirname), then deletes it; smfos-bskdz-util decodes and executes it inline in index.js. tsbwt-hawsi-util reads the key "_bz", inflates the bytes with zlib.inflateSync and executes the result the same way. None of the packages defines a lifecycle hook, so the decoder runs whenever the entry point is required — including transitively as a dependency. In these builds the encoded body decodes to the single statement console.log(1), a placeholder for a second-stage payload. No C2 host, IP address, callback URL, environment variable or credential file appears in any of the three packages.

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.