Malicious Code Injection in keyla-poke102: A Threat to npm Users
Summary
MAL-2025-157572: Malicious code in keyla-poke102 (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-poke102 is a package available on the npm ecosystem, often utilized in various JavaScript projects. It is part of a broader campaign involving token rewards that has led to the proliferation of malicious packages. This specific package has been identified as containing harmful scripts that manipulate its own metadata and publish derivatives, posing a risk to developers and their projects.
Vulnerability Detail
The vulnerability in keyla-poke102 stems from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall keyla-poke102If 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 keyla-poke102 and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and source of packages before including them in your project.
Conclusion
The keyla-poke102 package poses a significant risk due to its malicious code that alters package metadata and publishes harmful derivatives. It is essential for developers to uninstall this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for keyla-poke102 →
FAQ
keyla-poke102 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall keyla-poke102' and check your project for any other affected packages.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, use trusted sources, and consider using tools like Vulert to monitor for vulnerabilities in your project.
