Critical Malicious Code Vulnerability in domain-name Package

domain-name Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18619: Malicious code in domain-name (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 domain-name package is a widely used npm library that facilitates the parsing and manipulation of domain names. It is designed to help developers handle domain-related tasks efficiently. However, this package has been found to contain malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the domain-name 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, and other severe ramifications for users and systems. The issue was identified in all versions starting from its introduction, making it critical for developers to address it promptly.

How To Fix

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

npm uninstall domain-name

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, consider removing the domain-name package from your project until a secure version is available. You can do this by executing: npm uninstall domain-name. Alternatively, you may explore other packages that provide similar functionality without the associated risks.

Conclusion

The domain-name package has been identified as containing malicious code, which poses a serious threat to applications that utilize it. Developers are urged to update the package to the latest version or consider alternative solutions to mitigate risks. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for domain-name →

Share this vulnerability

FAQ

The domain-name package is an npm library used for parsing and manipulating domain names, helping developers manage domain-related tasks.

The malicious code can lead to unauthorized access and data breaches, posing significant security risks to applications using the package.

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

Yes, updating to the latest version of the domain-name package will address the vulnerability. Use the command 'npm update domain-name' to apply the fix.

If immediate updates are not possible, consider uninstalling the domain-name package or using alternative libraries that do not have known vulnerabilities.

How To Fix

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

npm uninstall domain-name

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