Which versions of test-pkg-pnpm are malicious?

The following npm versions of test-pkg-pnpm are flagged malicious: 1.0.1, 1.0.4. Treat any of these as compromised.

How do I remediate test-pkg-pnpm if I installed it?

Remove test-pkg-pnpm from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed test-pkg-pnpm — how do I know if it already compromised me?

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

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

Malicious package

test-pkg-pnpmnpm

Malicious code in test-pkg-pnpm (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6716

Immediate action

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

npm uninstall test-pkg-pnpm

What this malware does

On npm install, the package's postinstall script (node demo-clean.js) auto-executes two installer-side actions without consent. First, openDemo() platform-branches via execSync to open https://github.com/X3r0Day/BunnyHijack in the installer's default browser and to spawn the OS calculator (calc on Windows, open -a Calculator on macOS, gnome-calculator/kcalc on Linux) — the canonical calc.exe proof of unauthenticated code execution on the installer's host. Second, cleanup() walks every ancestor directory of INIT_CWD, process.cwd(), and the user's home directory, calling fs.rmSync(..., {recursive:true, force:true}) against paths inside each ancestor's node_modules, node_modules/.pnpm, node_modules/.bin/node* shims, ~/.npm/_npx, ~/.bun/install/cache, and tmpdir entries; cleanupPackageJson() then reads each ancestor package.json and rewrites it via fs.writeFileSync after deleting matching entries from dependencies, devDependencies, optionalDependencies, and peerDependencies. The destructive recursive-force-rm operates well outside the package's own directory and reaches the user's home tree, and the spawned-process primitive can be retargeted to any binary in a future release.

Malicious versions

2 flagged

1.0.11.0.4

Indicators of compromise (SHA-256)

8ee6a2ba8d90a67199eae146b7688190adb974ce5aa1be7c07d56e2e3999d270

ae5df84cbdf3092d5f7b8f405248144eacdf5119c756c97726974e547810ebec

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for test-pkg-pnpm (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-pkg-pnpm across your stack and pipelines.
If you installed it — respond
Remove test-pkg-pnpm from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If test-pkg-pnpm 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-pkg-pnpm 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-pkg-pnpm on npm has been identified as a malicious package (versions 1.0.1, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007894IN-MAL-2026-007893

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test-pkg-pnpm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring