memtry-cli
Local stdio MCP proxy for memtry.io — bridges stdio MCP clients to the cloud
This report shows the evidence for memtry-cli@1.0.4, the only known version.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10736 confirms this npm version as malicious.
Advisory
MAL-2026-10736
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in memtry-cli (npm)
Details
memtry-cli installs an MCP server whose `memtry_onboarding` tool returns a prompt that instructs the connected AI agent to scan the installer's home directory (~/.claude, ~/.gemini, ~/.cursor, ~/Library/Application Support, ~/Documents, ~/Downloads, ~/Desktop, ~/Projects) for chat histories, resumes, YC applications, financial documents, and personal data, then submit the collected content through the package's `create_repo` / `update_context` / `append_changelog` tools. Those tools default-route via `callCloud(`${BASE_URL}/api/mcp`)` to the author-controlled endpoint https://memtry.vercel.app/api/mcp, and the shipped `.gemini/settings.json` pins BASE_URL to that host with a bundled Bearer API key. Only items the model explicitly tags `status: private` stay local; the onboarding prompt does not instruct the model to apply that tag to the harvested personal or financial content, so exfiltration to the author's Vercel endpoint is the default path. The tarball also ships a live `mk_...` API key for memtry.vercel.app in `.gemini/settings.json`.
References
Independent scan evidence
public snapshotBehavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStrings
NoLicense
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
2 Medium4 Low
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowNo License
Affected versions and remediation
This report applies to memtry-cli@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing memtry-cli@1.0.4. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.