Malicious Code Injection in jeep-poke40: A Threat to npm Packages
Summary
MAL-2025-157009: Malicious code in jeep-poke40 (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-poke40 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the npm registry with derivative packages. The malicious nature of jeep-poke40 lies in its ability to manipulate package metadata and publish harmful variants, compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in jeep-poke40 originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file by removing private flags and changing version numbers. The ramifications include potential security risks for developers who unknowingly install these malicious packages, leading to compromised applications and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke40If 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-poke40 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The jeep-poke40 package poses a significant threat to the npm ecosystem due to its malicious behavior of publishing harmful variants and modifying package metadata. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for jeep-poke40 →
FAQ
jeep-poke40 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.
The vulnerability can lead to the installation of malicious packages that modify your project's metadata, potentially compromising security and integrity.
You should uninstall jeep-poke40 immediately using 'npm uninstall jeep-poke40' and review your project's dependencies for any other malicious packages.
You can use tools like npm audit to check for vulnerabilities in your dependencies. Additionally, consider using Vulert, which monitors and alerts for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
