Malicious Code Injection in jeep-poke37: A Threat to npm Ecosystem
Summary
MAL-2025-157005: Malicious code in jeep-poke37 (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-poke37 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary functionality is to inflate developer reputation scores through the tea.xyz token reward campaign, which has led to an influx of similar malicious packages in the registry.
Vulnerability Detail
The jeep-poke37 package contains malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The vulnerability originates from a campaign that exploits npm's publishing mechanisms, posing risks such as reputation damage for developers and increased difficulty in managing package dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke37If 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-poke37 package and any other packages that may be linked to the tea.xyz campaign. Monitor your package-lock.json file for any unauthorized changes and remove any suspicious packages immediately.
Conclusion
The jeep-poke37 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to mitigate the risks associated with this package.
See every vulnerability recorded for jeep-poke37 →
FAQ
jeep-poke37 is an npm package identified as part of a malicious campaign that modifies package metadata and floods the npm registry with derivative packages.
The malicious code can compromise your project's integrity by altering package metadata, which may lead to dependency issues and reputational damage.
You should uninstall jeep-poke37 immediately using the command npm uninstall jeep-poke37 and review your other dependencies for any related vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Yes, there are multiple packages associated with the tea.xyz token reward campaign. It is advisable to review your dependencies regularly and remove any suspicious packages.
