Malicious Code Injection in iqbal-poke40: A Threat to npm Ecosystem

iqbal-poke40 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156847: Malicious code in iqbal-poke40 (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

iqbal-poke40 is a package within the npm ecosystem, often used for various development purposes. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability in iqbal-poke40 arises from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, potentially leading to further exploitation or data breaches.

How To Fix

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

npm uninstall iqbal-poke40

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 iqbal-poke40 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to ensure no malicious packages are included.

Conclusion

The iqbal-poke40 package poses a significant security risk due to its malicious behavior aimed at manipulating npm registry data. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for iqbal-poke40 →

Share this vulnerability

FAQ

iqbal-poke40 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

You should uninstall the package immediately using the command npm uninstall iqbal-poke40 and audit your project for any other malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall iqbal-poke40

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