Malicious Code Injection in keyla-poke71: A Threat to npm Users

keyla-poke71 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157642: Malicious code in keyla-poke71 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

keyla-poke71 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various npm packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the applications that depend on it.

Vulnerability Detail

The vulnerability in keyla-poke71 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with derivative packages. The ramifications include potential security risks for applications that rely on this package, as well as the degradation of the npm ecosystem due to the proliferation of malicious packages.

How To Fix

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

npm uninstall keyla-poke71

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 prevent the installation of the malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include keyla-poke71 or any of its derivatives. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The keyla-poke71 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Users must take immediate action to remove the package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for keyla-poke71 →

Share this vulnerability

FAQ

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

The vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package.json and pollutes the npm registry.

You should uninstall the package immediately using 'npm uninstall keyla-poke71' and check your project for any other affected dependencies.

You can use 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-poke71

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