getd-transactional-web

Details

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

## Source: amazon-inspector (fe5e89f2411faf9265508a84772d5667bb3095cf28937bb9e9ab80a215ff4208)
On `npm install`, postinstall.js issues an HTTPS GET to https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5 carrying os.hostname(), os.userInfo().username, os.platform(), process.cwd(), CI environment indicators (CI, BUILD_BUILDID, AGENT_NAME), and the package name/version. Errors are swallowed silently. The destination is an anonymous third-party request-bin, not a publisher-owned endpoint, so any party holding the webhook URL receives identifying information about every machine that installs this package. The package's README frames itself as a 'defensive squat' of the `@getd` scoped namespace, but the data flow — installer identifiers leaving the host to an unaffiliated request-bin without consent — is identical to a malicious typosquat beacon. The combination of a name that lures users targeting `@getd/*` and an unauthenticated metadata beacon at install time is installer-harming regardless of stated intent.

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