Malicious Code Injection in inal-poke105: A Threat to npm Users

inal-poke105 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156378: Malicious code in inal-poke105 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'inal-poke105' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of these packages is to automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'inal-poke105' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, which can lead to the proliferation of malicious variants in the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may inadvertently contribute to the pollution of the npm ecosystem and compromise their projects.

How To Fix

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

npm uninstall inal-poke105

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-poke105' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure no malicious packages are included.

Conclusion

The 'inal-poke105' package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata. It is essential to remove this package and any associated variants from your projects to maintain security. Regular audits and the use of monitoring tools like Vulert can help safeguard against such vulnerabilities.

See every vulnerability recorded for inal-poke105 →

Share this vulnerability

FAQ

'inal-poke105' is an npm package that has been identified as malicious, primarily associated with the tea.xyz token reward campaign.

The vulnerability can lead to the installation of malicious packages that modify your project's dependencies, potentially compromising security and functionality.

You should immediately remove 'inal-poke105' from your project and audit your dependencies for any other malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities, ensuring your project remains secure.

How To Fix

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

npm uninstall inal-poke105

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