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

keyla-poke69 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The package 'keyla-poke69' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to inflate developer reputation scores through automated publishing of derivative packages. However, 'keyla-poke69' has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'keyla-poke69' originates from its design to include autopublish scripts that modify the package.json file. This malicious payload removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently introduce vulnerabilities into their applications.

How To Fix

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

npm uninstall keyla-poke69

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-poke69' package and monitor your project for any instances of its usage. If you have already installed it, remove it immediately using the command: 'npm uninstall keyla-poke69'.

Conclusion

The 'keyla-poke69' package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial to remove this package and monitor your projects for vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for keyla-poke69 →

Share this vulnerability

FAQ

'keyla-poke69' is an npm package associated with a token reward campaign that has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to the republishing of harmful package variants.

You should uninstall 'keyla-poke69' immediately using the command 'npm uninstall keyla-poke69' to mitigate any risks.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Check out the Vulert playground at Vulert Scanner for a quick assessment.

Yes, there are several packages that have been reported to contain malicious code. It is essential to stay updated on security advisories and regularly audit your dependencies.

How To Fix

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

npm uninstall keyla-poke69

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