Malicious Code Injection in keyla-poke56 Package - npm Vulnerability
Summary
MAL-2025-157625: Malicious code in keyla-poke56 (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
The keyla-poke56 package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automatically generate and publish derivative versions with randomized names, aimed at inflating developer reputation scores for token rewards. The functionality of this package is compromised due to its malicious intent, which poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in the keyla-poke56 package originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive data and the proliferation of untrustworthy packages in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall keyla-poke56If 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 workaround, you can monitor your package dependencies using tools like Vulert. By utilizing Vulert's playground at https://vulert.com/scanner, you can check if your application is affected by this vulnerability without requiring any signup. This tool analyzes your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Conclusion
The keyla-poke56 package poses a significant risk due to its malicious code that modifies package metadata and proliferates untrustworthy variants. It is crucial for developers to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their applications. Staying informed and proactive can help mitigate risks associated with open-source dependencies.
See every vulnerability recorded for keyla-poke56 →
FAQ
keyla-poke56 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of untrustworthy packages into your application, potentially compromising security and data integrity.
You should uninstall the keyla-poke56 package immediately using the command 'npm uninstall keyla-poke56' and review your other dependencies for similar vulnerabilities.
Yes, regularly update your packages, monitor your dependencies with tools like Vulert, and review the security advisories for the packages you use.
Yes, you can use Vulert's playground at Vulert Scanner to analyze your package-lock.json file for vulnerabilities without any signup.
