Which versions of mms-thin-client are malicious?

The following npm versions of mms-thin-client are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate mms-thin-client if I installed it?

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

If mms-thin-client 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.

How do I find mms-thin-client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mms-thin-client (2 malicious versions).

Malicious package

mms-thin-clientnpm

Advisory published Oct 30, 2025Updated Oct 1, 2026

mms-thin-client is a confirmed malicious npm package (MAL-2025-49231) that executes malicious code on install (malicious versions 0.0.1-security, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mms-thin-client (npm)

MAL-2025-49231

Immediate action

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

npm uninstall mms-thin-client

What this malware does

The package mms-thin-client was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

57427ccebae288ec20571b2713f7e71b7cf97044e30896db254f9371e32764f3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for mms-thin-client (2 malicious versions).
If you installed it — respond
Remove mms-thin-client 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 mms-thin-client 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. mms-thin-client on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mms-thin-client-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