Malicious Code Injection in wawan-mangut14-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76185: Malicious code in wawan-mangut14-breki (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-mangut14-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing.
Vulnerability Detail
The vulnerability in wawan-mangut14-breki stems from its inclusion in a campaign that deploys malicious code to modify package.json files. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry and potential exploitation of developers' reputations, as well as the risk of introducing further vulnerabilities into dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-mangut14-brekiIf 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-mangut14-breki package altogether. If it is already in use, consider removing it from your dependencies and replacing it with a secure alternative.
Conclusion
The wawan-mangut14-breki package presents a serious vulnerability due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their projects for similar threats to maintain the integrity of their applications.
See every vulnerability recorded for wawan-mangut14-breki →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it under random names, affecting the integrity of the npm registry.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
You should remove the package from your project immediately and check for any secure alternatives to replace its functionality.
While specific exploits have not been detailed, the manipulation of package metadata poses a significant risk to the integrity of the npm ecosystem.
Regularly audit your dependencies, utilize tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
