Which versions of box-sign-client-poc are malicious?

The following npm versions of box-sign-client-poc are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate box-sign-client-poc if I installed it?

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.

I already installed box-sign-client-poc — how do I know if it already compromised me?

If box-sign-client-poc was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is box-sign-client-poc part of a known attack campaign?

Yes — box-sign-client-poc is associated with the IN-MAL-2026-019639 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 box-sign-client-poc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for box-sign-client-poc (version 1.0.0).

Malicious package

box-sign-client-pocnpm

Advisory published Sep 4, 2026Updated Sep 4, 2026

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

Find it
Search your lockfiles and build artifacts for box-sign-client-poc (version 1.0.0).
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.
Did it already run?
If box-sign-client-poc was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

npmjs.com

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