Malicious Code Injection in keyla-poke25 Package: A Threat to npm Users

keyla-poke25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157591: Malicious code in keyla-poke25 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The keyla-poke25 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms to inflate developer reputation scores through the generation of derivative packages.

Vulnerability Detail

The vulnerability in the keyla-poke25 package originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading 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-poke25

If 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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package. It is advisable to monitor your dependencies closely and avoid using unverified packages.

Conclusion

The keyla-poke25 package poses a significant threat due to its malicious code designed to manipulate npm's publishing system. Users are strongly advised to uninstall this package and remain vigilant about their dependencies. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for keyla-poke25 →

Share this vulnerability

FAQ

keyla-poke25 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with compromised packages.

If your application uses the keyla-poke25 package, it may be at risk of being compromised due to the malicious scripts that modify package configurations and publish unauthorized variants.

You should immediately uninstall the keyla-poke25 package using the command npm uninstall keyla-poke25 and review your project's dependencies for any other potential vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground without any signup.

As of now, there is no patched version available for keyla-poke25. It is recommended to remove the package and avoid using any unverified packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall keyla-poke25

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback