Malicious Code Injection in jeep-poke17: A Threat to npm Users
Summary
MAL-2025-156983: Malicious code in jeep-poke17 (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-poke17 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the tea.xyz token reward initiative, is designed to manipulate developer reputation scores by flooding the registry with derivative packages. Its primary function is to serve as a vehicle for malicious scripts that alter package metadata and republish variants, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in jeep-poke17 arises from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which can pollute the npm registry and potentially expose users to further security risks. The origin of this vulnerability is linked to the tea.xyz token reward scheme, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke17If 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-poke17 package and replace it with a trusted alternative that serves the same purpose without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The jeep-poke17 package poses a significant threat to users of the npm ecosystem due to its malicious code designed to manipulate package metadata and reputation scores. It is essential to remove this package from your projects and monitor for vulnerabilities regularly. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for jeep-poke17 →
FAQ
jeep-poke17 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and expose your project to further security risks due to the malicious behavior of the package.
You should uninstall jeep-poke17 immediately using the command 'npm uninstall jeep-poke17' and monitor your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
