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

keyla-poke97 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157670: Malicious code in keyla-poke97 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package keyla-poke97 is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to inflate developer reputation scores through automated publishing of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in keyla-poke97 originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these malicious 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-poke97

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 workaround, you can avoid using the keyla-poke97 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without any signup.

Conclusion

The keyla-poke97 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the security of their applications. Utilizing tools like Vulert can aid in monitoring for vulnerabilities effectively.

See every vulnerability recorded for keyla-poke97 →

Share this vulnerability

FAQ

keyla-poke97 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall keyla-poke97' and monitor your project for any unusual behavior.

Yes, tools like Vulert can help monitor your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application 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-poke97

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