Malicious Code Injection in jeep-poke10: A Threat to npm Users

jeep-poke10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156976: Malicious code in jeep-poke10 (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-poke10 is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, jeep-poke10 has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in jeep-poke10 originates from its association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to confusion and security risks for developers relying on npm for package management.

How To Fix

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

npm uninstall jeep-poke10

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 jeep-poke10 package from your project by executing the command: npm uninstall jeep-poke10. This will help mitigate the risk until a patched version is available.

Conclusion

The jeep-poke10 package poses a significant security risk due to its malicious code injection vulnerability. Developers should take immediate action to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for jeep-poke10 →

Share this vulnerability

FAQ

jeep-poke10 is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the injection of malicious code, which may compromise the integrity of your application and its dependencies.

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

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and review package sources before installation.

How To Fix

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

npm uninstall jeep-poke10

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