Malicious Code Injection in jeep-poke29: A Threat to npm Users
Summary
MAL-2025-156996: Malicious code in jeep-poke29 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
jeep-poke29 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. It is crucial for developers to be aware of such vulnerabilities as they can lead to significant security risks and pollution of the npm ecosystem.
Vulnerability Detail
The vulnerability in jeep-poke29 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke29If 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, avoid using the jeep-poke29 package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The jeep-poke29 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and inflates developer reputation scores. It is crucial for developers to take immediate action to remove this package and monitor their projects for any vulnerabilities.
See every vulnerability recorded for jeep-poke29 →
FAQ
jeep-poke29 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 may compromise the integrity of your project if the malicious package is inadvertently used.
You should uninstall jeep-poke29 immediately using the command npm uninstall jeep-poke29 and check for any dependencies that may rely on it.
You can use tools like npm audit to regularly check for vulnerabilities in your npm packages.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
