Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

box-sign-client-pocnpm

box-sign-client-poc is a confirmed malicious npm package (MAL-2026-15921) 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 box-sign-client-poc (npm)

MAL-2026-15921
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall box-sign-client-poc

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. The script reads the installer's hostname and OS username, embeds them together with a timestamp into a DNS subdomain of the form poc-<hostname>-<user>-<timestamp>.iv6mfybhp42k33ysmzi73de5w.canarytokens.com, and issues a DNS resolution for that name, causing the installer's host and user identifiers to be transmitted to a third-party canarytokens.com collector at install time. The package name and framing indicate a dependency-confusion proof-of-concept targeting a Box-branded internal package, but the exfiltration primitive runs against any machine that installs it.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

cc47a8e8a147ec412ecc05d666655b675a36b9eec0823e278767a286993e7e0d

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for box-sign-client-poc (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 box-sign-client-poc across your stack and pipelines.

  2. If you installed it — respond

    box-sign-client-poc 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.

  3. Did it already run?

    If box-sign-client-poc 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.

  4. How O3 protects you

    O3 blocks box-sign-client-poc 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. box-sign-client-poc 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-019639

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks box-sign-client-poc-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
box-sign-client-poc (npm) malicious package — MAL-2026-15921 | O3 Security