Malicious Code Injection in wawan-menjes33-breki Package
Summary
MAL-2025-76188: Malicious code in wawan-menjes33-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-menjes33-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-menjes33-breki package originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in security risks for developers who unknowingly use these compromised packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-menjes33-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, avoid using the wawan-menjes33-breki package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
Conclusion
The wawan-menjes33-breki package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for wawan-menjes33-breki →
FAQ
It is an npm package associated with a token reward campaign that has been identified as containing malicious code.
The malicious code can modify your package.json file, remove private flags, and publish derivative packages, potentially compromising your project's security.
You should uninstall the wawan-menjes33-breki package immediately and monitor your project for any further vulnerabilities.
Yes, you can use Vulert's playground to check if your application is affected by this vulnerability without any signup.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions to mitigate risks.
