Which versions of @flowfuse/flowfuse are malicious?

The following npm versions of @flowfuse/flowfuse are flagged malicious: 2.24.2-375f5e6-202511240929.0. Treat any of these as compromised.

How do I remediate @flowfuse/flowfuse if I installed it?

Remove @flowfuse/flowfuse 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 @flowfuse/flowfuse — how do I know if it already compromised me?

If @flowfuse/flowfuse was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @flowfuse/flowfuse part of a known attack campaign?

Yes — @flowfuse/flowfuse is associated with the GHSA-mpvf-p8hg-65gw 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 @flowfuse/flowfuse across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @flowfuse/flowfuse (version 2.24.2-375f5e6-202511240929.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @flowfuse/flowfuse across your stack and pipelines.

Malicious package

@flowfuse/flowfusenpm

Malicious code in @flowfuse/flowfuse (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191453

Immediate action

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

npm uninstall @flowfuse/flowfuse

What this malware does

The package @flowfuse/flowfuse was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.24.2-375f5e6-202511240929.0

Indicators of compromise (SHA-256)

3f50820b961ca6c0ae3063f3b37383fb7ba7dfd65375fdf0a94723ea8a8016f3

22ba60a5d020675e45988b9c85546af27a402e4bdd7667fa7d8a30c7f94063f9

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @flowfuse/flowfuse (version 2.24.2-375f5e6-202511240929.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @flowfuse/flowfuse across your stack and pipelines.
If you installed it — respond
Remove @flowfuse/flowfuse 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 @flowfuse/flowfuse was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @flowfuse/flowfuse before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @flowfuse/flowfuse on npm has been identified as a malicious package (version 2.24.2-375f5e6-202511240929.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mpvf-p8hg-65gw

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @flowfuse/flowfuse-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