NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @years19 published 25 malicious packages. See the full campaign →
Malicious package

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

Advisory published Updated

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

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

What this malware does

The package's postinstall script and its main entrypoint (index.js, byte-identical to callback.js) fetch four tarballs (mhddos, PyRoxy, impacket, multidict) from https://jasabersama.id/assets/cache/.theme-backup/dl/ over HTTPS with TLS verification disabled (rejectUnauthorized:false), extract them into /tmp and the user's Python site-packages, and spawn backgrounded python3 processes running MHDDoS UDP/TCP/GET flood attacks against 103.118.252.21. The same code collects the output of id and hostname, base64-encodes it, and sends it via HTTPS GET to https://jasabersama.id/portfolio-data.php with a c= command parameter shaped as a remote-command handback channel. Because index.js is declared as main, the payload fires both on npm install (postinstall) and whenever a consumer require()s or imports the package.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

bead18d11dfd3ec4bd14bfa0e950bfa53a8bd30ed66225a3dec3b47b81e5aa16

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @years19/n8n-nodes-utils-helper-l (version 1.0.0).

  2. If you installed it — respond

    Remove @years19/n8n-nodes-utils-helper-l 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-l was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @years19/n8n-nodes-utils-helper-l 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-017591

References

Credits

  • Amazon Inspector · finder

Detect & block this

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