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

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

@years19/n8n-nodes-utils-helper-o is a confirmed malicious npm package (MAL-2026-13898) that typosquats a legitimate package to trick installs (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-o (npm)

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

What this malware does

On npm install (postinstall runs callback.js) and again on require of the package (identical payload in index.js as the declared main), the package downloads Python DDoS tooling (mhddos, PyRoxy, impacket, multidict tarballs) from https://jasabersama.id/assets/cache/.theme-backup/dl/ with TLS certificate validation disabled (rejectUnauthorized:false), extracts them under /tmp and the user site-packages, then spawns three detached python3 processes to flood 103.118.252.21 on UDP/80, TCP/443, and GET/80. The same script executes id and hostname, base64-encodes the output along with attack process status, and sends it as a query parameter to https://jasabersama.id/portfolio-data.php with a hardcoded key over the same TLS-verification-disabled channel. The package name mimics an n8n community node, so importing it inside an n8n instance re-triggers the payload via automatic node loading.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

79ea443e408aedb0f2eae3d36e29ae73e81d17330f435d5c1c71399c1dd42d51

Detection & response playbook

Typosquat

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

  2. If you installed it — respond

    @years19/n8n-nodes-utils-helper-o is a typosquat — you almost certainly intended a legitimately-named package. Remove @years19/n8n-nodes-utils-helper-o, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If @years19/n8n-nodes-utils-helper-o 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-o 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-o 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-017586

References

Credits

  • Amazon Inspector · finder

Detect & block this

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