Malicious Code Injection in jimmy-poke2: A Threat to npm Users
Summary
MAL-2025-157075: Malicious code in jimmy-poke2 (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-poke2' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in 'jimmy-poke2' stems from its association with a malicious campaign that floods the npm registry with derivative packages. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of projects that depend on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jimmy-poke2If 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, you can avoid using 'jimmy-poke2' and any packages that depend on it. Additionally, consider using the following command to uninstall the package: npm uninstall jimmy-poke2.
Conclusion
The 'jimmy-poke2' package poses a significant threat due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to remove this package and monitor their projects for any potential vulnerabilities. Utilizing tools like Vulert can enhance security and provide real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for jimmy-poke2 →
FAQ
The primary risk is the potential for malicious code to be executed in your application, which can lead to data breaches or unauthorized access.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
You should immediately uninstall the package and check your project for any dependencies that may have been affected.
While specific exploits have not been detailed, the nature of the vulnerability allows for significant risks, including the potential for code injection and registry pollution.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
