LWA-2026-13870 confirmed malware

xhypher-btns@1.0.2

Malicious code in xhypher-btns (npm)

T1027 · Obfuscated Files or InformationT1027.013 · Encrypted/Encoded FileT1059.007 · JavaScript

Analysis

xhypher-btns@1.0.2 ships its entire implementation as an encrypted, self-defending payload that decodes and evals itself at require time. The declared entry point, gifted.js, decrypts a string table using a key derived from its own function source, runs the result through eval, and aborts with "Error: the code has been tampered!" if the decoded text is altered; it then performs two module loads via encrypted names (require(lx2V.JJJR(0)), require(lx2V.FEER(1))) and re-exports them under decrypted property names, so neither the package's dependencies nor its exported API can be read from the manifest or the source. The second bundle, gift.js, uses the same anti-tamper decrypt-and-eval scheme, control-flow flattening, and resolves an additional module with a dynamically built `await import(...)` target taken from the encrypted string table. Although the package presents itself as a Baileys/WhatsApp "send buttons" helper and declares no dependencies, the code it actually runs is hidden, and no plaintext network endpoints, credential paths, or readable API surface exist anywhere in the shipped JavaScript. The decoded payload executes whenever the package is imported — inside the process that holds the Baileys session, including its auth state. No install hook is present, so nothing executes at install time. No network IOC could be recovered from the bytes because the string table is encrypted.

analyzed by
Leitwacht
first seen
Nov 10, 2026, 12:50 AM
analyzed
Nov 10, 2026, 12:51 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.