NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @doaction published 15 malicious packages. See the full campaign →
Malicious package

@doaction/paynpm

Advisory published Updated

@doaction/pay is a confirmed malicious npm package (MAL-2026-5375) that steals credentials and exfiltrates sensitive data (malicious versions 9.9.9, 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @doaction/pay (npm)

MAL-2026-5375
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @doaction/pay

What this malware does

@doaction/pay 9.9.9 declares "preinstall": "node scripts/postinstall.js" in package.json, which requires @doaction/shared/bin/postinstall.js and runs automatically on npm install with no user consent. The package's stated purpose is Datadog environment telemetry, and src/index.js wraps collectEnv and sendToDatadog from the shared dependency. At install time no caller-supplied API key or destination exists, so the preinstall execution path reads installer environment variables and ships them to a destination hardcoded inside the transitive dependency. Two additional concerns corroborate intent: (1) the lifecycle script invoked from preinstall is misleadingly named scripts/postinstall.js, while an unused scripts/preinstall.js of similar shape sits alongside it — a reviewer-confusion pattern; (2) the 9.9.9 version with an 'internal testing' description is consistent with a coordinated package set targeting installer environments rather than a normal release.

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.

Malicious versions

2 flagged
9.9.999.99.99

Indicators of compromise (SHA-256)

ea0e4224fea42b723c5ddeed073192af51d5fec4e00b596f37df2f4e3585f4b5
a0a6f5d2258f3a2b373b66990c85dbbe09e260c25ade58d6f44cfb53b9e09616
a6212e535568abe842341e0c1ddc4548ac0146e1bbce874e0a45d282f4d196a1
66be5e0fe7c87db433a786ebffe006e89378ddc687056638b962b421b8794f2a
94ec95e460ba16497749775ca5e0bac92e4013e2297dd506bb2b99254acffaf3

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @doaction/pay (2 malicious versions).

  2. If you installed it — respond

    @doaction/pay is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @doaction/pay was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @doaction/pay on npm has been identified as a malicious package (versions 9.9.9, 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-55rv-c39c-944mIN-MAL-2026-004988IN-MAL-2026-004987IN-MAL-2026-005188IN-MAL-2026-005187

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @doaction/pay-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@doaction/pay (npm) malicious package — MAL-2026-5375 | O3 Security