Which versions of test2221 are malicious?

The following npm versions of test2221 are flagged malicious: 2.2.3, 2.2.4, 2.2.6. Treat any of these as compromised.

How do I remediate test2221 if I installed it?

test2221 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If test2221 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 test2221 part of a known attack campaign?

Yes — test2221 is associated with the IN-MAL-2026-011087, IN-MAL-2026-014942, IN-MAL-2026-014934 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 test2221 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 test2221 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test2221 across your stack and pipelines.

Malicious package

test2221npm

test2221 is a confirmed malicious npm package (MAL-2026-11192) that opens a backdoor for remote access (malicious versions 2.2.3, 2.2.4, 2.2.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test2221 (npm)

MAL-2026-11192

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall test2221

What this malware does

package.json declares preinstall and postinstall lifecycle scripts that run curl against http://54.37.234.136/voicemail over plain HTTP, sending the installer's username (whoami), hostname, working directory, and a timestamp as query-string parameters. Both hooks fire automatically on npm install, transmitting installer host identifiers to a hardcoded bare-IP endpoint with no relation to any documented package purpose. The behavior matches reconnaissance-beacon shape suitable for follow-on targeting of the installer's host.

The OpenSSF Package Analysis project identified 'test2221' @ 2.2.4 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

2.2.32.2.42.2.6

Indicators of compromise (SHA-256)

178c9841a69c4a2de3ad248f8d4dbba8f004c8e8947a34f9e6ae12404183e6e2

38741fd8a6f3ffcff6a34fbe07df84f5694996ca108b575078937d43906353d2

310867cf8d300cc2e3c9b9744cd9c4eb7df1b6ff855ee38e108e793fe556cbef

f6113dcb20ef051691e0cc0034132b94421604bd16a085229f75aae5c612a3d9

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for test2221 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test2221 across your stack and pipelines.
If you installed it — respond
test2221 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If test2221 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 test2221 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. test2221 on npm has been identified as a malicious package (versions 2.2.3, 2.2.4, 2.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011087IN-MAL-2026-014942IN-MAL-2026-014934

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks test2221-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database