Malicious Code Injection in wawan-mangga31-pore: A Threat to npm Ecosystem
Summary
MAL-2025-98503: Malicious code in wawan-mangga31-pore (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 'wawan-mangga31-pore' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been flooding the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with random names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'wawan-mangga31-pore' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-mangga31-poreIf 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 avoid using the 'wawan-mangga31-pore' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before installation.
Conclusion
The 'wawan-mangga31-pore' package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for wawan-mangga31-pore →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without signup.
You should uninstall the package immediately using 'npm uninstall wawan-mangga31-pore' and replace it with a trusted alternative.
Yes, it can lead to the pollution of the npm registry and compromise the integrity of applications that depend on affected packages.
Regularly audit your dependencies, use trusted sources, and consider using tools like Vulert for real-time monitoring of vulnerabilities.
