Malicious Code Injection in jeep-poke16: A Threat to npm Packages
Summary
MAL-2025-156982: Malicious code in jeep-poke16 (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-poke16 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package.json files and republishes variants to pollute the npm registry.
Vulnerability Detail
The vulnerability in jeep-poke16 arises from its malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeep-poke16If 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-poke16 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The jeep-poke16 package poses a significant threat due to its malicious code that alters package.json files and repopulates the npm registry with compromised variants. Developers are urged to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.
See every vulnerability recorded for jeep-poke16 →
FAQ
jeep-poke16 is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.
It modifies package.json files, removes private flags, changes version numbers, and republishes variants to pollute the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should remove the jeep-poke16 package from your project and monitor for any unauthorized changes in your package-lock.json file.
Currently, there is no specific patch mentioned for jeep-poke16. It is advisable to remove the package until a secure version is released.
