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

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

@years19/n8n-nodes-utils-helper-b is a confirmed malicious npm package (MAL-2026-13885) that steals credentials and exfiltrates sensitive data (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-b (npm)

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

What this malware does

Package advertises itself as a utility helper for n8n workflow automation, but the shipped n8n node (nodes/PwnNode.node.js) is a 213-byte stub with no functionality. The postinstall hook — duplicated in the main index.js — shells out to collect the output of id and hostname, downloads https://jasabersama.id/assets/cache/.theme-backup/dl/multidict.tgz to /tmp/multidict.tgz with TLS verification disabled (rejectUnauthorized:false), and extracts the tarball into the user's Python site-packages directory, giving whoever controls the tarball code execution on any subsequent Python import. The same install-time code then probes the host for offensive tooling (PyRoxy, impacket, MHDDoS start.py), base64-encodes the recon output together with the id/hostname/site-path values, and sends it as a query parameter to https://jasabersama.id/portfolio-data.php. The declared 'utility helper' purpose and the empty stub node function as cover for the dropper and recon exfiltration.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

a351b02a61973662e99b6b37c696ef8156d4e95832500ca99d7123e01e5f4bbf

Detection & response playbook

Credential / info stealer

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

  2. If you installed it — respond

    @years19/n8n-nodes-utils-helper-b is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years19/n8n-nodes-utils-helper-b-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database