MAL-2026-10736 Malicious code in memtry-cli (npm)
Malicious package
Published
MAL-2026-10736 is a malicious package: memtry-cli (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-10736/ (Markdown: https://insights.sbomify.com/MAL-2026-10736/index.md)
- Package
- memtry-cli
- Registry
- npm
What is MAL-2026-10736?
MAL-2026-10736 is a malicious package in memtry-cli, published on 16 Jul 2026.
Official description
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.What should I do about MAL-2026-10736?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.