Which versions of n8n-nodes-healthmon are malicious?

The following npm versions of n8n-nodes-healthmon are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate n8n-nodes-healthmon if I installed it?

n8n-nodes-healthmon establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed n8n-nodes-healthmon — how do I know if it already compromised me?

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

Yes — n8n-nodes-healthmon is associated with the IN-MAL-2026-020341 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 n8n-nodes-healthmon across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for n8n-nodes-healthmon (version 1.0.0).

Malicious package

n8n-nodes-healthmonnpm

Advisory published Sep 23, 2026Updated Sep 23, 2026

n8n-nodes-healthmon is a confirmed malicious npm package (MAL-2026-16444) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in n8n-nodes-healthmon (npm)

MAL-2026-16444

Immediate action

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

npm uninstall n8n-nodes-healthmon

What this malware does

n8n-nodes-healthmon ships as a purported n8n health-monitoring node but its index.js binds an HTTP server on 0.0.0.0:41111 that reads a JSON body and passes the c field directly to child_process.exec, giving any network-reachable party arbitrary command execution on the installer's host. The listener is started with no authentication and no loopback restriction. package.json declares postinstall: node postinstall.js || true, and postinstall.js does require('./index.js'), so the listener launches automatically during npm install without user consent. The same code path also runs when n8n loads the node via dist/HealthMonNode.node.js, so re-exposure occurs on every n8n startup. The health-monitoring framing is a cover story; the actual behavior is a persistent, world-reachable backdoor.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7b6e9b877fe50a6a5cdf3cd0af73e755973a6eecb2940424618a5edfdc9443ed

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for n8n-nodes-healthmon (version 1.0.0).
If you installed it — respond
n8n-nodes-healthmon establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If n8n-nodes-healthmon 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. n8n-nodes-healthmon on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020341

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks n8n-nodes-healthmon-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database