Which versions of sd-pay-ts are malicious?

The following npm versions of sd-pay-ts are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate sd-pay-ts if I installed it?

Remove sd-pay-ts from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed sd-pay-ts — how do I know if it already compromised me?

If sd-pay-ts was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is sd-pay-ts part of a known attack campaign?

Yes — sd-pay-ts is associated with the GHSA-x35w-cc75-vw5x, RLMA-2025-06467, RLUA-2026-01550 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sd-pay-ts across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sd-pay-ts (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sd-pay-ts across your stack and pipelines.

Malicious package

sd-pay-tsnpm

Malicious code in sd-pay-ts (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192563

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sd-pay-ts

What this malware does

The package sd-pay-ts was found to contain malicious code.

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

1 flagged

999.0.0

Indicators of compromise (SHA-256)

c21a3fe3b0a1df838e4d8b768b5dcc2cf3831bea34c8527fd9e8493ab480bdd7

7543455a42022174e965eac8f842494f5ad7eb1e0755dfd01035529d63d7a5ff

af8117684352bba6ca3ac4172a2afed5af8a2af5973b33d57f94e7c015c9658f

119f30ed106d21c1ded3c8481c0f41d2bb0188ef7f89fff07c61609b8a59b101

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sd-pay-ts (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sd-pay-ts across your stack and pipelines.
If you installed it — respond
Remove sd-pay-ts from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If sd-pay-ts was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks sd-pay-ts before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. sd-pay-ts on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x35w-cc75-vw5xRLMA-2025-06467RLUA-2026-01550

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sd-pay-ts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring