getd-handler-api

Details

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

## Source: amazon-inspector (83398d27bb84d47296f796b4b2e6e9b5a0efc474add2e57592455e7d5d54eab5)
On `npm install`, postinstall.js collects the installer's hostname, username, platform, current working directory, and CI-related environment variables, then sends them via HTTPS GET to https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5 (postinstall.js line 18). Errors are silenced so the beacon runs invisibly during install. Although package.json describes itself as a 'defensive' typosquat placeholder for the @getd/* scope, installer-side identifiers leave the machine unconditionally without consent on every install, which is unauthorized data collection regardless of stated intent. The combination of a typosquat-shaped name and an automatic install-time phone-home is the standard namespace-abuse exfil pattern.

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

Compromised versions (1)

• 0.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.