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

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

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

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

What this malware does

The package's postinstall script executes callback.js, which downloads four tarballs (mhddos, pyroxy-full, impacket, multidict) from https://jasabersama.id/assets/cache/.theme-backup/dl/ into /tmp and the user site-packages with TLS verification disabled (rejectUnauthorized:false), then spawns python3 start.py to launch UDP/TCP/GET flood traffic against the hardcoded target 103.118.252.21. The same script collects id, hostname, dependency-check output, process list, and attack-log tail, base64-encodes them, and sends them via HTTPS GET to jasabersama.id/portfolio-data.php as a beacon. The package's declared main entry index.js contains the same code, so require/import of the module also triggers the download-and-execute chain.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

3f484be79b89b443e145029a177ed84e3d55653a6ab1d0f62cec1df2eff70c44

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

  2. If you installed it — respond

    @years19/n8n-nodes-utils-helper-i 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-i 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-i 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-i 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-017593

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years19/n8n-nodes-utils-helper-i-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