Malicious Code Injection in keyla-poke83 Package - npm Vulnerability

keyla-poke83 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157655: Malicious code in keyla-poke83 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The keyla-poke83 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit developers by flooding the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability originates from the keyla-poke83 package, which contains scripts that automatically generate and publish derivative packages with randomized names. These scripts remove private flags from package.json, alter version numbers, and continuously republish variants, leading to a polluted npm registry. The ramifications include potential security risks for developers who inadvertently use these malicious packages, as they may introduce unwanted code into their applications.

How To Fix

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

npm uninstall keyla-poke83

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-poke83 package and any packages that may have been derived from it. Regularly monitor your package-lock.json file for any unauthorized changes, and consider using tools like Vulert to check for vulnerabilities in your dependencies.

Conclusion

The keyla-poke83 package poses a significant security risk due to its malicious code designed to exploit npm's package management system. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor their dependencies for vulnerabilities.

See every vulnerability recorded for keyla-poke83 →

Share this vulnerability

FAQ

keyla-poke83 is an npm package that has been identified as part of a malicious campaign to exploit developers by flooding the npm registry with derivative packages.

The vulnerability can introduce malicious code into your application, potentially compromising its security and functionality.

You should immediately uninstall the keyla-poke83 package and review your project for any unauthorized changes or dependencies.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall keyla-poke83

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