Malicious Code Injection in wulan-32 Package - npm Vulnerability
Summary
MAL-2025-170557: Malicious code in wulan-32 (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 wulan-32 package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the wulan-32 package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is part of a broader scheme to create numerous derivative packages that clutter the npm registry, potentially leading to security risks and reputation damage for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wulan-32If 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-32 package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The wulan-32 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial to uninstall this package and monitor your project for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for wulan-32 →
FAQ
The wulan-32 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package publishing.
The malicious code modifies your package.json file, removing private flags and generating numerous derivative packages, which can lead to security vulnerabilities and clutter in the npm registry.
You should uninstall the wulan-32 package immediately using the command npm uninstall wulan-32 to mitigate any potential risks.
Yes, you should look for alternative packages that provide similar functionality but are verified and do not have a history of malicious behavior.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.
