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

keyla-poke75 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157646: Malicious code in keyla-poke75 (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

The keyla-poke75 package 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to developers and users alike.

Vulnerability Detail

The vulnerability in the keyla-poke75 package originates from its association with a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This malicious code modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants to pollute the npm registry. The ramifications include potential security risks for users who unknowingly install these compromised packages, leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall keyla-poke75

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-poke75 package altogether until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The keyla-poke75 package poses a significant threat due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take necessary precautions to protect their applications.

See every vulnerability recorded for keyla-poke75 →

Share this vulnerability

FAQ

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

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially leading to security vulnerabilities in your application.

If you have installed the keyla-poke75 package, it is recommended to update it to the latest version or remove it from your project until a safe version is available.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application using the Vulert playground without any signup.

Detailed information about this vulnerability can be found in the vulnerability report and the package's repository on npm.

How To Fix

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

npm uninstall keyla-poke75

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