Malicious Code Injection in jeep-poke32: A Threat to npm Ecosystem
Summary
MAL-2025-157000: Malicious code in jeep-poke32 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
jeep-poke32 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm ecosystem by introducing harmful scripts and altering package metadata.
Vulnerability Detail
The vulnerability in jeep-poke32 stems from its association with a campaign that deploys autopublish scripts designed to manipulate package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The malicious payload can result in unauthorized access to sensitive data, reputation damage for developers, and potential exploitation of downstream applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke32If 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 jeep-poke32 from your project by executing the following command: npm uninstall jeep-poke32. This will prevent any malicious code from executing while you assess the impact of this vulnerability on your application.
Conclusion
The jeep-poke32 package poses a significant threat to the npm ecosystem due to its malicious code and the potential for exploitation. It is essential for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove or update affected packages to safeguard applications.
See every vulnerability recorded for jeep-poke32 →
FAQ
jeep-poke32 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive data and compromising the integrity of your application.
If you have installed jeep-poke32, it is crucial to uninstall it immediately and monitor your application for any unusual behavior.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at Vulert Playground.
Currently, there are no known patches for jeep-poke32. It is advisable to keep an eye on the npm registry for any updates or patches that may be released.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
