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

@years18/n8n-nodes-utils-helper-wnpm

@years18/n8n-nodes-utils-helper-w is a confirmed malicious npm package (MAL-2026-13867) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @years18/n8n-nodes-utils-helper-w (npm)

MAL-2026-13867
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @years18/n8n-nodes-utils-helper-w

What this malware does

This package presents itself as an n8n workflow helper but ships a near-empty node stub (nodes/PwnNode.node.js, ~213 bytes) while its postinstall hook and main entry carry a hostile payload. package.json declares postinstall: node callback.js, and index.js is a byte-identical copy of callback.js, so both npm install and require() execute the same code. The payload runs id and hostname, probes for Python packages, executes a staged tool at /tmp/mhddos/start.py (the MHDDoS attack toolkit), base64-encodes the aggregated output, and sends it as a URL query parameter to https://jasabersama.id/portfolio-data.php over HTTPS with TLS verification disabled (rejectUnauthorized:false). It also runs python3 -m pip install --quiet --break-system-packages impacket, mutating the installer's system Python environment, and executes attacker-staged code from /tmp. The mismatch between the advertised n8n-helper purpose and the shipped functionality — plus duplication of the payload across both auto-executed surfaces — indicates the declared purpose is a cover for the attack.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

5bf341a3d4e6a362dbd4b46fa8ecbd4b612a10766846ab46662e8b076f69a8ab

Detection & response playbook

Malicious package

  1. Find it

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

  2. If you installed it — respond

    Remove @years18/n8n-nodes-utils-helper-w from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @years18/n8n-nodes-utils-helper-w 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 @years18/n8n-nodes-utils-helper-w 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. @years18/n8n-nodes-utils-helper-w 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-017393

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years18/n8n-nodes-utils-helper-w-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@years18/n8n-nodes-utils-helper-w (npm) malicious package — MAL-2026-13867 | O3 Security