Malicious Code Injection in keyla-poke9: A Threat to npm Ecosystem

keyla-poke9 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157662: Malicious code in keyla-poke9 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

keyla-poke9 is an npm package that has been identified as part of a larger malicious campaign targeting the npm ecosystem. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. Its primary functionality is to participate in the tea.xyz token reward scheme, which incentivizes developers to inflate their reputation scores through the creation of numerous fake packages.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the keyla-poke9 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby allowing the package to continuously republish itself and its variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit the npm registry for nefarious purposes. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a degradation of trust in the npm ecosystem.

How To Fix

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

npm uninstall keyla-poke9

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, you can avoid using the keyla-poke9 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages.

Conclusion

The keyla-poke9 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from potential risks associated with this and similar vulnerabilities.

See every vulnerability recorded for keyla-poke9 →

Share this vulnerability

FAQ

keyla-poke9 is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the creation of fake packages.

The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project inadvertently uses compromised packages.

You should uninstall the keyla-poke9 package immediately using 'npm uninstall keyla-poke9' and audit your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors 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 needing to sign up.

How To Fix

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

npm uninstall keyla-poke9

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