Malicious Code Vulnerability in markdown-nconf-string-xerxes Package
Summary
MAL-2025-187928: Malicious code in markdown-nconf-string-xerxes (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The markdown-nconf-string-xerxes package is a Node.js library designed for handling configuration settings in markdown format. It is part of the npm ecosystem and is often used in applications that require markdown processing. However, this package has been identified as part of a malicious campaign that aims to exploit npm's package publishing system.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that floods npm with malicious packages. It includes scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry and potentially compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall markdown-nconf-string-xerxesIf 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include markdown-nconf-string-xerxes in its dependencies.
Conclusion
The markdown-nconf-string-xerxes package has been identified as a malicious entity within the npm ecosystem, posing significant risks to applications that utilize it. Immediate action is required to mitigate these risks by removing the package and monitoring for any further vulnerabilities.
See every vulnerability recorded for markdown-nconf-string-xerxes →
FAQ
The malicious code modifies package.json to remove private flags and changes version numbers, which can lead to unauthorized package republishing.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed markdown-nconf-string-xerxes, it is crucial to remove it immediately and check for any other dependencies that may be affected.
While specific exploits have not been detailed, the malicious behavior of the package can lead to significant security risks, including unauthorized access to your npm registry.
Regularly monitor your dependencies using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
