Malicious Code Injection in keyla-poke43: A Threat to npm Users
Summary
MAL-2025-157611: Malicious code in keyla-poke43 (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-poke43 is an npm package that has been implicated in a malicious campaign targeting developers within the npm ecosystem. This package is part of a broader initiative that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of keyla-poke43 lies in its ability to modify package metadata and republish itself under various names, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in keyla-poke43 originates from its design to automatically generate and publish derivative packages with randomized names. This behavior is facilitated by scripts that modify the package.json file, removing private flags and altering version numbers. The malicious payload not only pollutes the npm registry but also poses risks to developers who may unknowingly install these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall keyla-poke43If 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 measure, you can avoid using keyla-poke43 and any other packages that may be part of the malicious campaign. Consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The keyla-poke43 package poses a significant threat to npm users due to its malicious behavior of modifying and republishing packages. It is crucial for developers to be vigilant about the packages they use and to regularly check for vulnerabilities. By uninstalling affected packages and utilizing tools like Vulert, developers can better protect their projects from potential threats.
See every vulnerability recorded for keyla-poke43 →
FAQ
keyla-poke43 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the installation of malicious code that modifies your project's dependencies and potentially compromises its security.
You should uninstall the package immediately using the command npm uninstall keyla-poke43 and review your project's dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider using other reputable npm packages that provide similar functionality but do not have a history of malicious activity.
