Which versions of test-in-one are malicious?

The following npm versions of test-in-one are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate test-in-one if I installed it?

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

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

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

Malicious package

test-in-onenpm

test-in-one is a confirmed malicious npm package (MAL-2026-15562) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-in-one (npm)

MAL-2026-15562

Immediate action

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

npm uninstall test-in-one

What this malware does

The package declares a local file: dependency (detector at file:.yalc/detector) whose postinstall script (src/scripts/check.js) executes automatically on npm install. The script walks the installer's home directory, Desktop, Documents, Projects, and cwd to harvest desktop crypto-wallet directories, browser extension LevelDB stores (MetaMask, Phantom, and similar), ~/.ssh/* private keys, ~/.aws/credentials, ~/.git-credentials, .env*, .npmrc/.yarnrc, and the full process.env. The collected files are tarred and POSTed to a hardcoded Telegram Bot API endpoint (https://api.telegram.org/bot<redacted>/sendDocument, chat_id 416517694). The script additionally contains npm worm scaffolding: after collecting an npm token it calls whoami against registry.npmjs.org, enumerates all packages owned by the maintainer via the registry search API, and for each package downloads the tarball, injects a postinstall hook, bumps the version, writes a .npmrc with the stolen token, and prepares publication (the final publish call is currently gated by if (false), but token theft, maintainer enumeration, and the injector pipeline are live). Bundling the payload as a file: dependency causes npm to install and run its lifecycle hooks without a registry fetch, making the manifest itself the delivery vector.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4834c80d92d51ee12f73395ddc87c681baf4f911c6bbec54a9110cc55a9c4ae9

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 test-in-one (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-in-one across your stack and pipelines.
If you installed it — respond
test-in-one 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-in-one 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 test-in-one 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. test-in-one on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019128

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test-in-one-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