Malicious Code Vulnerability in lisa-semur62-breki: npm Package Exploitation
Summary
MAL-2025-74210: Malicious code in lisa-semur62-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-semur62-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 package metadata and inflate developer reputation scores, posing significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'lisa-semur62-breki' originates from its inclusion in a malicious campaign that deploys autopublish scripts. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The ramifications include potential exposure to further malicious code and degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lisa-semur62-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 'lisa-semur62-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'lisa-semur62-breki' package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for lisa-semur62-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should immediately uninstall the 'lisa-semur62-breki' package and check your project for any other potentially malicious dependencies.
Yes, regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you to issues in real-time without requiring code access.
You can find detailed information about this vulnerability in the official vulnerability report or by using monitoring tools like Vulert.
