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

keyla-poke72 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157643: Malicious code in keyla-poke72 (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-poke72 is an npm package that appears to be part of a broader scheme involving the tea.xyz token reward campaign. This package, like others in the campaign, is designed to manipulate the npm registry by automatically generating and publishing derivative packages. The malicious nature of this package lies in its ability to alter critical files and inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in keyla-poke72 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The package contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, potentially leading to security breaches and loss of reputation.

How To Fix

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

npm uninstall keyla-poke72

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-poke72 package and monitor your project for any instances of its usage. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can access Vulert's playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without any signup.

Conclusion

The keyla-poke72 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize monitoring tools like Vulert to safeguard their projects from such vulnerabilities.

See every vulnerability recorded for keyla-poke72 →

Share this vulnerability

FAQ

keyla-poke72 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.

You should uninstall the package immediately using 'npm uninstall keyla-poke72' and check for any other affected packages.

Regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and review package sources before installation.

Yes, you can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall keyla-poke72

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