HighPublic exploit

pnpm lockfile integrity bypass for HTTP/git tarball dependencies

IdentifiersCVE-2025-69263CWE-353

In pnpm versions 10.26.2 and below, HTTP/HTTPS tarball dependencies (and git-hosted tarballs) are recorded in the pnpm lockfile without integrity hashes. As a result, even when a lockfile is committed, pnpm cannot verify that the fetched tarball content matches a previously-resolved artifact. A remote server hosting the tarball can therefore serve different content on different installs while still satisfying the same lockfile entry, enabling a lockfile integrity bypass for URL/git tarball dependencies.

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.

Start free trial

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.

Supply-chain compromise risk: an attacker controlling (or able to influence) the remote tarball content can deliver different dependency payloads to different victims/CI runs (e.g., targeted malicious code, time-based/conditional payloads, audit evasion) despite the presence of a committed lockfile, because pnpm lacks integrity verification for these dependency types in affected versions.

Mitigation

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

Avoid or minimize HTTP/HTTPS tarball URL dependencies and git-hosted tarball dependencies in pnpm dependency trees; prefer registry-published packages that include integrity metadata. Until pnpm is upgraded, treat projects that include URL/git tarball dependencies as effectively unpinned for those artifacts, and enforce network egress controls/allowlisting for dependency fetches in CI/CD to limit exposure to arbitrary tarball hosts.

Remediation

Patch, then assume compromise.

Upgrade pnpm to 10.26.0 or later, which adds/fixes integrity handling for HTTP/HTTPS tarball and git-hosted tarball dependencies so lockfiles can provide integrity protection for these artifacts.

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.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app

the hacker newsNews

Jan 26, 2026

Malicious VS Code AI Extensions with 1.5 Million Installs Steal Developer Source Code

A pnpm PackageGate zero-day that can be exploited to bypass security controls intended to prevent automatic execution of lifecycle scripts (e.g., when using --ignore-scripts) and/or defeat lockfile integrity expectations during package installation.

bleeping computerNews

Jan 26, 2026

Hackers can bypass npm’s Shai-Hulud defenses via Git dependencies

A pnpm vulnerability (one of two referenced) fixed by pnpm; discussed in the context of PackageGate bypasses affecting JavaScript package managers, including bypass of script-execution protections and (for pnpm) lockfile integrity bypass.

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.

Start free trial

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 activity