Which versions of testingsmthb1g are malicious?

The following npm versions of testingsmthb1g are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate testingsmthb1g if I installed it?

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.

I already installed testingsmthb1g — how do I know if it already compromised me?

If testingsmthb1g was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is testingsmthb1g part of a known attack campaign?

Yes — testingsmthb1g is associated with the IN-MAL-2026-018196 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find testingsmthb1g across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for testingsmthb1g (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testingsmthb1g across your stack and pipelines.

Malicious package

testingsmthb1gnpm

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for testingsmthb1g (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testingsmthb1g across your stack and pipelines.
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.
Did it already run?
If testingsmthb1g was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks testingsmthb1g before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database