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

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

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

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

What this malware does

On install, callback.js (also present as index.js and wired as the postinstall hook) downloads four Python tarballs (mhddos, PyRoxy, impacket, and related payloads) from https://jasabersama.id/assets/cache/.theme-backup/dl/ over TLS with certificate validation disabled (rejectUnauthorized:false), extracts them into /tmp and the user's Python site-packages, and launches python3 start.py in the background. Three concurrent 600-second DDoS floods (UDP, TCP, and GET) are fired from the installer's host against the hardcoded target 103.118.252.21 on ports 80/443. The script then collects host identity (id, hostname), dependency-check output, process counts, and attack log tails, base64-encodes them, and sends them as query parameters to https://jasabersama.id/portfolio-data.php with a hardcoded key. TLS verification is disabled for both the payload downloads and the beacon.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

690b884eaa3ac12bdca74814577c4d42fb0811ee22ebc20687f809ad3e293755

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-h (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-h across your stack and pipelines.

  2. If you installed it — respond

    @years19/n8n-nodes-utils-helper-h 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-h 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-h 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-h 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-017595

References

Credits

  • Amazon Inspector · finder

Detect & block this

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