Malicious Code Injection in firdouskhan Package: npm Vulnerability Overview

firdouskhan Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171227: Malicious code in firdouskhan (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 firdouskhan package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by publishing numerous derivative packages with altered metadata. The primary functionality of firdouskhan is to serve as a token reward mechanism, but it has been compromised to inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability in the firdouskhan package originates from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially compromise other packages and applications relying on npm.

How To Fix

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

npm uninstall firdouskhan

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 prevent the installation of the firdouskhan package by using the following command: 'npm install --no-save firdouskhan'. This will ensure that the package is not added to your dependencies while you assess your application's security.

Conclusion

The firdouskhan package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to take immediate action by removing this package and monitoring your application for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for firdouskhan →

Share this vulnerability

FAQ

The firdouskhan package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through deceptive practices.

The vulnerability can lead to the pollution of the npm registry, potentially compromising other packages and applications that rely on npm for dependencies.

You should uninstall the firdouskhan package immediately using 'npm uninstall firdouskhan' and check for any other affected packages.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package.json and package-lock.json files for any suspicious packages.

How To Fix

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

npm uninstall firdouskhan

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