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

keyla-poke77 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157648: Malicious code in keyla-poke77 (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-poke77 is an npm package that has been implicated in a malicious campaign targeting developers participating in the tea.xyz token reward program. This package is designed to automate the generation and publication of derivative packages, which can mislead users and inflate developer reputation scores. The malicious behavior of this package poses a significant risk to the integrity of the npm registry and the security of applications relying on it.

Vulnerability Detail

The vulnerability in keyla-poke77 originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also compromises the security of applications that may unknowingly depend on these malicious packages. The potential ramifications include unauthorized access to sensitive data and the introduction of further vulnerabilities into dependent applications.

How To Fix

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

npm uninstall keyla-poke77

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 keyla-poke77 and any packages that depend on it. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The keyla-poke77 package poses a significant security risk due to its malicious behavior aimed at manipulating npm registry integrity. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their applications from potential threats.

See every vulnerability recorded for keyla-poke77 →

Share this vulnerability

FAQ

keyla-poke77 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores through the creation of derivative packages.

The malicious code can modify your package.json file, remove private flags, and introduce potentially harmful packages into your application, compromising its security.

You should uninstall keyla-poke77 immediately using the command npm uninstall keyla-poke77 and audit your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground without any signup.

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

How To Fix

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

npm uninstall keyla-poke77

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