Malicious Code Injection in wulan-17: A Threat to npm Packages
Summary
MAL-2025-170541: Malicious code in wulan-17 (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 package wulan-17 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, wulan-17 has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in wulan-17 stems from its association with a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security and reliability of applications that depend on these packages. The malicious payload is designed to exploit the npm ecosystem, making it crucial for developers to be aware of this threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wulan-17If 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 remove the wulan-17 package from your project by executing the command: npm uninstall wulan-17. This will prevent any malicious code from executing while you assess alternative packages or wait for a patched version.
Conclusion
The wulan-17 package has been identified as a vector for malicious code injection, posing significant risks to developers and the npm ecosystem. It is crucial to stay informed about such vulnerabilities and take proactive measures to secure your applications.
See every vulnerability recorded for wulan-17 →
FAQ
The vulnerability involves malicious code that modifies package.json files and repackages them, leading to potential security risks.
You can use Vulert, which monitors open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check your application without any signup.
Using the wulan-17 package can lead to security breaches, as it may introduce malicious code into your application, compromising its integrity.
Regularly updating your dependencies and using tools like Vulert to monitor vulnerabilities can help prevent similar issues.
If an immediate update is not possible, consider uninstalling the package and looking for alternative solutions until a patch is available.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
