Malicious Code Injection in jimmy-poke21: A Threat to npm Users
Summary
MAL-2025-157077: Malicious code in jimmy-poke21 (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 'jimmy-poke21' is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign linked to the tea.xyz token reward initiative. It is designed to manipulate the npm registry by creating and publishing numerous derivative packages with random names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'jimmy-poke21' originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include a loss of trust in the npm ecosystem and possible exploitation of affected applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jimmy-poke21If 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 prevent the installation of 'jimmy-poke21' by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the automatic installation of this malicious package until a fix is implemented.
Conclusion
The 'jimmy-poke21' package poses a significant security threat due to its malicious code that manipulates the npm registry. Developers must take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for jimmy-poke21 →
FAQ
The primary risk is that it modifies package.json files and floods the npm registry with malicious variants, which can compromise the integrity of other packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed the package, it is recommended to remove it immediately and check for any other affected packages in your project.
Currently, there are no known patches for the jimmy-poke21 package. It is advised to remove the package until a secure version is released.
Vulert uses the package-lock.json file to monitor and alert users in real-time for open-source vulnerabilities, ensuring that developers can maintain secure applications.
