Malicious Code Injection in wati-mieaceh71-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76135: Malicious code in wati-mieaceh71-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-mieaceh71-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. The primary functionality of such packages is to inflate developer reputation scores through the automatic generation and publication of derivative packages, often with randomized names.
Vulnerability Detail
The vulnerability in wati-mieaceh71-breki stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wati-mieaceh71-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, avoid using the wati-mieaceh71-breki package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The wati-mieaceh71-breki package poses a significant risk due to its malicious behavior of modifying project files and republishing variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for wati-mieaceh71-breki →
FAQ
The main risk is that it modifies your project's package.json file, potentially leading to the installation of other malicious packages and compromising your project's integrity.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By uploading your package-lock.json file to the Vulert playground, you can quickly check for any vulnerabilities without needing to sign up.
If you have installed the wati-mieaceh71-breki package, you should uninstall it immediately using 'npm uninstall wati-mieaceh71-breki' and review your other dependencies for potential vulnerabilities.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your project's dependencies.
Regularly audit your dependencies, keep them updated, and use trusted sources for package installations to minimize the risk of vulnerabilities.
