Malicious Code Injection in lisa-menjes43-breki Package - npm Vulnerability
Summary
MAL-2025-74193: Malicious code in lisa-menjes43-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 lisa-menjes43-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. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the lisa-menjes43-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are often Indonesian-themed. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lisa-menjes43-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, avoid using the lisa-menjes43-breki package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The lisa-menjes43-breki package poses a significant security risk due to its malicious code that alters package metadata and republishing behavior. It is essential for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for lisa-menjes43-breki →
FAQ
The impact includes potential pollution of the npm registry and the risk of using compromised packages that can lead to security breaches in applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If you have used the affected package, uninstall it immediately and check your application for any potential security issues that may have arisen from its use.
While specific exploits have not been detailed, the nature of the malicious code suggests that it could be used to compromise developer environments and inflate reputation scores fraudulently.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the open-source 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.
