Malicious Code Injection in keyla-poke61: npm Package Vulnerability

keyla-poke61 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157631: Malicious code in keyla-poke61 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'keyla-poke61' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in 'keyla-poke61' stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry and potential exploitation of developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall keyla-poke61

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 remove the 'keyla-poke61' package from your project by executing 'npm uninstall keyla-poke61'. This will prevent any malicious code from executing in your environment until a secure version is released.

Conclusion

The 'keyla-poke61' package has been identified as having a serious vulnerability due to malicious code injection. It is crucial for developers to take immediate action to remove or update this package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and preventing such vulnerabilities in the future.

See every vulnerability recorded for keyla-poke61 →

Share this vulnerability

FAQ

The malicious code modifies package.json to remove private flags, changes version numbers, and generates random package names, leading to the pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check your application without any signup.

Using compromised packages can lead to security breaches, unauthorized access to sensitive data, and damage to your application's integrity.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

Immediately uninstall the package and check your project for any unauthorized changes. Consider using a secure alternative package.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall keyla-poke61

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