autotel-mcp-instrumentation

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (d430094afb9dc367c9a2a0477eea7bba4074cf3eed9f6f2861a0e82f79706ee4)
No concrete installer-harm signals were identified for this package version. No lifecycle hooks, network destinations, credential reads, or other supply-chain attack fingerprints were surfaced in the available evidence. Routing for human review given incomplete coverage; a reviewer should confirm the package's lifecycle scripts and main-module top-level behavior before publishing a verdict.

## Source: ghsa-malware (5c64859e391f8cefcdc5dd1b66f0364b7821a5dbc3f1493a5cfb4a168ad6a4cf)
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.

Compromised versions (6)

• 29.0.2
• 30.0.5
• 31.0.1
• 32.0.1
• 33.0.2
• 34.0.1

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.