Which versions of nf-promise-state-machine are malicious?

The following npm versions of nf-promise-state-machine are flagged malicious: 99.0.0, 99.0.1. Treat any of these as compromised.

How do I remediate nf-promise-state-machine if I installed it?

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

If nf-promise-state-machine 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.

Is nf-promise-state-machine part of a known attack campaign?

Yes — nf-promise-state-machine is associated with the RLMA-2026-01793 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find nf-promise-state-machine across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nf-promise-state-machine (2 malicious versions).

Malicious package

nf-promise-state-machinenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

nf-promise-state-machine is a confirmed malicious npm package (MAL-2026-2376) that executes malicious code on install (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nf-promise-state-machine (npm)

MAL-2026-2376

Immediate action

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

npm uninstall nf-promise-state-machine

What this malware does

The package nf-promise-state-machine was found to contain malicious code.

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

87b44ef357b1328779c351909f4628b2058c478fb02ab138c0670f4f885e9938

dc012f9411ceaa957f4b364f6b1443d3244155de13f5fc0ccb759ad682bd0ae7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nf-promise-state-machine (2 malicious versions).
If you installed it — respond
Remove nf-promise-state-machine 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 nf-promise-state-machine 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. nf-promise-state-machine on npm has been identified as a malicious package (versions 99.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01793

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nf-promise-state-machine-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