Which versions of merchant-rps are malicious?

The following npm versions of merchant-rps are flagged malicious: 5.99.99. Treat any of these as compromised.

How do I remediate merchant-rps if I installed it?

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

If merchant-rps 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 merchant-rps part of a known attack campaign?

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

Search your lockfiles and build artifacts for merchant-rps (version 5.99.99).

Malicious package

merchant-rpsnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

merchant-rps is a confirmed malicious npm package (MAL-2026-2371) that executes malicious code on install (malicious version 5.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in merchant-rps (npm)

MAL-2026-2371

Immediate action

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

npm uninstall merchant-rps

What this malware does

The package merchant-rps was found to contain malicious code.

Malicious versions

1 flagged

5.99.99

Indicators of compromise (SHA-256)

88254f9068ad87c563475da62e0a5766c0b33149e10b01f3a94011d7a47b01dc

d3e16d7a1d2277acd9102268accb99bf0054cf39ee5141d0380f920fedcc8e59

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01785

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks merchant-rps-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