Malicious Code Injection in keyla-poke76: A Threat to npm Ecosystem
Summary
MAL-2025-157647: Malicious code in keyla-poke76 (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-poke76 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the same campaign, is designed to manipulate the npm ecosystem by generating and publishing derivative packages with random names. Its primary function is to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm packages.
Vulnerability Detail
The vulnerability in keyla-poke76 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry by continuously republishing variants of the package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages. The ramifications include potential security risks for applications relying on this package, as well as the degradation of the npm registry's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall keyla-poke76If 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 avoid using the keyla-poke76 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert.
Conclusion
The keyla-poke76 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package integrity. Developers are urged to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining application security.
See every vulnerability recorded for keyla-poke76 →
FAQ
keyla-poke76 is an npm package that has been identified as part of a malicious campaign to manipulate the npm ecosystem.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.
You should remove the keyla-poke76 package from your project and check for any unauthorized changes in your package-lock.json file.
You can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time 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 signing up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
