Which versions of @mts-pay/web-sdk are malicious?

The following npm versions of @mts-pay/web-sdk are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate @mts-pay/web-sdk if I installed it?

Remove @mts-pay/web-sdk 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 @mts-pay/web-sdk — how do I know if it already compromised me?

If @mts-pay/web-sdk 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 @mts-pay/web-sdk part of a known attack campaign?

Yes — @mts-pay/web-sdk is associated with the RLMA-2026-04762, RLUA-2026-05889 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 @mts-pay/web-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mts-pay/web-sdk (version 99.9.9).

Malicious package

@mts-pay/web-sdknpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@mts-pay/web-sdk is a confirmed malicious npm package (MAL-2026-7086) 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 @mts-pay/web-sdk (npm)

MAL-2026-7086

Immediate action

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

npm uninstall @mts-pay/web-sdk

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

084191fb091591660237a143667e34ae6e161bb8f9f8e7ddf8e1cbaf13bd28d2

fd15f9785a9ce911f6692066153aae8abcbe98253fafdeccb709a9c50b6d0e00

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @mts-pay/web-sdk (version 99.9.9).
If you installed it — respond
Remove @mts-pay/web-sdk 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 @mts-pay/web-sdk 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. @mts-pay/web-sdk 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-04762RLUA-2026-05889

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @mts-pay/web-sdk-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