NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @years19 published 25 malicious packages. See the full campaign →
Malicious package

@years19/n8n-nodes-utils-helper-enpm

Advisory published Updated

@years19/n8n-nodes-utils-helper-e is a confirmed malicious npm package (MAL-2026-13888) 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 @years19/n8n-nodes-utils-helper-e (npm)

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

What this malware does

Package presents itself as an n8n community utility node, but the shipped node file (nodes/PwnNode.node.js) is a 213-byte stub. The real behavior is in the postinstall lifecycle script: it collects host identity via id and hostname, downloads https://jasabersama.id/assets/cache/.theme-backup/dl/multidict.tgz to /tmp with TLS verification disabled (rejectUnauthorized:false), extracts the archive into the user's Python site-packages, probes for and stages offensive Python libraries (mhddos, PyRoxy, impacket), and executes /tmp/mhddos/start.py. Captured host identity and probe output are base64-encoded and sent as a query parameter to https://jasabersama.id/portfolio-data.php, again with TLS verification disabled. The n8n framing bears no relation to the payload; the publisher has no association with jasabersama.id.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

d5383b810a9933c1d20ffbcb7fbc4f7477c6603e5e7fe955d8380f765be69d8b

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @years19/n8n-nodes-utils-helper-e (version 1.0.0).

  2. If you installed it — respond

    Remove @years19/n8n-nodes-utils-helper-e 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 @years19/n8n-nodes-utils-helper-e was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @years19/n8n-nodes-utils-helper-e 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-017607

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years19/n8n-nodes-utils-helper-e-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
@years19/n8n-nodes-utils-helper-e (npm) malicious package — MAL-2026-13888 | O3 Security