Malicious code in n-sandbox (npm)

n-sandbox Updated 02 Oct 2025

Summary

12/10/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8341: Malicious code in n-sandbox (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The n-sandbox package is an npm package that provides a sandbox environment for executing untrusted code. It is commonly used in applications that require running user-generated code in a secure manner. However, the package has been found to contain malicious code that compromises the security of the host system.

Vulnerability Detail

The malicious code in the n-sandbox package poses a significant security risk to any computer that has it installed or running. It is advised to consider such computers as fully compromised, and all secrets and keys stored on them should be rotated immediately from a different computer. Removing the package may not guarantee the removal of all malicious software resulting from its installation, as full control of the computer may have been given to an outside entity.

How To Fix

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

npm uninstall n-sandbox

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 is no specific workaround mentioned for this vulnerability. The recommended course of action is to remove the n-sandbox package and follow the steps outlined in the 'how_to_fix' section.

Conclusion

The presence of malicious code in the n-sandbox package poses a severe security risk to any computer that has it installed or running. It is crucial to take immediate action by removing the package, rotating secrets and keys, and conducting a thorough security audit. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for n-sandbox →

Share this vulnerability

FAQ

The n-sandbox package is an npm package that provides a sandbox environment for executing untrusted code securely.

The malicious code compromises the security of the host system, giving full control to an outside entity. All secrets and keys stored on the affected computer should be rotated immediately.

If you have the n-sandbox package installed, it is recommended to remove it from your computer and rotate all secrets and keys stored on the machine from a different, trusted computer.

Removing the n-sandbox package may not guarantee the removal of all malicious software resulting from its installation. A thorough security audit is advised to identify and mitigate any potential damage.

After removing the n-sandbox package, it is crucial to rotate all secrets and keys stored on the affected computer from a different, trusted machine. Additionally, performing a security audit is recommended to identify and address any potential vulnerabilities.

How To Fix

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

npm uninstall n-sandbox

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