Malicious Code Injection in vera-lapis53-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75972: Malicious code in vera-lapis53-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-lapis53-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in 'vera-lapis53-breki' stems from its malicious payload that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vera-lapis53-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-lapis53-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes in the package.json file.
Conclusion
The 'vera-lapis53-breki' package poses a significant threat due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects remain secure. Immediate action should be taken to remove this package and monitor for any unauthorized changes.
See every vulnerability recorded for vera-lapis53-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.
You should uninstall the package immediately and look for alternatives. Run 'npm uninstall vera-lapis53-breki' to remove it.
Yes, using this package can lead to compromised project integrity, security risks, and potential damage to your developer reputation.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
