Malicious Code Injection in jeep-poke13: A Threat to npm Packages
Summary
MAL-2025-156979: Malicious code in jeep-poke13 (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-poke13 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with the proliferation of malicious packages on the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in jeep-poke13 stems from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to pollution of the npm registry. The malicious payload can potentially compromise the integrity of the npm ecosystem, allowing for further exploitation and abuse of developer trust.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke13If 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 jeep-poke13 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to identify and remove any potentially malicious packages.
Conclusion
The jeep-poke13 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for jeep-poke13 →
FAQ
jeep-poke13 is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially introducing further security risks.
You should remove jeep-poke13 from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for 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.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
