Which versions of sandbox-hooks are malicious?

The following npm versions of sandbox-hooks are flagged malicious: 0.0.1-security, 1.0.0, 99.0.0. Treat any of these as compromised.

How do I remediate sandbox-hooks if I installed it?

Remove sandbox-hooks 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 sandbox-hooks — how do I know if it already compromised me?

If sandbox-hooks 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 sandbox-hooks part of a known attack campaign?

Yes — sandbox-hooks is associated with the GHSA-58gm-9gr2-v55v, RLMA-2026-01546 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 sandbox-hooks 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 sandbox-hooks (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sandbox-hooks across your stack and pipelines.

Malicious package

sandbox-hooksnpm

Malicious code in sandbox-hooks (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-525

Immediate action

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

npm uninstall sandbox-hooks

What this malware does

The package sandbox-hooks was found to contain malicious code.

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

3 flagged

0.0.1-security1.0.099.0.0

Indicators of compromise (SHA-256)

7d12de65eeb03f7f648a293f5f7217cce1215878610d2bf4f973cd510733eedb

de188418d12a5397810d78eeeb5b8e939a4fc430f8c2aa3113e7fa3a5360e2c8

bec3bbb9325a46e9db5fb14452aceca5e505f7f9feb8727515f11b3149717a24

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

Campaign

GHSA-58gm-9gr2-v55vRLMA-2026-01546

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sandbox-hooks-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