Malicious code in autotel-terminal (npm)
Source: amazon-inspector
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
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
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.
