# MAL-2026-5469: Malicious code in getd-transactional-web (npm)


- **Type:** Malicious package
- **Package:** `getd-transactional-web` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-7f9r-465j-5hj6

## What is MAL-2026-5469?

MAL-2026-5469 is a malicious package in getd-transactional-web, published on 9 Jun 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-5469?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5469 is a malicious package: getd-transactional-web (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5469/ (Markdown: https://insights.sbomify.com/MAL-2026-5469/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5469

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5469/
Summaries are generated and may contain mistakes; the official description above is the record.