Arbitrary Code Execution in OpenClaw Local Plugin and Hook Installation via .npmrc Git Override
CVE-2026-35641 is an arbitrary code execution vulnerability affecting OpenClaw versions prior to 2026.3.24. The flaw exists in the local plugin and hook installation workflow. An attacker can craft a malicious .npmrc file that overrides the git executable used by npm. When OpenClaw performs npm install in the staged package directory, git-based dependencies can cause npm to invoke the attacker-specified program instead of the expected git binary. This results in execution of arbitrary code under the security context of the OpenClaw installation process.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary code execution on the affected system during local plugin or hook installation. Because the attacker-controlled program is executed by the npm install process, the attacker can compromise the confidentiality, integrity, and availability of the host within the privileges of the invoking user or service account.
If you can’t patch tonight, do this now.
Until patched, avoid installing untrusted local plugins or hooks, especially packages that may include attacker-controlled .npmrc files or git-based dependencies. Restrict who can supply or stage plugin and hook packages, review package contents before installation, and perform installations in tightly controlled environments with minimal privileges. Where operationally feasible, prevent npm from honoring untrusted per-package configuration during installation workflows.
Patch, then assume compromise.
Upgrade OpenClaw to version 2026.3.24 or later, which addresses the unsafe handling of .npmrc-controlled git executable overrides during local plugin and hook installation. Apply the vendor-provided fix and ensure all affected deployments are updated.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.