Malicious Code Injection in jeep-poke45: A Threat to npm Ecosystem
Summary
MAL-2025-157014: Malicious code in jeep-poke45 (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
The package jeep-poke45 is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly incorporate these packages into their projects.
Vulnerability Detail
The vulnerability in jeep-poke45 originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to security risks for developers who use these packages. The malicious payload can compromise the integrity of applications relying on affected packages, making them susceptible to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke45If 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-poke45 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The jeep-poke45 package poses a significant threat due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Removing the affected package and replacing it with secure alternatives is essential for maintaining the integrity of your projects.
See every vulnerability recorded for jeep-poke45 →
FAQ
jeep-poke45 is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through the publication of derivative packages.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and cluttering the npm registry with unwanted packages.
You should immediately uninstall the package using 'npm uninstall jeep-poke45' and check for any dependencies that may be affected.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, consider using well-known and trusted packages that provide similar functionality without the associated risks of malicious code.
