Malicious Code Injection in wulan-34: A Threat to npm Ecosystem
Summary
MAL-2025-170559: Malicious code in wulan-34 (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-34 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and distribution of JavaScript applications. However, wulan-34 has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This behavior not only undermines the integrity of the npm ecosystem but also poses significant risks to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in wulan-34 originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants. This can lead to developers inadvertently using compromised packages, which may contain harmful code or lead to reputation damage for legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wulan-34If 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 wulan-34 and any packages that are known to be associated with the tea.xyz campaign. Regularly check your package-lock.json file for any unauthorized changes and remove any suspicious packages immediately.
Conclusion
The wulan-34 package poses a significant threat to the npm ecosystem due to its malicious behavior of flooding the registry with compromised packages. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from potential security risks.
See every vulnerability recorded for wulan-34 →
FAQ
Wulan-34 is an npm package that has been identified as part of a malicious campaign to flood the npm registry with compromised packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising your application's security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
You should immediately uninstall the wulan-34 package using 'npm uninstall wulan-34' and review your other dependencies for any potential vulnerabilities.
Yes, tools like Vulert can help monitor your project for vulnerabilities by analyzing your package-lock.json file.
