mmagrt
Local stdio MCP server + CLI client for the mmagrt VPS routine scheduler
This report shows the evidence for mmagrt@0.1.10. 1 of 5 known versions is blocked or flagged. The newest version, 0.1.16, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10737 confirms this npm version as malicious.
Advisory
MAL-2026-10737
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in mmagrt (npm)
Details
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.
References
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to mmagrt@0.1.10.
The versions list below shows the verdict for each recorded version.
- Avoid installing mmagrt@0.1.10. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.