Malicious Code Injection in jeep-poke35: A Threat to npm Users
Summary
MAL-2025-157003: Malicious code in jeep-poke35 (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-poke35 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in jeep-poke35 originates from its design to execute autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, often themed around Indonesian culture, and continuously republish these variants to the npm registry. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke35If 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-poke35 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The jeep-poke35 package poses a significant threat to npm users due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial to take immediate action to remove this package and monitor your projects for any vulnerabilities.
See every vulnerability recorded for jeep-poke35 →
FAQ
jeep-poke35 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your project to security risks if malicious packages are inadvertently included.
You should uninstall the jeep-poke35 package immediately and check your package-lock.json file for any references to it.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
