Which versions of testing-on-npmjs are malicious?

The following npm versions of testing-on-npmjs are flagged malicious: 2.0.5, 2.0.6. Treat any of these as compromised.

How do I remediate testing-on-npmjs if I installed it?

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

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

Yes — testing-on-npmjs is associated with the IN-MAL-2026-004848, GHSA-4847-p5f9-4366 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 testing-on-npmjs 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 testing-on-npmjs (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testing-on-npmjs across your stack and pipelines.

Malicious package

testing-on-npmjsnpm

Malicious code in testing-on-npmjs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4356

Immediate action

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

npm uninstall testing-on-npmjs

What this malware does

On npm install, postinstall.js executes two attacker-controlled actions automatically. First, it collects installer-side identity (whoami, id, os.hostname(), os.platform(), current working directory) and CI-related environment variables (CI, GITHUB_REPOSITORY, NODE_ENV) and sends them via HTTPS GET to a Burp Collaborator OAST endpoint at qzt3b82juki138pb8n4nwg5f0664uvik.oastify.com (postinstall.js lines 11, 36-43). Second, it opens a TCP socket to the hardcoded address 10.10.10.247:4444 and pipes a /bin/sh (or cmd.exe on Windows) child process's stdio through the socket, granting an interactive remote shell to whoever controls that endpoint (postinstall.js lines 55-63). The package's own README (Takeover By lobo) and description (Security research canary — vercel) confirm the takeover/backdoor intent. Any environment running npm install on this package is fully compromised: identity leaked plus arbitrary remote code execution.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'testing-on-npmjs' @ 2.0.6 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

2.0.52.0.6

Indicators of compromise (SHA-256)

cf253783e300490b93cbf122d395cd50576ce01b2d765f75533242bbe88cff27

1575dee70b1f079b297d26405595aa16591e62de8fac896cf9ea485d6f534132

9aa408e186e92d2311cc7a848056ad9ae5ac9451ef65f586b6f6e70b4c3836e0

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for testing-on-npmjs (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testing-on-npmjs across your stack and pipelines.
If you installed it — respond
testing-on-npmjs 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 testing-on-npmjs 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 testing-on-npmjs 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. testing-on-npmjs on npm has been identified as a malicious package (versions 2.0.5, 2.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004848GHSA-4847-p5f9-4366

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks testing-on-npmjs-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