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

inal-poke97 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156488: Malicious code in inal-poke97 (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 Penetration testing for web, API and mobile 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-poke97' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of these packages poses a significant risk to the integrity of the npm registry and the security of applications that depend on them.

Vulnerability Detail

The vulnerability in 'inal-poke97' originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and creates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of dependent applications. The malicious payload is embedded in the package, making it a serious threat to developers and users alike.

How To Fix

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

npm uninstall inal-poke97

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 measure, you can avoid using the 'inal-poke97' package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.

Conclusion

The 'inal-poke97' package represents a significant threat within the npm ecosystem due to its malicious code that alters package metadata and republish variants. Developers must take immediate action to remove this package and implement best practices for dependency management to safeguard their applications.

See every vulnerability recorded for inal-poke97 →

Share this vulnerability

FAQ

The inal-poke97 package contains malicious code that modifies package.json files and republish variants to the npm registry, posing a security risk.

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

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

There are no patches available for the inal-poke97 package as it is inherently malicious. The best course of action is to remove it from your project.

Regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall inal-poke97

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