Malicious Code Injection in jimmy-poke46: A Threat to npm Users
Summary
MAL-2025-157104: Malicious code in jimmy-poke46 (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-poke46' is part of a broader campaign targeting npm users, associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, thereby inflating developer reputation scores. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in 'jimmy-poke46' stems from its inclusion in a malicious campaign that employs scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers, and a compromised ecosystem due to the proliferation of untrustworthy packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jimmy-poke46If 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, consider removing the 'jimmy-poke46' package from your project. You can do this by executing the command: npm uninstall jimmy-poke46. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'jimmy-poke46' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for jimmy-poke46 →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with untrustworthy packages.
You can use Vulert to monitor your application for vulnerabilities. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner.
It is recommended to uninstall the package immediately and check for any unauthorized changes in your project.
Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using your package-lock.json file.
The long-term implications include a compromised npm ecosystem, potential security risks for applications using affected packages, and a loss of trust in the npm registry.
