Malicious Code Injection in jimmy-poke28: A Threat to npm Users
Summary
MAL-2025-157084: Malicious code in jimmy-poke28 (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-poke28' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of such packages is primarily to manipulate the npm registry, which can lead to significant issues for developers relying on the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'jimmy-poke28' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry with derivative packages, potentially leading to security risks for developers who may unknowingly use these compromised packages. The malicious payload can also affect the reputation of legitimate packages and developers within the npm community.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jimmy-poke28If 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 'jimmy-poke28' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The 'jimmy-poke28' package poses a significant risk to npm users due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively. Staying informed and proactive can help maintain the security of your applications.
See every vulnerability recorded for jimmy-poke28 →
FAQ
'jimmy-poke28' is an npm package that has been identified as malicious, designed to manipulate the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall jimmy-poke28' and audit your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
