Malicious Code Injection in ocha-lapis3-breki: A Threat to npm Packages
Summary
MAL-2025-74695: Malicious code in ocha-lapis3-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
ocha-lapis3-breki is an npm package that is part of a broader ecosystem of packages often associated with token reward campaigns. These packages are typically designed to automate the generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the tea protocol token rewards. The package's functionality is compromised by malicious scripts that alter package metadata and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in ocha-lapis3-breki originates from its association with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. The malicious payload embedded within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the package but also poses a risk of reputation damage to developers and potential security threats to users who unknowingly install these variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ocha-lapis3-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, you can avoid using the ocha-lapis3-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities without requiring code access or installation.
Conclusion
The ocha-lapis3-breki package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is essential to remove this package and monitor your project for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for ocha-lapis3-breki →
FAQ
ocha-lapis3-breki is an npm package that is part of a campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security.
You should uninstall the package immediately and monitor your project for any further vulnerabilities.
You can use Vulert to monitor and alert you for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
