Which versions of mmagrt are malicious?

The following npm versions of mmagrt are flagged malicious: 0.1.10. Treat any of these as compromised.

How do I remediate mmagrt if I installed it?

mmagrt is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed mmagrt — how do I know if it already compromised me?

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

Yes — mmagrt is associated with the IN-MAL-2026-010718 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 mmagrt across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mmagrt (version 0.1.10).

Malicious package

mmagrtnpm

Advisory published Jul 16, 2026Updated Jul 16, 2026

mmagrt is a confirmed malicious npm package (MAL-2026-10737) that steals credentials and exfiltrates sensitive data (malicious version 0.1.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mmagrt (npm)

MAL-2026-10737

Immediate action

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

npm uninstall mmagrt

What this malware does

The npm package advertises itself as a 'VPS routine scheduler' but ships prebuilt Rust binaries (mmagrt and mmagrt-mcp) for darwin-arm64, darwin-x64, linux-arm64, linux-x64, and win32-x64 that snapshot the installer's WhatsApp Web session state and Google credentials from the local machine and POST them to a hardcoded anonymous Cloudflare-tunnel URL (participate-strips-occurred-bedrooms.trycloudflare.com). The exfil endpoint is embedded in all five per-platform binaries alongside strings such as 'WhatsApp credential not snapshotted', 'Google credential not snapshotted', 'auto-cred snapshot failed', '.mmagrt-snapshot/waa-export.json', and 'uploading -byte snapshot for routine' with '/routines/' and '/runs/' path fragments. The bin launcher bin/mmagrt.js routes the install subcommand to mmagrt-mcp, which writes the credential-harvesting binary into ~/Library/Application Support/Claude/claude_desktop_config.json (and platform equivalents) as an MCP stdio server, causing Claude Desktop to spawn the binary automatically on every launch and providing ongoing execution for the exfil agent. The stolen data class (WhatsApp session, Google credentials) is unrelated to the package's stated scheduler purpose, and the trycloudflare.com destination is anonymous, mutable infrastructure rather than a first-party endpoint.

Malicious versions

1 flagged

0.1.10

Indicators of compromise (SHA-256)

f7eddaa3f964de5ebd63c3272f8abe021b60402b5fde4d4437cc254c99a8211a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for mmagrt (version 0.1.10).
If you installed it — respond
mmagrt is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If mmagrt 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. mmagrt on npm has been identified as a malicious package (version 0.1.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010718

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mmagrt-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database