nodepack-daemonnpm
nodepack-daemon is a confirmed malicious npm package (MAL-2026-10111) that opens a backdoor for remote access (malicious version 1.2.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nodepack-daemon (npm)
What this malware does
The package presents itself as the popular pino logger (README badges, file layout mirroring pino's lib/proto.js, lib/redaction.js, lib/transport.js, DEFAULT_LEVELS, and module.exports.pino = middleware), but on use it triggers a remote code execution flow. index.js spawns node./lib/caller.js in a detached, stdio-ignored child when the exported middleware is invoked. lib/caller.js issues an HTTPS GET against https://jsonkeeper.com/b/QWPQX, reads the cookie field of the returned JSON, and passes it to Function.constructor('require', s), invoking the returned function with the real require — giving whatever code the paste currently contains full Node capabilities inside the installer's process. The exfil/C2 URLs are further obfuscated as base64-encoded fake process.env.DEV_API_KEY / DEV_SECRET_KEY / DEV_SECRET_VALUE constants in lib/caller.js and lib/const.js that decode to additional jsonkeeper.com paste endpoints (https://jsonkeeper.com/b/XRGF3, https://jsonkeeper.com/b/4NAKK) and a custom x-secret-key header. jsonkeeper.com is an anonymous, mutable paste host — the executed payload can be swapped by the operator at any time without a package update. Name impersonation of pino plus a mutable-paste remote-execute channel plus URL obfuscation is an unambiguous supply-chain attack.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nodepack-daemon (version 1.2.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nodepack-daemon across your stack and pipelines.
If you installed it — respond
nodepack-daemon establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If nodepack-daemon 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 nodepack-daemon 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks nodepack-daemon-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.