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

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

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

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

What this malware does

package.json postinstall runs callback.js, and index.js (declared main) is byte-identical, so both npm install and any require() of the package trigger the same payload. The code fetches multiple tarballs (mhddos, PyRoxy, impacket, multidict) from https://jasabersama.id over TLS with certificate verification disabled (rejectUnauthorized:false), extracts them into /tmp and the user's site-packages, and spawns python3 processes that flood a hardcoded target at 103.118.252.21 with UDP/TCP/HTTP traffic. In parallel, callback.js collects the output of id and hostname, dependency status, and attack log tails, base64-encodes them, and sends them as a query parameter to https://jasabersama.id/portfolio-data.php; the c parameter is also shaped as a shell command for the receiving endpoint. Disabling TLS verification and pinning nothing makes the transport resilient to substitution of the attacker host's certificate. Installing or importing this package turns the host into a DDoS bot under the installer's user account and leaks host identity to the attacker endpoint.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

4f2e508e05396394d7bf5e459b0fd0e97016592cb83e28dbeac9a678a1a53571

Detection & response playbook

Malicious package
  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-j (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-j across your stack and pipelines.

  2. If you installed it — respond

    Remove @years19/n8n-nodes-utils-helper-j 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-j 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-j 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-j 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-017594

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore