Malicious Code Injection in keyla-poke22: A Threat to npm Users
Summary
MAL-2025-157588: Malicious code in keyla-poke22 (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-poke22 is an npm package that has been identified as part of a malicious campaign targeting developers in the npm ecosystem. 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 manipulate package metadata and flood the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability in keyla-poke22 originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to a polluted npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly install these malicious packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall keyla-poke22If 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 keyla-poke22 package and monitor your project for any dependencies that may inadvertently include it. You can also utilize tools like Vulert to scan your package-lock.json file for vulnerabilities. Here’s how to use Vulert: Visit https://vulert.com/scanner, upload your package-lock.json, and check for vulnerabilities without any signup.
Conclusion
The keyla-poke22 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive steps, developers can safeguard their projects against such threats.
See every vulnerability recorded for keyla-poke22 →
FAQ
keyla-poke22 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious packages that modify your project's metadata, potentially compromising security and integrity.
You should uninstall the keyla-poke22 package immediately using 'npm uninstall keyla-poke22' and check your project for any other affected dependencies.
Regularly update your npm packages, monitor your dependencies for vulnerabilities using tools like Vulert, and be cautious when installing packages from unknown sources.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json. You can use it to check if your application is affected by vulnerabilities without requiring code access.
