Malicious Code Detected in fdir2 Package: Version 99.99.2 Compromised

fdir2 Updated 06 Dec 2025

Summary

06/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192354: Malicious code in fdir2 (npm). Affects fdir2 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 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 fdir2 package is a Node.js library designed for directory manipulation and file handling. It allows developers to efficiently navigate and manage file systems in their applications. However, the package version 99.99.2 has been identified as malicious, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the fdir2 package arises from its communication with a domain linked to malicious activities and the execution of commands that can compromise system integrity. This behavior can lead to unauthorized access, data theft, or further exploitation of the affected systems. The origin of this vulnerability is traced back to the package's malicious design, which was flagged by the OpenSSF Package Analysis project.

How To Fix

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

npm uninstall fdir2

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 remove the fdir2 package from your project until a secure version is released. Use the following command to uninstall the package: 'npm uninstall fdir2'. This will prevent any malicious code from executing in your application.

Conclusion

The fdir2 package version 99.99.2 has been flagged as malicious, posing serious security risks. Users are advised to update or remove the package to protect their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for fdir2 →

Share this vulnerability

FAQ

The fdir2 package is used for directory manipulation and file handling in Node.js applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

If you cannot update the package right away, consider removing it from your project as a temporary workaround.

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

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time using just your package-lock.json file.

How To Fix

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

npm uninstall fdir2

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