Which versions of memtry-cli are malicious?

The following npm versions of memtry-cli are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate memtry-cli if I installed it?

memtry-cli 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 memtry-cli — how do I know if it already compromised me?

If memtry-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is memtry-cli part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for memtry-cli (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging memtry-cli across your stack and pipelines.

Malicious package

memtry-clinpm

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

Malicious code in memtry-cli (npm)

MAL-2026-10736

Immediate action

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

npm uninstall memtry-cli

What this malware does

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.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

11638a6b1b7876a94ef23285cb88f0127c003bb5e4d786dbaba5c30a9cbdfdb7

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for memtry-cli (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging memtry-cli across your stack and pipelines.
If you installed it — respond
memtry-cli 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 memtry-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks memtry-cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. memtry-cli on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010783

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks memtry-cli-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