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

jeep-poke41 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157010: Malicious code in jeep-poke41 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

jeep-poke41 is an npm package that has been identified as part of a malicious campaign targeting developers in the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with derivative packages. The primary functionality of jeep-poke41 is to serve as a placeholder or utility package, but it has been compromised to facilitate malicious activities.

Vulnerability Detail

The vulnerability in jeep-poke41 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for rewards in the tea protocol, leading to the continuous republishing of these variants and polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's package management system for nefarious purposes.

How To Fix

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

npm uninstall jeep-poke41

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 prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The jeep-poke41 package poses a significant threat due to its malicious code designed to manipulate npm's package management system. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor for vulnerabilities. By taking these steps, you can help protect your projects from potential exploitation.

See every vulnerability recorded for jeep-poke41 →

Share this vulnerability

FAQ

jeep-poke41 is an npm package that has been compromised to include malicious code aimed at manipulating the npm registry.

The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and affecting your developer reputation.

You should uninstall jeep-poke41 immediately and check your package-lock.json for any references to it.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to create an account.

How To Fix

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

npm uninstall jeep-poke41

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