payments-notifications (npm) · Malicious Code
Affects payments-notificationsSource GCVE Database
Malicious package : remove payments-notifications and rotate any secrets on hosts that installed it.
Data as of 4 Nov 2026, 17:16 UTC
Malicious package
Published to npm · OSV MAL-2025-49390
What to do
Remove payments-notifications from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmpayments-notifications | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ec2ff3c7a16e539813080b53ccec2b3531078fed7382156c676025c1188b9c7c) The package payments-notifications was found to contain malicious code. ## Source: ossf-package-analysis (9c5b0d60c2bb18c0a072118e86869399843cb27d5642927e3d29c1567c968f18) The OpenSSF Package Analysis project identified 'payments-notifications' @ 2.0.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.