OpenClaw Completes Security Audit With Trail of Bits via OpenAI's Patch the Planet
OpenClaw completed a security audit conducted by Trail of Bits through OpenAI's Patch the Planet initiative. The recap, written by Josh Avant, covers what the review examined and what shipped as a result. According to the announcement, every actionable issue found during the audit has been repaired, with fixes landing in stable releases.
What the audit covered
The central question driving the review: what happens when an AI agent's permissions change while it's still working? That scenario is specific to multi-step agent runs, where a single task can span many tool calls, approvals, and context transitions. If permissions shift halfway through, you need to know whether the agent honors the new state or keeps operating on the old one.
The audit examined three areas:
- Permissions — how they behave and hold up as an agent moves through a multi-step task.
- Identity — how the agent's identity is represented and maintained across the run.
- Approvals — how approval gates function when an agent is carrying out work across multiple steps.
This is the class of problem that matters for anyone running agents with real access — filesystem, network, shell, or external APIs. A permission check that's correct at step 1 but stale by step 7 is a real exposure surface.
Outcome
All actionable findings were fixed. The fixes were shipped in stable releases rather than held behind a flag or preview channel. The full recap — what the team found, what changed, and what they learned about securing agent systems — is linked below.
If you're building or running agents that hold credentials or perform side effects across multiple steps, the permission-revalidation-during-work question is worth reading up on directly. The source post points to openclaw.ai/blog/openclaw-trail-of-bits-engagement-recap for the details.
📖 Read the full source: r/openclaw
👀 See Also

BlindKey: Blind Credential Injection for AI Agents
BlindKey is a security tool that prevents AI agents from accessing plaintext API credentials by using encrypted vault tokens and a local proxy. Agents reference tokens like bk://stripe, and the proxy injects the real credential at request time.

Critical RCE vulnerability in protobuf.js library
A critical remote code execution vulnerability in protobuf.js versions 8.0.0/7.5.4 and lower allows JavaScript code execution through malicious schemas. Patches are available in versions 8.0.1 and 7.5.5.

Malicious Google Ad Targets Claude Code Installation
A malicious Google ad appears as the top result for 'install claude code' searches, attempting to trick users into running suspicious terminal commands. The ad was still active as of March 15, 2026, and the author narrowly avoided executing the code.

LiteLLM v1.82.8 Compromise Uses .pth File for Persistent Execution
LiteLLM v1.82.8 was compromised on PyPI and includes a .pth file that executes arbitrary code on every Python process startup, not just when the library is imported. The payload runs even if LiteLLM is installed as a transitive dependency and never used directly.