Malicious Code Injection in jeep-poke14: A Threat to npm Ecosystem

jeep-poke14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156980: Malicious code in jeep-poke14 (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

jeep-poke14 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate package metadata and inflate developer reputation scores through the generation of derivative packages. Its functionality is compromised by the presence of malicious scripts that automate the publishing of these packages, leading to potential abuse of the npm ecosystem.

Vulnerability Detail

The vulnerability in jeep-poke14 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The ramifications include potential security risks for applications relying on these packages, as well as reputational damage for developers.

How To Fix

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

npm uninstall jeep-poke14

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 jeep-poke14 and replace it with a trusted alternative package that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The jeep-poke14 package poses a significant threat to the npm ecosystem due to its malicious code and the potential for abuse. It is crucial for developers to be vigilant in monitoring their dependencies and to take immediate action to remove any compromised packages. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for jeep-poke14 →

Share this vulnerability

FAQ

jeep-poke14 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall jeep-poke14 immediately and replace it with a trusted package to mitigate the risk.

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall jeep-poke14

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