Malicious Code Injection in keyla-poke81: A Threat to npm Packages
Summary
MAL-2025-157653: Malicious code in keyla-poke81 (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-poke81 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with harmful packages. The primary functionality of this package is to serve as a tool for developers, but it has been compromised to include malicious scripts that can alter package metadata and publish unauthorized derivatives.
Vulnerability Detail
The vulnerability in keyla-poke81 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The malicious payload can significantly impact developers by inflating reputation scores fraudulently and compromising 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-poke81If 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-poke81 and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks from malicious packages.
Conclusion
The keyla-poke81 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to remove this package and safeguard your projects.
See every vulnerability recorded for keyla-poke81 →
FAQ
keyla-poke81 is an npm package that has been identified as part of a malicious campaign designed to manipulate the npm registry.
The vulnerability can lead to unauthorized modifications of your package metadata and the potential pollution of the npm registry, affecting your project's integrity.
You should uninstall the package immediately using 'npm uninstall keyla-poke81' and audit your project for other vulnerable dependencies.
Regularly update your dependencies, use trusted packages, and utilize tools like npm audit to monitor for vulnerabilities.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file. You can check for vulnerabilities without any signup at the Vulert playground.
