Malicious Code Injection in vera-miebogor51-breki Package: A Threat to npm Users
Summary
MAL-2025-75979: Malicious code in vera-miebogor51-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 vera-miebogor51-breki package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The primary functionality of this package is to inflate developer reputation scores for token rewards, but it poses significant risks due to its malicious behavior.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the vera-miebogor51-breki package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potential misuse of developer credentials. The ramifications include loss of control over published packages, reputational damage, and the risk of further exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vera-miebogor51-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 vera-miebogor51-breki package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and revert them if necessary.
Conclusion
The vera-miebogor51-breki package poses a significant threat due to its embedded malicious code, which can compromise your project's integrity and security. It is essential to take immediate action by uninstalling the package and monitoring your dependencies for any unauthorized changes. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your open-source projects.
See every vulnerability recorded for vera-miebogor51-breki →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The malicious code modifies your package.json file, removes private flags, and republishes variants, which can lead to unauthorized access and pollution of the npm registry.
You should uninstall the package immediately using 'npm uninstall vera-miebogor51-breki' and check your project for any unauthorized changes.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities without requiring access to the code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
