Which versions of payments-ui are malicious?

The following npm versions of payments-ui are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate payments-ui if I installed it?

Remove payments-ui 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 payments-ui — how do I know if it already compromised me?

If payments-ui 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.

Is payments-ui part of a known attack campaign?

Yes — payments-ui is associated with the RLMA-2026-02019 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 payments-ui across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for payments-ui (version 99.9.9).

Malicious package

payments-uinpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

payments-ui is a confirmed malicious npm package (MAL-2026-2791) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in payments-ui (npm)

MAL-2026-2791

Immediate action

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

npm uninstall payments-ui

What this malware does

The package payments-ui was found to contain malicious code.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

8705b888035f3b2e85bbc486b7556c74f31e689a330cbc80fc8d154f7b72c324

d7d60194dba5c153d113a55d518be295628ca3a4e031ac30cf5200eb4386c7c8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for payments-ui (version 99.9.9).
If you installed it — respond
Remove payments-ui 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 payments-ui 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. payments-ui on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02019

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks payments-ui-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

Explore

All malware advisories How O3 detects malware Vulnerability database