Malicious Code Injection in inal-poke22 Package - npm Vulnerability

inal-poke22 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156407: Malicious code in inal-poke22 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The inal-poke22 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward system. It is designed to manipulate package metadata and publish numerous derivative packages, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the inal-poke22 package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential security risks for developers who unknowingly use these packages.

How To Fix

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

npm uninstall inal-poke22

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-poke22 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The inal-poke22 package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and the integrity of the npm registry. It is crucial to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for inal-poke22 →

Share this vulnerability

FAQ

The inal-poke22 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

Using the inal-poke22 package can lead to security risks, including the potential for your project to be associated with malicious activities and the pollution of the npm registry.

If you have installed the inal-poke22 package, you should uninstall it immediately using 'npm uninstall inal-poke22' and check for any dependencies that may rely on it.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can also use the Vulert playground to check if your application is affected by this vulnerability.

To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall inal-poke22

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