Malicious Code Detected in fdir1 Package - npm Vulnerability Alert

fdir1 Updated 06 Dec 2025

Summary

06/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192353: Malicious code in fdir1 (npm). Affects fdir1 versions 99.99.2. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The fdir1 package is a Node.js library designed for directory manipulation and file handling. It is commonly used in various npm projects for its ease of use and efficiency in managing file systems. However, the package version 99.99.2 has been identified as malicious, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the fdir1 package arises from its communication with a domain linked to malicious activities and the execution of commands that can lead to harmful behavior. This could result in unauthorized access to sensitive data, system compromise, or further exploitation of the affected application. The malicious nature of the package was identified by the OpenSSF Package Analysis project, which flagged it due to its suspicious behavior.

How To Fix

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

npm uninstall fdir1

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

If immediate updating is not feasible, consider removing the fdir1 package from your project and replacing it with an alternative library that offers similar functionality without the associated risks.

Conclusion

The fdir1 package has been identified as malicious, posing serious risks to applications that utilize it. It is crucial to update to a secure version or find an alternative to mitigate these risks. Regular monitoring of dependencies using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for fdir1 →

Share this vulnerability

FAQ

fdir1 is a Node.js library used for directory and file manipulation in npm projects.

The OpenSSF Package Analysis project flagged the fdir1 package due to its communication with a malicious domain and execution of harmful commands.

Using this version can lead to unauthorized access, data breaches, and potential system compromise.

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

Consider removing the fdir1 package and replacing it with a safer alternative until you can update.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall fdir1

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