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

keyla-poke35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157602: Malicious code in keyla-poke35 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

keyla-poke35 is an npm package that has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The primary functionality of keyla-poke35 is compromised due to its malicious intent, which aims to inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability in keyla-poke35 stems from its inclusion in a campaign that employs autopublish scripts to modify package.json files, removing private flags and altering version numbers. This manipulation allows the package to continuously republish variants with random names, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can lead to unintended consequences for developers who unknowingly install these compromised packages, including security risks and reputation damage.

How To Fix

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

npm uninstall keyla-poke35

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, avoid using keyla-poke35 and any other packages associated with the tea.xyz token reward campaign. Instead, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in keyla-poke35 highlights the importance of vigilance when using open-source packages. By understanding the nature of this vulnerability and taking appropriate actions, developers can protect their projects from potential threats. Regular monitoring and updates are essential to maintaining a secure development environment.

See every vulnerability recorded for keyla-poke35 →

Share this vulnerability

FAQ

keyla-poke35 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and damage your project's integrity.

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

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

npm uninstall keyla-poke35

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