Malicious Code Injection in keyla-poke60 Package

keyla-poke60 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157630: Malicious code in keyla-poke60 (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-poke60 package 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 functionality of keyla-poke60 is to serve as a component in this ecosystem, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the keyla-poke60 package stems from its inclusion in a malicious campaign designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. This can result in security risks for developers who unknowingly integrate these compromised packages into their projects.

How To Fix

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

npm uninstall keyla-poke60

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 the keyla-poke60 package and monitor your project's dependencies for any malicious packages. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities. Here’s how you can use Vulert: Visit https://vulert.com/scanner and upload your package-lock.json to check for any affected packages.

Conclusion

The keyla-poke60 package has been identified as part of a malicious campaign that can compromise the integrity of projects using it. It is essential to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for keyla-poke60 →

Share this vulnerability

FAQ

keyla-poke60 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic publication of compromised packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and stability.

You should uninstall the keyla-poke60 package immediately using 'npm uninstall keyla-poke60' and check for any other compromised packages.

You can use Vulert to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file. Visit Vulert Scanner for more information.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories for the packages you use.

How To Fix

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

npm uninstall keyla-poke60

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