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

inal-poke113 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156387: Malicious code in inal-poke113 (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 package 'inal-poke113' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package, like others in its category, aims to inflate developer reputation scores for rewards, but it has been compromised to include malicious scripts that can harm the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'inal-poke113' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This can lead to a significant risk for developers who may unknowingly install these malicious packages, compromising their applications and potentially leading to data breaches or other security issues.

How To Fix

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

npm uninstall inal-poke113

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 'inal-poke113' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'inal-poke113' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and publish harmful variants. Developers are urged to remove this package and regularly audit their dependencies to maintain application security.

See every vulnerability recorded for inal-poke113 →

Share this vulnerability

FAQ

The primary risk is that it modifies package.json files, potentially leading to the installation of malicious derivatives that can compromise application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Immediately uninstall the package using 'npm uninstall inal-poke113' and audit your project for any other potentially malicious packages.

Currently, there is no specific patched version for 'inal-poke113' since it is recommended to remove the package entirely.

Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities.

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-poke113

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