Malicious Code Injection in iqbal-poke41: A Threat to npm Users

iqbal-poke41 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

iqbal-poke41 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality is compromised, making it a potential risk for developers who may unknowingly include it in their projects.

Vulnerability Detail

The vulnerability in iqbal-poke41 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry by continuously republishing variants, which can lead to security risks and reputation damage for developers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall iqbal-poke41

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, avoid using the iqbal-poke41 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The iqbal-poke41 package poses a significant risk due to its malicious code that modifies project files and pollutes the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts on open-source vulnerabilities.

See every vulnerability recorded for iqbal-poke41 →

Share this vulnerability

FAQ

iqbal-poke41 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the modification of your package.json file, removal of private flags, and pollution of the npm registry, which may compromise your project's integrity and security.

You should uninstall the package immediately using the command npm uninstall iqbal-poke41 and audit your project for any other vulnerabilities.

You can use tools like npm audit to check for vulnerabilities in your packages. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

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

How To Fix

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

npm uninstall iqbal-poke41

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