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

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

@years19/n8n-nodes-utils-helper-f is a confirmed malicious npm package (MAL-2026-13889) that opens a backdoor for remote access (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-f (npm)

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

What this malware does

The package's postinstall (scripts.postinstall: node callback.js) collects host identity and environment fingerprint (output of id, hostname, Python user-site path with its contents filtered for offensive-tooling keywords such as pyroxy/impacket/multidict/socks/maxmind, presence of /tmp/mhddos and /tmp/implant, uptime), base64-encodes the result, and sends it as a query string to https://jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized: false). The request path also includes a hardcoded key k=S7k9xQ2mZj and a c= parameter carrying echo <b64> | base64 -d >> /tmp/n8n_rce_result.txt, matching a beacon/check-in shape for an attacker-controlled command channel. The package poses as an n8n community node (nodes/PwnNode.node.js exports only a stub description) while main (index.js) is identical to the postinstall exfil script, so both npm install and any require of the package trigger the beacon. The name mimics legitimate n8n-nodes-* community naming.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

0200e9a9dfdd3de819e8111363492aa235bd40790b89adc91a5d7e0a410ae120

Detection & response playbook

Backdoor / remote access

  1. Find it

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

  2. If you installed it — respond

    @years19/n8n-nodes-utils-helper-f establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If @years19/n8n-nodes-utils-helper-f 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 @years19/n8n-nodes-utils-helper-f 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. @years19/n8n-nodes-utils-helper-f 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-017606

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years19/n8n-nodes-utils-helper-f-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

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