Malicious Code Injection in wati-rangi38-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76144: Malicious code in wati-rangi38-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-rangi38-breki' 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 and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits the npm registry, leading to the proliferation of harmful packages that can compromise developer reputations and project integrity.
Vulnerability Detail
The vulnerability in 'wati-rangi38-breki' originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly incorporate these malicious packages into their projects, potentially leading to security breaches and loss of control over their code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wati-rangi38-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 remove the 'wati-rangi38-breki' package from your project by executing the following command: 'npm uninstall wati-rangi38-breki'. This will help mitigate the risk until a patched version is available.
Conclusion
The 'wati-rangi38-breki' package poses a significant risk due to its malicious code that alters package.json files and floods the npm registry. It is essential for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for wati-rangi38-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with harmful derivative packages.
You can use tools like Vulert to check your package-lock.json for vulnerabilities without needing to install any software.
Using this package can lead to security breaches, loss of control over your code, and damage to your developer reputation due to the proliferation of malicious packages.
Regularly updating your dependencies, using vulnerability monitoring tools like Vulert, and conducting security audits can help prevent such vulnerabilities.
You should uninstall the package immediately and check for any other affected dependencies. Consider using a vulnerability monitoring tool to stay informed.
