Malicious Code Injection in keyla-poke28: A Threat to npm Ecosystem

keyla-poke28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157594: Malicious code in keyla-poke28 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

keyla-poke28 is an npm package that appears to be part of a broader campaign associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate npm's publishing system, creating numerous derivative packages with randomized names to inflate developer reputation scores. Its functionality is compromised due to the presence of malicious scripts that alter package metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in keyla-poke28 originates from its association with a malicious campaign that employs scripts to modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which can lead to the proliferation of untrustworthy packages in the npm ecosystem. The ramifications include potential security risks for developers who unknowingly install these packages, as they may contain harmful code or lead to further exploitation of the npm registry.

How To Fix

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

npm uninstall keyla-poke28

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-poke28 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages and remove any that are suspicious or unverified.

Conclusion

The keyla-poke28 package is compromised by malicious code that poses a significant threat to the npm ecosystem. It is essential for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for keyla-poke28 →

Share this vulnerability

FAQ

keyla-poke28 is an npm package involved in a malicious campaign that aims to manipulate the npm registry by creating numerous derivative packages.

The malicious code can alter your package.json file, leading to the installation of untrustworthy packages and potential security vulnerabilities in your project.

You should uninstall keyla-poke28 immediately using 'npm uninstall keyla-poke28' and audit your project for any other suspicious packages.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall keyla-poke28

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