Malicious Code Injection in wati-rawon37-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76146: Malicious code in wati-rawon37-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 wati-rawon37-breki is part of the npm ecosystem, which is a popular package manager for JavaScript. 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, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in wati-rawon37-breki arises from its malicious payload that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to compromised developer accounts and a degraded trust in the npm ecosystem, as it artificially inflates the number of packages and can mislead users about the legitimacy of software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wati-rawon37-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 wati-rawon37-breki package and replace it with a secure alternative. Always review the packages you include in your project for any signs of malicious behavior.
Conclusion
The wati-rawon37-breki package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for wati-rawon37-breki →
FAQ
wati-rawon37-breki is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The vulnerability can compromise your project's integrity by introducing malicious code, which may lead to security breaches and loss of trust in your software.
If you have installed wati-rawon37-breki, you should uninstall it immediately using npm uninstall wati-rawon37-breki and review your project for any other potentially harmful packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.
Yes, there are various tools available, including Vulert, that can help you monitor and manage vulnerabilities in your open-source dependencies without requiring code access or installation.
