Critical Malicious Code Vulnerability in sandbox-hooks Package

sandbox-hooks Updated 02 Feb 2026

Summary

27/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-525: Malicious code in sandbox-hooks (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The sandbox-hooks package is a Node.js library designed to facilitate the creation of sandboxed environments for executing untrusted code. It is commonly used in applications that require isolation for security purposes. However, this package has been found to contain malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the sandbox-hooks package. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected computer. The malicious nature of the code is classified under CWE-506, which indicates that the product contains embedded malicious code. Users are advised to treat any system running this package as fully compromised.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall sandbox-hooks

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There are no effective workarounds for this vulnerability other than removing the package and securing the system. It is crucial to ensure that the system is thoroughly checked for any remaining malicious software after the package is removed.

Conclusion

The discovery of malicious code within the sandbox-hooks package poses a significant security risk to any system using it. Immediate action is required to remove the package and secure the system. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their software dependencies.

See every vulnerability recorded for sandbox-hooks →

Share this vulnerability

FAQ

Immediately remove the sandbox-hooks package and rotate any secrets or keys stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to sensitive information and potential control over your system by malicious actors.

After removing the malicious package, it is crucial to rotate all secrets and keys and perform a thorough security audit of your system.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to their latest versions.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall sandbox-hooks

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback