Malicious Code Injection in lisa-brongkos16-breki: A Threat to npm Users
Summary
MAL-2025-74160: Malicious code in lisa-brongkos16-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 'lisa-brongkos16-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 and republish derivative packages, potentially harming developers' reputations and polluting the npm registry.
Vulnerability Detail
The vulnerability in 'lisa-brongkos16-breki' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the automatic republishing of these variants. This behavior can inflate developer reputation scores fraudulently and compromise the integrity of the npm registry, posing a risk to users who may unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lisa-brongkos16-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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using tools like Vulert, which can alert you to open-source vulnerabilities in real-time without requiring code access. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'lisa-brongkos16-breki' package poses a significant risk due to its malicious code that alters package metadata and repackages itself. It is crucial for developers to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.
See every vulnerability recorded for lisa-brongkos16-breki →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages.
If you have this package installed, it can compromise your project's integrity by modifying your package.json and republishing malicious variants, which can lead to security risks.
You should remove the package immediately and check for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities and alerts you in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
