Malicious Code Injection in jeep-poke2: A Threat to npm Packages
Summary
MAL-2025-156986: Malicious code in jeep-poke2 (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
Background
jeep-poke2 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. It is designed to facilitate the development and distribution of JavaScript applications. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, potentially harming developers' reputations and the integrity of the npm ecosystem.
Vulnerability Detail
The jeep-poke2 package contains 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 the npm registry. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards, posing significant risks to developers and users relying on the integrity of npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke2If 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
Currently, the best workaround is to avoid using the jeep-poke2 package altogether. If it is already included in your project, remove it immediately and monitor your package-lock.json for any other potentially affected packages.
Conclusion
The jeep-poke2 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and proactive is key to maintaining the security of your applications.
See every vulnerability recorded for jeep-poke2 →
FAQ
jeep-poke2 is an npm package that has been identified as malicious, designed to manipulate package metadata and flood the npm registry.
The malicious code can compromise the integrity of your project by altering package metadata and potentially introducing security vulnerabilities.
You should uninstall the jeep-poke2 package immediately using the command npm uninstall jeep-poke2.
Yes, Vulert can monitor your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
