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

inal-poke108 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156381: Malicious code in inal-poke108 (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-poke108' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'inal-poke108' originates from its malicious design, which includes scripts that automatically modify the package.json file to remove private flags and change version numbers. This allows the package to republish itself under various names, effectively polluting the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly use these packages, as well as a compromised npm ecosystem that can lead to further exploitation.

How To Fix

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

npm uninstall inal-poke108

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-poke108' package and monitor your dependencies for any malicious activity. Consider using tools like Vulert to check for vulnerabilities in your package-lock.json file. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability without needing to sign up.

Conclusion

The 'inal-poke108' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects. Staying informed and vigilant is crucial to maintaining the integrity of open-source software.

See every vulnerability recorded for inal-poke108 →

Share this vulnerability

FAQ

The 'inal-poke108' package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of derivative packages.

Using the 'inal-poke108' 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.

You should immediately uninstall the package using 'npm uninstall inal-poke108' and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application.

No, there is no patch available for 'inal-poke108' as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall inal-poke108

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