Malicious Code Vulnerability in vera-brongkos65-breki Package
Summary
MAL-2025-75951: Malicious code in vera-brongkos65-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The vera-brongkos65-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that alters package metadata.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the vera-brongkos65-breki package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially harming developers' reputations. The malicious code is part of a broader scheme to exploit the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vera-brongkos65-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 the vulnerable package by using npm's package-lock.json to lock dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json for any known issues.
Conclusion
The vera-brongkos65-breki package contains a serious vulnerability due to malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your project for vulnerabilities using tools like Vulert to ensure ongoing security.
See every vulnerability recorded for vera-brongkos65-breki →
FAQ
The vera-brongkos65-breki package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The malicious code modifies your package.json file, potentially exposing your project to security risks and harming your developer reputation by flooding the npm registry with unwanted packages.
You should immediately remove the vera-brongkos65-breki package from your project and monitor for any updates or patches that may address the vulnerability.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
