Malicious Code Detected in boxedin Package - Vulnerability Overview

boxedin Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16044: Malicious code in boxedin (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 boxedin package is a JavaScript library available on npm, primarily used for creating isolated environments for executing code securely. It is designed to provide developers with a controlled execution context, preventing unauthorized access to the global scope. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the boxedin package stems from the presence of malicious code that can compromise the integrity and security of applications using this library. This code can potentially lead to unauthorized data access, data manipulation, or even remote code execution, depending on how the package is integrated into the application. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall boxedin

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

As a temporary workaround, you can avoid using the boxedin package altogether and look for alternative libraries that provide similar functionality without the associated risks. Additionally, you can implement security measures such as input validation and output encoding to mitigate potential threats from malicious code.

Conclusion

The discovery of malicious code in the boxedin package highlights the importance of regularly reviewing and updating dependencies in software projects. Developers are urged to take immediate action to remove the affected package and consider secure alternatives to ensure the safety of their applications.

See every vulnerability recorded for boxedin →

Share this vulnerability

FAQ

The boxedin package is a JavaScript library used for creating isolated execution environments for code.

The malicious code can lead to unauthorized data access, data manipulation, or remote code execution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

You should remove the boxedin package and replace it with a secure alternative. If a patched version is available, update it using npm update boxedin.

Yes, there are several alternatives available that provide similar functionality without the security risks. Research and select a library that meets your needs.

How To Fix

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

npm uninstall boxedin

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