Malicious Code Injection in vera-mangut2-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75974: Malicious code in vera-mangut2-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 'vera-mangut2-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'vera-mangut2-breki' originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vera-mangut2-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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Additionally, you can use the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The 'vera-mangut2-breki' package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for vera-mangut2-breki →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising applications that depend on them.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
If you have installed 'vera-mangut2-breki', it is crucial to remove it immediately and audit your project for any other vulnerabilities.
As of now, there are no known patches for 'vera-mangut2-breki'. The best course of action is to remove the package and monitor for updates.
Vulert uses your package-lock.json to monitor for vulnerabilities in your dependencies and provides real-time alerts, helping you maintain a secure application.
