Malicious Code Injection in jimmy-poke36: npm Package Vulnerability
Summary
MAL-2025-157093: Malicious code in jimmy-poke36 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'jimmy-poke36' is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts designed to manipulate package metadata and inflate developer reputation scores. The primary function of this package appears to be the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'jimmy-poke36' originates from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to continuously republish variants of the package, thereby polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards, making it a significant threat to developers and users relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jimmy-poke36If 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 this package by using the following command to uninstall it: npm uninstall jimmy-poke36. Additionally, consider using a package-lock.json file to monitor and control the versions of packages in your project.
Conclusion
The 'jimmy-poke36' package poses a significant threat due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate risks associated with open-source packages.
See every vulnerability recorded for jimmy-poke36 →
FAQ
The primary risk is that it contains malicious code that can alter package metadata and flood the npm registry with unwanted packages, potentially compromising other projects.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including those from the jimmy-poke36 package.
Yes, you can use npm audit to identify vulnerabilities in your dependencies and take action to remove or update affected packages.
You should immediately uninstall the package using the command: npm uninstall jimmy-poke36 and check for any other affected packages.
Yes, detailed information about the vulnerability can be found in the npm registry and through security advisories related to the package.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
