Malicious Code Injection in wati-brongkos61-breki Package
Summary
MAL-2025-76109: Malicious code in wati-brongkos61-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 wati-brongkos61-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata.
Vulnerability Detail
The vulnerability in the wati-brongkos61-breki package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to continuously republish variants with randomized names, thereby polluting the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes developers to inflate their reputation scores through such deceptive practices. The ramifications include potential security risks for developers who unknowingly use these packages, as they may introduce vulnerabilities into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wati-brongkos61-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-brongkos61-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package dependencies for any updates or vulnerabilities.
Conclusion
The wati-brongkos61-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the security of their applications.
See every vulnerability recorded for wati-brongkos61-breki →
FAQ
The wati-brongkos61-breki package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
Using the wati-brongkos61-breki package can introduce security risks, as it modifies package metadata and republish variants that may contain malicious code.
You should uninstall the wati-brongkos61-breki package immediately using the command: npm uninstall wati-brongkos61-breki.
Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file.
You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without needing to sign up.
