Malicious code in autotel-terminal (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (47ab3c608b6bea332dc57224c5929d54d923655f3bd225ff30e25c3406b8a9a5) The package's bundled CLI files (dist/cli.cjs and dist/cli.js) contain co-occurring tokens 'ping' and 'POST' that triggered a network/command exfiltration pattern match. These tokens are commonly produced by minified/bundled CLI tooling that includes both shell-spawn helpers and HTTP request helpers, and keyword proximity in a single bundled file is the weakest evidence shape. No traced-code evidence corroborates that these tokens are wired together into an exfiltration path, no install-time lifecycle hook is documented, and no attacker-controlled destination has been identified in the cited evidence. Routing to human review so a reviewer can de-bundle the relevant spans of dist/cli.cjs around line 3260 and dist/cli.js around line 3253 to confirm whether the 'ping' and 'POST' tokens correspond to a benign CLI feature (e.g. health-check + telemetry/upload) or a real exfiltration sink. ## 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 contains malicious code known as Miasma malware, which spreads through weaponized binding.gyp files executed during package installation. This malware attempts credential and token exfiltration for cloud and registry services and propagates by compromising additional packages and repositories. Detection was triggered by network/command exfiltration pattern matches involving 'ping' and 'POST' tokens in bundled CLI files, though no direct exfiltration path was confirmed. The malware grants attackers full control over infected systems, necessitating immediate secret rotation and package removal.
Potential Impact
Systems with the affected autotel-terminal package versions installed are considered fully compromised, with attackers potentially having full control. All secrets and keys stored on such systems may have been exfiltrated, requiring immediate rotation from a secure environment. Removing the package alone does not guarantee removal of all malicious software introduced by the malware.
Mitigation Recommendations
Remove the affected autotel-terminal package versions immediately. Rotate all secrets and keys from a different, uncompromised system. Due to the potential full system compromise, additional forensic analysis and remediation may be necessary. Patch status is not confirmed; check vendor advisories for updates. No official fix or patch is currently documented.
Malicious code in autotel-terminal (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (47ab3c608b6bea332dc57224c5929d54d923655f3bd225ff30e25c3406b8a9a5) The package's bundled CLI files (dist/cli.cjs and dist/cli.js) contain co-occurring tokens 'ping' and 'POST' that triggered a network/command exfiltration pattern match. These tokens are commonly produced by minified/bundled CLI tooling that includes both shell-spawn helpers and HTTP request helpers, and keyword proximity in a single bundled file is the weakest evidence shape. No traced-code evidence corroborates that these tokens are wired together into an exfiltration path, no install-time lifecycle hook is documented, and no attacker-controlled destination has been identified in the cited evidence. Routing to human review so a reviewer can de-bundle the relevant spans of dist/cli.cjs around line 3260 and dist/cli.js around line 3253 to confirm whether the 'ping' and 'POST' tokens correspond to a benign CLI feature (e.g. health-check + telemetry/upload) or a real exfiltration sink. ## 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 contains malicious code known as Miasma malware, which spreads through weaponized binding.gyp files executed during package installation. This malware attempts credential and token exfiltration for cloud and registry services and propagates by compromising additional packages and repositories. Detection was triggered by network/command exfiltration pattern matches involving 'ping' and 'POST' tokens in bundled CLI files, though no direct exfiltration path was confirmed. The malware grants attackers full control over infected systems, necessitating immediate secret rotation and package removal.
Potential Impact
Systems with the affected autotel-terminal package versions installed are considered fully compromised, with attackers potentially having full control. All secrets and keys stored on such systems may have been exfiltrated, requiring immediate rotation from a secure environment. Removing the package alone does not guarantee removal of all malicious software introduced by the malware.
Mitigation Recommendations
Remove the affected autotel-terminal package versions immediately. Rotate all secrets and keys from a different, uncompromised system. Due to the potential full system compromise, additional forensic analysis and remediation may be necessary. Patch status is not confirmed; check vendor advisories for updates. No official fix or patch is currently documented.
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"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c7468715ace4315ac45
Added to database: 07/09/2026, 09:40:04 UTC
Last enriched: 07/09/2026, 10:08:50 UTC
Last updated: 07/24/2026, 20:39:27 UTC
Views: 23
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.