Malicious Code Injection in wawan-bakwan65-breki Package
Summary
MAL-2025-76164: Malicious code in wawan-bakwan65-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 wawan-bakwan65-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity.
Vulnerability Detail
The vulnerability in the wawan-bakwan65-breki package stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-bakwan65-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 measure, you can avoid using the wawan-bakwan65-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The wawan-bakwan65-breki package poses a significant risk due to its malicious code that alters project files and repopulates the npm registry with compromised packages. It is crucial to remove this package from your projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.
See every vulnerability recorded for wawan-bakwan65-breki →
FAQ
It is an npm package associated with a token reward campaign that has been identified as malicious.
The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your project's integrity.
You should remove the wawan-bakwan65-breki package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
