Malicious Code Injection in inal-poke64: A Threat to npm Ecosystem

inal-poke64 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156453: Malicious code in inal-poke64 (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 Your last release was probably never penetration tested 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 'inal-poke64' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate token rewards through the automatic generation and publication of derivative packages. This package, like others in the campaign, is intended to inflate developer reputation scores by creating numerous variants with randomized names.

Vulnerability Detail

The vulnerability in 'inal-poke64' stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages. The origin of this issue is linked to a broader trend of malicious packages flooding the npm ecosystem, particularly those associated with token reward schemes.

How To Fix

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

npm uninstall inal-poke64

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, you can avoid using the 'inal-poke64' package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The 'inal-poke64' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and stay vigilant about the packages you use. Utilizing tools like Vulert can help you monitor for vulnerabilities and maintain the integrity of your software.

See every vulnerability recorded for inal-poke64 →

Share this vulnerability

FAQ

The inal-poke64 package contains malicious code that modifies package.json files and floods the npm registry with compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

If you have installed inal-poke64, you should uninstall it immediately using the command 'npm uninstall inal-poke64' and review your other dependencies for similar vulnerabilities.

Yes, consider searching for alternative packages that provide similar functionality but have a verified reputation and are free from malicious code.

To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.

How To Fix

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

npm uninstall inal-poke64

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