Which versions of test_adminet are malicious?

The following npm versions of test_adminet are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate test_adminet if I installed it?

test_adminet 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 test_adminet — how do I know if it already compromised me?

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

Yes — test_adminet is associated with the IN-MAL-2026-010335 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 test_adminet across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for test_adminet (version 99.9.9).

Malicious package

test_adminetnpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

test_adminet is a confirmed malicious npm package (MAL-2026-10509) that steals credentials and exfiltrates sensitive data (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test_adminet (npm)

MAL-2026-10509

Immediate action

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

npm uninstall test_adminet

What this malware does

The package's package.json declares a preinstall hook that runs index.js. On npm install, index.js uses child_process.exec to curl-POST installer identifiers ($(whoami), $(hostname), id output) together with the contents of /etc/passwd, /etc/hosts, and /etc/shadow (base64-encoded and stuffed into the User-Agent header) to a hardcoded webhook.site endpoint. The /etc/shadow read attempts to harvest local password hashes; if the install runs as root (common in CI/Docker), hashes are transmitted off-host. Behavior fires automatically on default npm install with no user interaction.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

e1971734ce6221624b53d3647a5881c1fe0bc7f8ae4d383a5ff2a9f5080da57c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for test_adminet (version 99.9.9).
If you installed it — respond
test_adminet 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 test_adminet 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. test_adminet on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010335

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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