Malicious Code Injection in jimmy-poke3: A Threat to npm Users

jimmy-poke3 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157086: Malicious code in jimmy-poke3 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'jimmy-poke3' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'jimmy-poke3' originates from its association with a malicious campaign that utilizes autopublish scripts to modify the package.json file. This manipulation removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised package integrity, potential data leaks, and a degraded developer reputation system within the npm ecosystem.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall jimmy-poke3

If 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, users can remove the 'jimmy-poke3' package from their project by executing the command: npm uninstall jimmy-poke3. This will prevent any malicious code from executing while a permanent fix is being sought.

Conclusion

The 'jimmy-poke3' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. Users are advised to uninstall the package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for jimmy-poke3 →

Share this vulnerability

FAQ

'jimmy-poke3' is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata for token rewards.

The vulnerability can lead to the injection of malicious code, compromising the integrity of your project and potentially exposing sensitive data.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall jimmy-poke3

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback