Malicious Code Injection in lala-poke10: A Threat to npm Packages
Summary
MAL-2025-157932: Malicious code in lala-poke10 (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 'lala-poke10' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code. However, 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. This vulnerability poses a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'lala-poke10' originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lala-poke10If 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 'lala-poke10' and any other packages associated with the tea.xyz campaign. Regularly audit your npm packages using the command 'npm audit' to identify and address vulnerabilities in your project.
Conclusion
The 'lala-poke10' package poses a significant security risk due to its malicious code that modifies package files and floods the npm registry. It is essential to remove this package and monitor your dependencies to maintain the integrity of your applications. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities.
See every vulnerability recorded for lala-poke10 →
FAQ
The main threat is the injection of malicious code that modifies package.json files and floods the npm registry with unwanted packages.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall lala-poke10' and audit your project for other potential vulnerabilities.
Currently, there are no specific patches for lala-poke10, but removing the package is the best course of action.
Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in real-time.
