Malicious Code Injection in keyla-poke105 Package - npm Vulnerability

keyla-poke105 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The keyla-poke105 package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and properties, thereby inflating developer reputation scores.

Vulnerability Detail

The vulnerability in the keyla-poke105 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and creates random package names, which leads to the continuous republishing of these variants. The origin of this issue is linked to a broader trend of malicious packages flooding the npm registry, specifically targeting developers involved in the tea protocol token rewards. The ramifications include potential pollution of the npm registry and compromised developer reputations.

How To Fix

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

npm uninstall keyla-poke105

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 remove the keyla-poke105 package from your project by executing the following command: npm uninstall keyla-poke105. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The keyla-poke105 package poses a significant risk due to its malicious code that alters project configurations and can lead to reputational damage. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for keyla-poke105 →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and damaging your project's reputation.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall keyla-poke105

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