Malicious Code Injection in vera-oblok30-breki: A Threat to npm Packages
Summary
MAL-2025-75983: Malicious code in vera-oblok30-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-oblok30-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, aimed at inflating 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 in 'vera-oblok30-breki' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags and changing version numbers, which allows the package to continuously republish variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vera-oblok30-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 workaround, you can avoid using the 'vera-oblok30-breki' package entirely and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall vera-oblok30-breki.
Conclusion
The 'vera-oblok30-breki' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.
See every vulnerability recorded for vera-oblok30-breki →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected.
You should immediately uninstall the 'vera-oblok30-breki' package and check for any alternative packages that do not pose security risks.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Using compromised packages can lead to security breaches, data leaks, and unauthorized access to your application, which can have severe implications for your users and business.
