Malicious Code Detected in boxless Package - Security Alert

boxless Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16046: Malicious code in boxless (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 boxless package is an npm library designed for developers to facilitate various functionalities in their applications. It is commonly used for its lightweight nature and ease of integration. However, recent findings have revealed that the package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the boxless package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this code was identified by security researchers, highlighting the importance of scrutinizing third-party packages before integration.

How To Fix

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

npm uninstall boxless

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 may consider removing the boxless package from your project until a secure version is released. You can do this by executing: npm uninstall boxless. Additionally, consider using alternative packages that provide similar functionality without the security risks.

Conclusion

The discovery of malicious code in the boxless package underscores the importance of vigilance when using third-party libraries. Users are encouraged to update to a patched version or consider alternative solutions to mitigate security risks. Utilizing tools like Vulert can further enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for boxless →

Share this vulnerability

FAQ

The boxless package is an npm library used by developers for various functionalities in their applications.

The malicious code found in the boxless package can lead to unauthorized access and potential data breaches.

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 any signup.

If you cannot update the package right away, consider uninstalling it and using alternative packages until a secure version is available.

Regularly check for updates from package maintainers and utilize tools like Vulert to monitor vulnerabilities in your dependencies.

How To Fix

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

npm uninstall boxless

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