Malicious Code Injection in vera-lapis2-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75970: Malicious code in vera-lapis2-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-lapis2-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 aims to exploit the npm registry by generating and publishing numerous derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'vera-lapis2-breki' originates from its association with the tea.xyz token reward campaign, which has led to the proliferation of malicious packages in the npm registry. The malicious code embedded in this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to a polluted npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to further exploitation or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vera-lapis2-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 measure, avoid using the 'vera-lapis2-breki' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'vera-lapis2-breki' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to take immediate action by removing the package and ensuring their dependencies are secure. Utilizing tools like Vulert can help in monitoring for vulnerabilities in real-time.
See every vulnerability recorded for vera-lapis2-breki →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry by publishing numerous derivative packages with altered metadata.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall vera-lapis2-breki' and update your dependencies.
Yes, using this package can lead to the pollution of the npm registry and potential exploitation of your application, which may compromise security.
Regularly audit your dependencies, stay informed about known vulnerabilities, and use tools like Vulert to monitor your projects for open-source vulnerabilities.
