What does the f0-state-manager malware do?

The package f0-state-manager was found to contain malicious code. The OpenSSF Package Analysis project identified 'f0-state-manager' @ 99.13.9 (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 f0-state-manager are malicious?

The following npm versions of f0-state-manager are flagged malicious: 99.13.9. Treat any of these as compromised.

How do I remediate f0-state-manager if I installed it?

Remove f0-state-manager 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 f0-state-manager — how do I know if it already compromised me?

If f0-state-manager 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 f0-state-manager across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for f0-state-manager (version 99.13.9).

Malicious package

f0-state-managernpm

Advisory published Mar 29, 2026Updated Mar 31, 2026

f0-state-manager is a confirmed malicious npm package (MAL-2026-2287) that executes malicious code on install (malicious version 99.13.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in f0-state-manager (npm)

MAL-2026-2287

Immediate action

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

npm uninstall f0-state-manager

What this malware does

The package f0-state-manager was found to contain malicious code.

The OpenSSF Package Analysis project identified 'f0-state-manager' @ 99.13.9 (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.13.9

Indicators of compromise (SHA-256)

843c9d414a45b746177092a8c7119a4a5ea88f852bed2e14884e5adb9fc13b1f

989b5f62777b6b7fbd236eb28a54b0e42ba48548dc0a49919c5f311c1f1c7072

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for f0-state-manager (version 99.13.9).
If you installed it — respond
Remove f0-state-manager 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 f0-state-manager 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. f0-state-manager on npm has been identified as a malicious package (version 99.13.9 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 f0-state-manager-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