Malicious Code Injection in keyla-poke4: A Threat to npm Users
Summary
MAL-2025-157607: Malicious code in keyla-poke4 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
keyla-poke4 is an npm package that has been identified as part of a malicious campaign targeting developers within the npm ecosystem. This package is designed to exploit the npm registry by generating and publishing derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. The malicious behavior of this package poses a significant risk to the integrity of the npm registry and the security of applications relying on it.
Vulnerability Detail
The vulnerability in keyla-poke4 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates 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. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall keyla-poke4If 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 the malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include keyla-poke4 or any other suspicious packages. You can also use tools like Vulert to monitor your project for vulnerabilities without requiring code access. For more information, visit https://vulert.com/scanner.
Conclusion
The keyla-poke4 package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications. Regular monitoring and updating of dependencies can help mitigate these risks.
See every vulnerability recorded for keyla-poke4 →
FAQ
keyla-poke4 is an npm package identified as part of a malicious campaign that exploits the npm registry.
The vulnerability can lead to the installation of malicious code, compromising the security and integrity of your application.
You should uninstall keyla-poke4 immediately using the command 'npm uninstall keyla-poke4' and check your project for any other affected packages.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
