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

keyla-poke95 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157668: Malicious code in keyla-poke95 (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-poke95 is an npm package that appears to be part of a broader scheme associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. Its functionality is compromised due to the presence of malicious code that alters package metadata and proliferates harmful variants across the npm registry.

Vulnerability Detail

The vulnerability in keyla-poke95 stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This code is part of a larger effort to spam the npm registry with derivative packages, which can lead to reputation inflation for developers and potential security risks for users who inadvertently install these malicious variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with numerous similar malicious packages.

How To Fix

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

npm uninstall keyla-poke95

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-poke95 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The keyla-poke95 package poses a significant risk due to its malicious code that alters package metadata and proliferates harmful variants. It is crucial for developers to be vigilant and regularly audit their dependencies to maintain the integrity and security of their projects. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for keyla-poke95 →

Share this vulnerability

FAQ

keyla-poke95 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to security risks and cluttering the npm registry with unwanted packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

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

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.

How To Fix

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

npm uninstall keyla-poke95

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