getd-transactional-web
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-7f9r-465j-5hj6
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in getd-transactional-web (npm)
---
_-= 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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0