Malicious Code Injection in keyla-poke93: A Threat to npm Packages

keyla-poke93 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157666: Malicious code in keyla-poke93 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

keyla-poke93 is an npm package that has been implicated in a malicious campaign related to the tea.xyz token reward system. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. The malicious nature of this package poses significant risks to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in keyla-poke93 originates from its association with a malicious campaign that floods the npm registry with derivative 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 leads to the pollution of the npm registry and can compromise the integrity of other packages, potentially allowing for further exploitation.

How To Fix

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

npm uninstall keyla-poke93

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

As a temporary measure, avoid using keyla-poke93 and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.

Conclusion

The keyla-poke93 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for keyla-poke93 →

Share this vulnerability

FAQ

keyla-poke93 is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and exposing your project to further risks.

You should uninstall keyla-poke93 immediately using 'npm uninstall keyla-poke93' and check for any other affected packages in your project.

You can use tools like npm audit to check for vulnerabilities in your project. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall keyla-poke93

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