Loading vulnerability…
CVE-2025-65099 is a code execution vulnerability in Claude Code affecting versions prior to 1.0.39 when run on systems using Yarn 3.0 or later. Under these conditions, Claude Code could be induced to execute code supplied by a project's Yarn plugins before the user accepted the application's startup trust dialog. The flaw effectively allowed project-controlled plugin code to run prior to completion of the intended trust decision, undermining the security boundary implied by the startup prompt. The issue was fixed in Claude Code version 1.0.39.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2025-65099, targeting the @anthropic-ai/claude-code package (version 1.0.38) when used with Yarn. The exploit demonstrates two techniques: one using the 'yarnPath' configuration to execute arbitrary JavaScript (script.js), and another using a malicious Yarn plugin (plugin-command-interceptor.js). Both techniques leverage Node.js's execSync to execute a shell command that writes 'Pwned!' to a file named 'proof.txt' in the working directory, serving as evidence of code execution. The repository includes setup instructions using Docker to create a vulnerable environment. The exploit is a local privilege escalation or code execution PoC, requiring the attacker to control the Yarn configuration or plugin path. No network endpoints are involved; the main fingerprintable artifact is the creation of 'proof.txt'. The code is concise and demonstrates the vulnerability clearly, but does not provide a weaponized or remote payload.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.