NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

test22221npm

Advisory published Updated

test22221 is a confirmed malicious npm package (MAL-2026-12478) that executes malicious code on install (malicious versions 2.2.7, 2.2.8, 2.2.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test22221 (npm)

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

What this malware does

package.json declares preinstall and postinstall lifecycle hooks that run on npm install. Both hooks curl a hardcoded bare-IP endpoint over plain HTTP at 54.37.234.136, sending the installer's username (whoami), hostname, current working directory, and a timestamp as query-string parameters to http://54.37.234.136/voicemail. The same lifecycle scripts also embed an unbounded for((i=1;;i++)) loop that repeatedly curls incrementing paths on the same host with a 10-second sleep, functioning as a long-poll channel to the attacker-controlled endpoint during install. The destination is a bare IP with no relationship to any package publisher domain, and the collected fields are host-identification data with no legitimate purpose in an install hook.

Malicious versions

3 flagged
2.2.72.2.82.2.9

Indicators of compromise (SHA-256)

a44fe0c6ead0b2a6bb04d0b5e3b533495b68798d43c99f3ba0de9f7602687f66
e3cbc7d139320187d95a6264959f8d4a2a6688fa6140bc8bc43e2fba0110914f
e4a3401759b5c6d7effdafcbae6027657e3cf8f9aabf1f04dfc2fa9039b64e53
f0b1d9a9ac9b91da2ebc8f000a9c724a1380ba91a85620c64353193370c20689

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for test22221 (3 malicious versions).

  2. If you installed it — respond

    Remove test22221 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 test22221 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. test22221 on npm has been identified as a malicious package (versions 2.2.7, 2.2.8, 2.2.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014868IN-MAL-2026-014752IN-MAL-2026-014744RLMA-2026-10797

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks test22221-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

test22221 (npm) malicious package — MAL-2026-12478 | O3 Security