Malicious Code Injection in wulan-31: A Threat to npm Packages
Summary
MAL-2025-170556: Malicious code in wulan-31 (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
Background
The package wulan-31 is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies and streamline development processes. However, wulan-31 has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and the integrity of the registry itself.
Vulnerability Detail
The vulnerability in wulan-31 originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wulan-31If 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, you can avoid using the wulan-31 package and any packages that may have been derived from it. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The wulan-31 package poses a significant threat due to its malicious code that alters project files and floods the npm registry. It is crucial for developers to be vigilant, remove compromised packages, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for wulan-31 →
FAQ
The main risk is that it modifies your package.json file and floods the npm registry with malicious variants, which can harm your project's integrity and reputation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the wulan-31 vulnerability without needing to sign up.
If you have used the wulan-31 package, you should uninstall it immediately and audit your project for any other potentially compromised packages.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
To prevent similar vulnerabilities, regularly update your dependencies, use trusted packages, and conduct security audits on your project.
