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

jeep-poke8 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157023: Malicious code in jeep-poke8 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The jeep-poke8 package 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, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.

Vulnerability Detail

The jeep-poke8 package contains malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards associated with the tea.xyz project. The ramifications include the pollution of the npm registry and potential security risks for applications that inadvertently depend on these malicious packages.

How To Fix

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

npm uninstall jeep-poke8

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 the jeep-poke8 package and replace it with a trusted alternative. Regularly monitor your package dependencies for any signs of malicious activity, and consider using tools like Vulert to track vulnerabilities in your project.

Conclusion

The jeep-poke8 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and repopulates the registry with harmful variants. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications against such vulnerabilities.

See every vulnerability recorded for jeep-poke8 →

Share this vulnerability

FAQ

The jeep-poke8 package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry and inflate developer reputation scores.

The malicious code can lead to the pollution of the npm registry and may introduce security vulnerabilities into your application if you depend on compromised packages.

You should uninstall the jeep-poke8 package immediately using the command npm uninstall jeep-poke8 and audit your project for any other potentially malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall jeep-poke8

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