Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

testingsmthb1gnpm

Advisory published Updated

testingsmthb1g is a confirmed malicious npm package (MAL-2026-14142) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testingsmthb1g (npm)

MAL-2026-14142
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall testingsmthb1g

What this malware does

scripts/postinstall.js runs at npm install and performs an install-time dropper chain. A URL stored as an integer array is XOR-decoded (key 'stf2026') to https://github.com/bebraz1/qPzM50V1AKG0rVlH/releases/download/null/main.exe — a personal GitHub account unrelated to the package publisher, at a random-named repository with a mutable 'null' release tag. On Windows, the script downloads this binary to the TEMP directory and spawns it detached with stdio ignored. On WSL/virtualized Linux, the script detects the environment via /proc/version and WSL_DISTRO_NAME, assembles an XOR-decoded PowerShell command line, and executes it via exec() to fetch and run the same payload on the Windows host, escaping the Linux sandbox. In parallel, the script POSTs a platform label to a hardcoded bare-IP endpoint http://193.70.34.101:20099/vote whose hostname is constructed via split-join to evade string matching. The destination URL, PowerShell command, and shell fragments are all XOR-obfuscated integer arrays reconstructed at runtime.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

04fa6b8b5826315448e5d4f27036ab31ef115621027c040897e200894c43dfa3

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for testingsmthb1g (version 1.0.0).

  2. If you installed it — respond

    Remove testingsmthb1g from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If testingsmthb1g was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. testingsmthb1g on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018196

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks testingsmthb1g-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

testingsmthb1g (npm) malicious package — MAL-2026-14142 | O3 Security