Malicious code in @years20/n8n-nodes-utils-helper-b (npm)
The npm package @years20/n8n-nodes-utils-helper-b version 1.0.0 contains malicious code that executes during installation and runtime. It collects system information and SSH public key data, encodes it, and exfiltrates it to a remote server with TLS verification disabled. Additionally, it writes a private SSH key to a temporary file and attempts to SSH into localhost on specific ports to find pre-provisioned access on developer and CI hosts. This behavior enables persistent command and control capabilities and potential lateral movement within affected environments.
AI Analysis
Technical Summary
The malicious code in @years20/[email protected] executes on npm install (postinstall) and on require/import of the package's main entry files (callback.js and index.js). It runs system commands to gather user ID, hostname, and WSL detection, reads the SSH Ed25519 public key, base64-encodes this data, and sends it via an unverified TLS GET request to a remote URL. The payload is structured as a shell command that can be replayed by a command and control server. The scripts also write an embedded base64 OpenSSH Ed25519 private key to /tmp/pk with restrictive permissions and attempt SSH authentication to localhost on ports 22495 and 22 using a list of common usernames, aiming to find pre-configured SSH access on developer and CI machines. This ensures execution even if npm install is run with --ignore-scripts, as the package is loaded at runtime by n8n.
Potential Impact
This malicious package can exfiltrate sensitive system and SSH key information to an attacker-controlled server, potentially compromising system confidentiality. The embedded private key and SSH brute force attempts to localhost allow the attacker to gain unauthorized access to local services, enabling lateral movement or persistence on developer and CI hosts. The disabling of TLS verification increases the risk of man-in-the-middle interception during data exfiltration. Overall, this poses a significant risk to the integrity and confidentiality of affected systems.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package. Users should immediately remove @years20/n8n-nodes-utils-helper-b version 1.0.0 from their environments and avoid installing or importing this package. Verify that no unauthorized SSH keys have been added to /tmp or other locations and audit local SSH access logs for suspicious activity. Consider rotating SSH keys and credentials if this package was installed. Monitor for any unexpected network connections to the indicated remote domain. Since this is a malicious package, remediation involves removal and incident response rather than patching.
Malicious code in @years20/n8n-nodes-utils-helper-b (npm)
Description
The npm package @years20/n8n-nodes-utils-helper-b version 1.0.0 contains malicious code that executes during installation and runtime. It collects system information and SSH public key data, encodes it, and exfiltrates it to a remote server with TLS verification disabled. Additionally, it writes a private SSH key to a temporary file and attempts to SSH into localhost on specific ports to find pre-provisioned access on developer and CI hosts. This behavior enables persistent command and control capabilities and potential lateral movement within affected environments.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The malicious code in @years20/[email protected] executes on npm install (postinstall) and on require/import of the package's main entry files (callback.js and index.js). It runs system commands to gather user ID, hostname, and WSL detection, reads the SSH Ed25519 public key, base64-encodes this data, and sends it via an unverified TLS GET request to a remote URL. The payload is structured as a shell command that can be replayed by a command and control server. The scripts also write an embedded base64 OpenSSH Ed25519 private key to /tmp/pk with restrictive permissions and attempt SSH authentication to localhost on ports 22495 and 22 using a list of common usernames, aiming to find pre-configured SSH access on developer and CI machines. This ensures execution even if npm install is run with --ignore-scripts, as the package is loaded at runtime by n8n.
Potential Impact
This malicious package can exfiltrate sensitive system and SSH key information to an attacker-controlled server, potentially compromising system confidentiality. The embedded private key and SSH brute force attempts to localhost allow the attacker to gain unauthorized access to local services, enabling lateral movement or persistence on developer and CI hosts. The disabling of TLS verification increases the risk of man-in-the-middle interception during data exfiltration. Overall, this poses a significant risk to the integrity and confidentiality of affected systems.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package. Users should immediately remove @years20/n8n-nodes-utils-helper-b version 1.0.0 from their environments and avoid installing or importing this package. Verify that no unauthorized SSH keys have been added to /tmp or other locations and audit local SSH access logs for suspicious activity. Consider rotating SSH keys and credentials if this package was installed. Monitor for any unexpected network connections to the indicated remote domain. Since this is a malicious package, remediation involves removal and incident response rather than patching.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13910
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7c9b2ebf8831d539cdb748
Added to database: 08/12/2026, 16:11:26 UTC
Last enriched: 08/12/2026, 16:25:23 UTC
Last updated: 08/12/2026, 16:25:23 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.