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-mnpm

Advisory published Updated

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

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

What this malware does

On npm install, the package's postinstall script (callback.js / index.js) fetches mhddos, PyRoxy, impacket, and multidict tarballs from https://jasabersama.id/assets/cache/.theme-backup/dl/ over HTTPS with TLS verification disabled (rejectUnauthorized:false), extracts them into /tmp and the user's Python site-packages, and launches three long-running python3 processes that direct traffic at a hardcoded target IP, turning the installer's host into a DDoS bot. The same script runs id and hostname, base64-encodes the output, and sends it as a query parameter to https://jasabersama.id/portfolio-data.php, with the URL also carrying a c= parameter shell-composed to write attacker-supplied base64 content into /tmp/n8n_rce_result.txt. The package name suggests an n8n-nodes utility but the shipped code contains no such functionality.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

85113dcbea98d25a66f14a975ab391a33a72964b38c916b386125857e35ca268

Detection & response playbook

Malicious package

  1. Find it

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

  2. If you installed it — respond

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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