Malicious Code Injection in jeep-poke33: A Threat to npm Ecosystem
Summary
MAL-2025-157001: Malicious code in jeep-poke33 (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-poke33 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 manipulate developer reputation scores by flooding the registry with derivative packages. The functionality of jeep-poke33 is compromised due to its malicious intent, leading to potential security risks for developers and users relying on this package.
Vulnerability Detail
The vulnerability in jeep-poke33 stems from its design to execute autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, ultimately leading to the pollution of the npm registry. The malicious payload can inflate developer reputation scores fraudulently, posing risks of dependency confusion and potential exploitation of users who unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke33
If 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 measure, avoid using jeep-poke33 and any other packages associated with the tea.xyz token reward campaign. Monitor your package dependencies closely and consider using tools like Vulert to assess your project's vulnerability status. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The jeep-poke33 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to safeguard their projects against similar vulnerabilities in the future.
See every vulnerability recorded for jeep-poke33 →
FAQ
jeep-poke33 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores by flooding the npm registry with compromised packages.
The vulnerability can lead to the installation of malicious packages, which may compromise your project's security and integrity by introducing unwanted code or dependencies.
You should immediately uninstall jeep-poke33 using the command npm uninstall jeep-poke33 and review your project's dependencies for any other potentially harmful packages.
Regularly update your packages, use tools like Vulert to monitor for vulnerabilities, and avoid installing packages from untrusted sources.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application's vulnerability status in real-time at Vulert Scanner.