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

jeep-poke26 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156993: Malicious code in jeep-poke26 (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-poke26 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, specifically for the tea.xyz protocol.

Vulnerability Detail

The vulnerability in jeep-poke26 stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised development environment, where developers may unknowingly use these malicious packages, risking their applications' integrity and security.

How To Fix

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

npm uninstall jeep-poke26

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, avoid using the jeep-poke26 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages.

Conclusion

The jeep-poke26 package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package and monitor your dependencies for any similar threats. Utilizing tools like Vulert can aid in maintaining a secure development environment.

See every vulnerability recorded for jeep-poke26 →

Share this vulnerability

FAQ

jeep-poke26 is an npm package identified as part of a malicious campaign that manipulates the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately using 'npm uninstall jeep-poke26' and check for any dependencies that may be affected.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall jeep-poke26

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