# MAL-2026-16162: Malicious code in n8n-nodes-sysdiag2 (npm)


- **Type:** Malicious package
- **Package:** `n8n-nodes-sysdiag2` (npm)
- **Published:** 14 Sep 2026

## What is MAL-2026-16162?

MAL-2026-16162 is a malicious package in n8n-nodes-sysdiag2, published on 14 Sep 2026. 

### Official description

The package advertises itself as an n8n community node for system diagnostics, but the shipped node module (dist/SysDiag.node.js) is an inert stub returning [{ok:true}] and the package's main is a one-line empty export. All behavior is implemented in a postinstall script that runs automatically on npm install. The postinstall collects host and environment data (env, id, hostname, /proc/1/cgroup, mount table, process capabilities) into /tmp/.be and posts it via wget --post-file to http://121.127.33.228:8443/env2 over plain HTTP. It also downloads http://121.127.33.228:8444/mn8n2 to /tmp/.mn2, chmod +x, and launches it detached via nohup, executing an opaque attacker-supplied binary on the installer's host. In parallel, it spawns a detached loop that connects nc to 121.127.33.228:443 with -e /bin/sh and reconnects every 7 seconds, providing a persistent interactive reverse shell to the operator of that IP. The three payloads share a single hardcoded bare IP unrelated to any legitimate n8n publisher and fire without user interaction on npm install.

The OpenSSF Package Analysis project identified 'n8n-nodes-sysdiag2' @ 2.0.0 (npm) as malicious.

It is considered malicious because:

- The package executes one or more commands associated with malicious behavior.

## What should I do about MAL-2026-16162?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-16162 is a malicious package: n8n-nodes-sysdiag2 (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-16162/ (Markdown: https://insights.sbomify.com/MAL-2026-16162/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-16162

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-16162/
Summaries are generated and may contain mistakes; the official description above is the record.