취약점

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

Source: amazon-inspector (f2bbb2ac2e6e954090b85e740a9a10a8267429800107690dfbde310c0b3d9fc7)

Pattern-based matches fired on the strings 'ping' and 'POST' co-occurring in the package's bundled output (dist/index.cjs, dist/index.js, dist/server.cjs, dist/server.js) and in src/backends/collector/receiver.ts. The package advertises itself as an MCP (Model Context Protocol) server with a telemetry/collector backend, where 'ping' likely refers to OpenTelemetry/health-check semantics and POST refers to receiver endpoints — not a hardcoded exfiltration channel. No attacker-controlled domain, credential read, lifecycle hook, or environment scraping was observed. Routing to human review because traced-code corroboration of intent was not available and the keyword co-occurrence alone is insufficient to confirm or rule out malicious behavior in the bundled output.

Source: ghsa-malware (9437d9a4154fd87a4ce99716b267b0a16d3277af57cf02dc7462e6ad149c9d68)

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.