Malicious Code Injection in keyla-poke52: A Threat to npm Ecosystem
Summary
MAL-2025-157621: Malicious code in keyla-poke52 (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
keyla-poke52 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify essential files and republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in keyla-poke52 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to manipulate package.json files. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to the proliferation of harmful packages in the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these packages into their projects, as well as the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall keyla-poke52If 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 keyla-poke52 package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The keyla-poke52 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package files and inflate developer reputation scores. It is crucial for developers to remove this package from their projects and monitor for any dependencies that may have included it. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.
See every vulnerability recorded for keyla-poke52 →
FAQ
keyla-poke52 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The malicious code can modify your package.json file, remove private flags, and republish variants, potentially leading to security vulnerabilities.
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.
You should uninstall the package immediately using 'npm uninstall keyla-poke52' and check for any dependencies that may rely on it.
Yes, you should look for reputable packages that provide similar functionality without the associated risks of keyla-poke52.
