Critical Malicious Code Vulnerability in sandbox-plugin (npm)

sandbox-plugin Updated 02 Oct 2025

Summary

10/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5794: Malicious code in sandbox-plugin (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 Penetration testing for web, API and mobile 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-plugin is an npm package designed to provide a secure environment for executing untrusted code. It is commonly used in applications that require code execution isolation. However, this package has been found to contain embedded malicious code, which poses a significant security risk to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code embedded within the sandbox-plugin package. This code can compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive data, secrets, and keys. The ramifications of this vulnerability are severe, as it can lead to complete system compromise and data breaches.

How To Fix

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

npm uninstall sandbox-plugin

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

Currently, the only effective workaround is to uninstall the sandbox-plugin package. You can do this by running the following command in your terminal: npm uninstall sandbox-plugin. Additionally, ensure that you monitor your system for any signs of compromise.

Conclusion

The sandbox-plugin npm package has been identified as containing malicious code that can compromise systems. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for sandbox-plugin →

Share this vulnerability

FAQ

You should immediately uninstall the sandbox-plugin package and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

As of now, there is no patch available. The recommended action is to uninstall the package until a secure version is released.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall sandbox-plugin

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