Malicious Code Injection in jeep-poke15: A Threat to npm Packages

jeep-poke15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The package jeep-poke15 is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to manage dependencies in their applications. However, jeep-poke15 has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns for developers and users alike.

Vulnerability Detail

The vulnerability in jeep-poke15 stems from its involvement in a malicious campaign that floods the npm registry with derivative packages. This package contains scripts designed to automatically generate and publish variants with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags and alters version numbers, which can lead to unintended consequences for developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.

How To Fix

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

npm uninstall jeep-poke15

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 measure, you can avoid using the jeep-poke15 package and replace it with a known, secure alternative. Always verify the integrity of packages before including them in your project.

Conclusion

The jeep-poke15 package poses a significant security risk due to its malicious code designed to exploit npm's publishing system. Developers must take immediate action to remove this package and ensure their dependencies are secure. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for jeep-poke15 →

Share this vulnerability

FAQ

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

If your application uses jeep-poke15, it may inadvertently include malicious code that can compromise security and functionality.

You should uninstall jeep-poke15 immediately and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json 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 jeep-poke15

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