Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

n8n-nodes-data-transformer-utilsnpm

n8n-nodes-data-transformer-utils is a confirmed malicious npm package (MAL-2026-16418) 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-data-transformer-utils (npm)

MAL-2026-16418
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall n8n-nodes-data-transformer-utils

What this malware does

The package's postinstall.js runs automatically on npm install and combines child_process.execSync with http/https.request and multiple curl invocations to collect host information (including reads of /etc/hosts) and POST/GET the results to a remote endpoint. The file uses a hardcoded hostname target, executes shell commands to gather system data, and transmits it over HTTP without any relation to the package's advertised data-transformation purpose. The package name mimics the n8n community-node naming convention, providing a lure for users seeking legitimate n8n utilities. Installing the package on default settings triggers immediate host reconnaissance and outbound exfiltration to an attacker-controlled destination.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

77b996187dc49e5591ddf3cef428be3a9309e7f5bab48bd4698aed2be0c3dfb0

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for n8n-nodes-data-transformer-utils (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-data-transformer-utils across your stack and pipelines.

  2. If you installed it — respond

    n8n-nodes-data-transformer-utils 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.

  3. Did it already run?

    If n8n-nodes-data-transformer-utils 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.

  4. How O3 protects you

    O3 blocks n8n-nodes-data-transformer-utils 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-data-transformer-utils 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-020315

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

n8n-nodes-data-transformer-utils (npm) malicious package — MAL-2026-16418 | O3 Security