test2221 (npm) · Malicious Code
Affects test2221Source GCVE Database
Malicious package : remove test2221 and rotate any secrets on hosts that installed it.
Data as of 5 Aug 2026, 15:39 UTC
Malicious package
Published to npm · OSV MAL-2026-11192
What to do
Remove test2221 from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtest2221 | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f6113dcb20ef051691e0cc0034132b94421604bd16a085229f75aae5c612a3d9) 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. ## Source: ossf-package-analysis (178c9841a69c4a2de3ad248f8d4dbba8f004c8e8947a34f9e6ae12404183e6e2) 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.