Malicious Code Injection in npm Package: lisa-klanting35-ruro
Summary
MAL-2025-105225: Malicious code in lisa-klanting35-ruro (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-klanting35-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. The campaign exploits the npm registry by flooding it with packages that contain harmful scripts.
Vulnerability Detail
The vulnerability in 'lisa-klanting35-ruro' originates from its association with the tea.xyz token reward campaign. It includes scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lisa-klanting35-ruroIf 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 and control the versions of your dependencies. Ensure that your project does not include 'lisa-klanting35-ruro' in the package-lock.json file.
Conclusion
The 'lisa-klanting35-ruro' package has been identified as malicious, posing significant risks to developers and applications. It is crucial to remove this package and monitor your dependencies to maintain the security and integrity of your projects.
See every vulnerability recorded for lisa-klanting35-ruro →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising the security of applications that depend on them.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.
No, there is no patch available for this package. The recommended action is to uninstall it from your project.
You should immediately uninstall the package using the command: npm uninstall lisa-klanting35-ruro to mitigate any risks.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
