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

keyla-poke36 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157603: Malicious code in keyla-poke36 (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

keyla-poke36 is an npm package that appears to be part of a broader scheme involving the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been compromised to include malicious scripts that can alter its own metadata and proliferate harmful variants across the npm registry.

Vulnerability Detail

The vulnerability in keyla-poke36 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to continuously republish itself under random names, polluting the npm registry and potentially leading to security risks for users who unknowingly install these variants. The malicious payload is designed to exploit the npm ecosystem by creating numerous derivative packages with deceptive names, making it difficult for developers to identify the original, safe package.

How To Fix

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

npm uninstall keyla-poke36

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, users can manually check their package-lock.json file for any instances of keyla-poke36 and remove it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The keyla-poke36 package has been identified as containing malicious code that can compromise npm projects. Users are advised to uninstall the package and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your projects.

See every vulnerability recorded for keyla-poke36 →

Share this vulnerability

FAQ

keyla-poke36 is an npm package involved in a token reward campaign that has been compromised to include malicious code.

The malicious code can modify your package.json file, remove private flags, and create numerous derivative packages, potentially leading to security vulnerabilities.

You should uninstall the package immediately and monitor your project for any signs of compromise.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

You can find detailed information about this vulnerability in the package's repository or by checking security advisories related to npm packages.

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-poke36

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