Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

RCE via git dependency lifecycle scripts bypass in pnpm v10

IdentifiersCVE-2025-69264CWE-693· Protection Mechanism Failure

pnpm v10.0.0 through v10.25 contains a bypass of its v10 security behavior that disables dependency lifecycle scripts by default. Although pnpm v10 blocks postinstall scripts via the onlyBuiltDependencies mechanism, dependencies sourced from Git repositories can still execute lifecycle scripts (notably prepare, prepublish, and prepack) during the fetch phase of pnpm install. This allows arbitrary code execution from a git-hosted dependency without the user’s explicit consent/approval, undermining the intended protection against automatic script execution during installation. The issue is fixed in pnpm v10.26.0.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Arbitrary code execution during pnpm install when a project includes a malicious or compromised git-hosted dependency. This can enable theft of secrets (environment variables, credentials/tokens), tampering/backdooring of source or build artifacts, and broader supply-chain compromise, including in CI/CD environments where installs run automatically.

Mitigation

If you can’t patch tonight, do this now.

Until upgrading, avoid or strictly control git-based dependencies (e.g., disallow git+https / direct git sources by policy), pin any unavoidable git dependencies to vetted commit SHAs, and perform installs in hardened/isolated environments (least-privilege runners, no long-lived secrets available at install time, and restricted network egress). If operationally feasible, run installs with scripts ignored (e.g., pnpm --ignore-scripts), noting this may break builds that rely on lifecycle scripts.

Remediation

Patch, then assume compromise.

Upgrade pnpm to v10.26.0 or later across developer workstations and CI/CD runners to ensure git-hosted dependencies cannot execute prepare/prepublish/prepack scripts during fetch in a way that bypasses the default-disabled lifecycle scripts protection.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PnpmPnpmapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.