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

keyla-poke62 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157632: Malicious code in keyla-poke62 (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-poke62 is an npm package that appears to be part of a broader campaign aimed at exploiting the npm registry. This package is designed to facilitate token rewards for the tea.xyz protocol by generating and publishing numerous derivative packages. Its functionality is compromised by malicious scripts that manipulate package metadata, potentially affecting developers' reputations and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in keyla-poke62 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and undermining the trustworthiness of legitimate packages.

How To Fix

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

npm uninstall keyla-poke62

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-poke62 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-poke62 package poses a significant threat due to its malicious code that manipulates package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor your dependencies regularly to maintain the integrity of your applications.

See every vulnerability recorded for keyla-poke62 →

Share this vulnerability

FAQ

keyla-poke62 is an npm package linked to a malicious campaign that aims to exploit the npm registry for token rewards.

The vulnerability can lead to the pollution of the npm registry, affecting the integrity of your project's dependencies and potentially damaging your reputation as a developer.

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

You can use tools like Vulert, which monitors your package-lock.json 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 any signup.

How To Fix

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

npm uninstall keyla-poke62

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