Malicious Code Detected in domainbox Package - Security Alert

domainbox Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18620: Malicious code in domainbox (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 domainbox package is an npm library designed for domain management and related functionalities. It is widely used in web development for tasks such as domain registration and DNS management. 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 domainbox package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access, data breaches, or other harmful actions that can severely impact users and systems. The malicious nature of this code was identified by Amazon Inspector, highlighting the importance of vigilance in package management.

How To Fix

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

npm uninstall domainbox

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 measure, consider removing the domainbox package from your project until a secure version is confirmed. You can do this by executing: 'npm uninstall domainbox'. This will help mitigate any immediate risks associated with the malicious code.

Conclusion

The discovery of malicious code in the domainbox package underscores the importance of maintaining secure dependencies in software development. It is essential to regularly monitor and update packages to protect applications from potential vulnerabilities. Utilizing tools like Vulert can aid in identifying and managing these risks effectively.

See every vulnerability recorded for domainbox →

Share this vulnerability

FAQ

The domainbox package is used for domain management tasks, including domain registration and DNS management in web applications.

The malicious code was discovered by Amazon Inspector, which identified security risks associated with the domainbox package.

Using the compromised domainbox package can lead to unauthorized access, data breaches, and other harmful actions that may affect your application and its users.

Yes, you can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner without any signup.

If you cannot update the package immediately, consider removing it from your project as a temporary workaround to mitigate risks until a secure version is available.

How To Fix

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

npm uninstall domainbox

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