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

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

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

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

What this malware does

The package advertises itself as an n8n utility helper and registers a trivial stub node (nodes/PwnNode.node.js), but its postinstall lifecycle script performs the actual behavior. On install it fetches a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/multidict.tgz with TLS verification disabled (rejectUnauthorized:false), extracts it into the user's Python site-packages directory, and invokes attack tooling from the dropped archive (PyRoxy, impacket, mhddos /tmp/mhddos/start.py). The same postinstall executes id and hostname on the installer's machine, base64-encodes the output together with results from the dropped payload, and sends them to https://jasabersama.id/portfolio-data.php via an https.get whose path smuggles a base64-piped shell command. Installing the package results in attacker-controlled code being written to the Python import path and executed on the installer's host, and installer identity/execution results being transmitted to the author-controlled endpoint.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

3bd60aaab1ca86f97939ddbea892feba63b7d911dd038a8d6f348ece5af3a76e

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

  2. If you installed it — respond

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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