Malicious Code Injection in keyla-poke32: A Threat to npm Ecosystem
Summary
MAL-2025-157599: Malicious code in keyla-poke32 (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-poke32 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious activities on the npm registry. This package is designed to interact with the npm ecosystem, but it has been compromised to include harmful scripts that can affect developers and their projects.
Vulnerability Detail
The vulnerability in keyla-poke32 originates from its involvement in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry and inflate developer reputation scores fraudulently. The malicious payload can also lead to unintentional exposure of sensitive information and compromise the integrity of dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall keyla-poke32If 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 the keyla-poke32 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project's dependencies for vulnerabilities.
Conclusion
The keyla-poke32 package poses a significant risk due to its malicious code that can compromise the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your project's security posture.
See every vulnerability recorded for keyla-poke32 →
FAQ
keyla-poke32 is an npm package involved in a token reward campaign, but it has been identified as malicious due to its harmful scripts.
The malicious code can modify your package.json, remove private flags, and publish variants that can pollute the npm registry, potentially compromising your project's integrity.
You should remove the keyla-poke32 package from your project immediately and monitor your dependencies for any other vulnerabilities.
You can use Vulert, which monitors your package-lock.json to alert you in real-time for open-source vulnerabilities without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
