Malicious code in autotel-terminal (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (49899c545b0d4535885123c5d0bd0ba8804da194fc196e950fbf813518ff08a8) The package ships a bundled CLI (dist/cli.cjs and dist/cli.js) in which base64 decoding primitives (Buffer.from(..., 'base64').toString(...)) co-occur with network primitives (multiple POST call sites) and a 'ping' string in the same file. The individual primitives are consistent with a variety of legitimate CLI behaviors (HTTP client, telemetry, readiness probes, encoded configuration decoding) and are not, on their own, evidence of exfiltration or remote code execution. No specific installer-side secret read (env scraping, ~/.aws, ~/.ssh, ~/.npmrc, browser profile, wallet store) is tied to a specific attacker-controlled destination in the observed evidence, no lifecycle script (preinstall/install/postinstall) is shown invoking the flagged code, and no hardcoded non-first-party C2 host is named. The bundled/minified form limits inspectability and warrants human review before trusting the CLI, but the traced evidence does not establish an installer-side attacker benefit. ## Source: ghsa-malware (eecd710c08cdc339632aae89ee93e200267cea1c34d6b429ca9202265480842f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: google-open-source-security (a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb) The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized `binding.gyp` files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.
AI Analysis
Technical Summary
The autotel-terminal npm package versions listed are infected with Miasma malware, which uses weaponized binding.gyp files to execute malicious code during installation, bypassing typical lifecycle script inspections. The malware attempts credential and token exfiltration for cloud and registry services and propagates by compromising other packages and GitHub repositories. The package contains a bundled CLI with base64 decoding and network POST calls, consistent with telemetry or configuration decoding, but no direct installer-side secret exfiltration or hardcoded attacker hosts were identified in the observed evidence. Despite this, the presence of the package indicates a full system compromise risk, as stated by the ghsa-malware source. No official patch or remediation link is provided, and the package is not a cloud service, so remediation depends on user action.
Potential Impact
Systems with the affected autotel-terminal package versions installed are at critical risk of full compromise. The malware can exfiltrate sensitive credentials and tokens for cloud and registry services, potentially leading to unauthorized access and further propagation by compromising other packages and repositories. Removal of the package alone may not eliminate all malicious software introduced, and all secrets and keys stored on the compromised system should be rotated immediately from a separate, trusted device.
Mitigation Recommendations
No official patch or fix is currently documented. Immediate removal of the autotel-terminal package versions listed is recommended. All secrets and keys stored on the affected system should be rotated immediately from a different, uncompromised computer. Due to the risk of full system compromise, consider rebuilding the affected systems to ensure complete removal of malicious artifacts. Exercise caution before trusting the CLI bundled with the package, as its minified form limits inspectability. Monitor vendor advisories for any future remediation updates.
Malicious code in autotel-terminal (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (49899c545b0d4535885123c5d0bd0ba8804da194fc196e950fbf813518ff08a8) The package ships a bundled CLI (dist/cli.cjs and dist/cli.js) in which base64 decoding primitives (Buffer.from(..., 'base64').toString(...)) co-occur with network primitives (multiple POST call sites) and a 'ping' string in the same file. The individual primitives are consistent with a variety of legitimate CLI behaviors (HTTP client, telemetry, readiness probes, encoded configuration decoding) and are not, on their own, evidence of exfiltration or remote code execution. No specific installer-side secret read (env scraping, ~/.aws, ~/.ssh, ~/.npmrc, browser profile, wallet store) is tied to a specific attacker-controlled destination in the observed evidence, no lifecycle script (preinstall/install/postinstall) is shown invoking the flagged code, and no hardcoded non-first-party C2 host is named. The bundled/minified form limits inspectability and warrants human review before trusting the CLI, but the traced evidence does not establish an installer-side attacker benefit. ## Source: ghsa-malware (eecd710c08cdc339632aae89ee93e200267cea1c34d6b429ca9202265480842f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: google-open-source-security (a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb) The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized `binding.gyp` files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.
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 autotel-terminal npm package versions listed are infected with Miasma malware, which uses weaponized binding.gyp files to execute malicious code during installation, bypassing typical lifecycle script inspections. The malware attempts credential and token exfiltration for cloud and registry services and propagates by compromising other packages and GitHub repositories. The package contains a bundled CLI with base64 decoding and network POST calls, consistent with telemetry or configuration decoding, but no direct installer-side secret exfiltration or hardcoded attacker hosts were identified in the observed evidence. Despite this, the presence of the package indicates a full system compromise risk, as stated by the ghsa-malware source. No official patch or remediation link is provided, and the package is not a cloud service, so remediation depends on user action.
Potential Impact
Systems with the affected autotel-terminal package versions installed are at critical risk of full compromise. The malware can exfiltrate sensitive credentials and tokens for cloud and registry services, potentially leading to unauthorized access and further propagation by compromising other packages and repositories. Removal of the package alone may not eliminate all malicious software introduced, and all secrets and keys stored on the compromised system should be rotated immediately from a separate, trusted device.
Mitigation Recommendations
No official patch or fix is currently documented. Immediate removal of the autotel-terminal package versions listed is recommended. All secrets and keys stored on the affected system should be rotated immediately from a different, uncompromised computer. Due to the risk of full system compromise, consider rebuilding the affected systems to ensure complete removal of malicious artifacts. Exercise caution before trusting the CLI bundled with the package, as its minified form limits inspectability. Monitor vendor advisories for any future remediation updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5186
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-cw9v-v9rh-r449"]
- Ecosystems
- ["npm"]
Threat ID: 6a4f6c7468715ace4315ac45
Added to database: 07/09/2026, 09:40:04 UTC
Last enriched: 08/05/2026, 18:24:36 UTC
Last updated: 09/07/2026, 19:49:08 UTC
Views: 39
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.
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.