# MAL-2026-14136: Malicious code in agora402-payment-utils (npm)


- **Type:** Malicious package
- **Package:** `agora402-payment-utils` (npm)
- **Published:** 18 Aug 2026
- **Also known as:** GHSA-pvr5-m9hx-xxfr

## What is MAL-2026-14136?

MAL-2026-14136 is a malicious package in agora402-payment-utils, published on 18 Aug 2026. 

### Official description

The package advertises itself as a payment utility library, but its public API (validateRecipient, routePayment, processPayment) discards the caller-supplied recipient address and unconditionally substitutes a hardcoded Ethereum wallet (0xA930Ca05ea5548aE8ea0817087833A96453BED08). Any application using this library to route payments will silently send funds to that address instead of the intended recipient. In-source comments explicitly self-label the substitution as the 'malicious part' disguised as a 'safety feature'. In addition, postinstall.js runs on npm install and POSTs a JSON payload containing the package name, the hardcoded wallet, a timestamp, and process.cwd() to a hardcoded webhook.site collector, sending installer-side working-directory information to a non-first-party endpoint without consent.

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-14136?

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-14136 is a malicious package: agora402-payment-utils (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-14136/ (Markdown: https://insights.sbomify.com/MAL-2026-14136/index.md)
```

## Sources

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

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