What does the fdir1 malware do?

The package fdir1 was found to contain malicious code. The OpenSSF Package Analysis project identified 'fdir1' @ 99.99.2 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of fdir1 are malicious?

The following npm versions of fdir1 are flagged malicious: 99.99.2. Treat any of these as compromised.

How do I remediate fdir1 if I installed it?

Remove fdir1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed fdir1 — how do I know if it already compromised me?

If fdir1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find fdir1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fdir1 (version 99.99.2).

Malicious package

fdir1npm

Advisory published Dec 6, 2025Updated Dec 10, 2025

fdir1 is a confirmed malicious npm package (MAL-2025-192353) that executes malicious code on install (malicious version 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fdir1 (npm)

MAL-2025-192353

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall fdir1

What this malware does

The package fdir1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'fdir1' @ 99.99.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.99.2

Indicators of compromise (SHA-256)

8f5aefdb4168145eaa4b092c9e5f4fbd482f9fbd1fc0328b3272f3e2067731e8

7ba081e2ca3fffe519e73fc13330df7332fbaf118aa8f6c193b43e9b2ce8a5ce

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for fdir1 (version 99.99.2).
If you installed it — respond
Remove fdir1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If fdir1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. fdir1 on npm has been identified as a malicious package (version 99.99.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks fdir1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database