Which versions of logfuse are malicious?

The following npm versions of logfuse are flagged malicious: 2.1.6. Treat any of these as compromised.

How do I remediate logfuse if I installed it?

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

If logfuse 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 logfuse part of a known attack campaign?

Yes — logfuse is associated with the RLMA-2026-05145, IN-MAL-2026-009409, RLUA-2026-06312 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 logfuse across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for logfuse (version 2.1.6).

Malicious package

logfusenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

logfuse is a confirmed malicious npm package (MAL-2026-7314) that executes malicious code on install (malicious version 2.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in logfuse (npm)

MAL-2026-7314

Immediate action

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

npm uninstall logfuse

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Malicious versions

1 flagged

2.1.6

Indicators of compromise (SHA-256)

389e75ed90c0c82ffc717d29b97dd7b368dc458cdfa0005440be404baef1c971

259fc8b205e41dea32af006c7eaa325f0d1cca2421c668b778b8d2559d8ec900

3d08b2e7fe62e81b7f3d100414dac694f05ad40ab5db36641a52c56d13f4d05f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05145IN-MAL-2026-009409RLUA-2026-06312

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks logfuse-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