Fetching from the wire…
Top 5 · 2026-03-25 · source-backed
Lasso Security published research demonstrating that Claude Code's --dangerously-skip-permissions flag enables indirect prompt injection via poisoned READMEs, documentation files, and MCP responses. Then they did something unusual: they released the defense alongside the attack.
Their open-source claude-hooks project implements a PostToolUse hook with 50+ regex patterns across four attack categories: instruction override, role-playing manipulation, encoding/obfuscation, and context manipulation. When a tool returns content that matches an attack pattern, the hook intercepts it and injects a warning into Claude's context before processing continues. It's the first production-ready open-source defense for Claude Code's autonomous mode.
This matters because three independent security responses landed in the same week. Trail of Bits released their internal Claude Code security config with PreToolUse hooks that block dangerous patterns before execution. Anthropic shipped CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=1 in v2.1.83, which strips credentials from every subprocess environment. Three different teams, three different approaches, all targeting the same attack surface.
The Claude Code v2.1.83 release itself is significant beyond the credential scrubbing. managed-settings.d/ lets organizations deploy modular policies. sandbox.failIfUnavailable enforces strict sandbox requirements. Transcript search via / key makes long sessions navigable. Over 50 bugs fixed. The --bare flag gives ~14% faster SDK performance.
For builders using Claude Code autonomously (and I know many of you are), here's your action list: install claude-hooks as a PostToolUse defender. Add CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=1 to your shell profile. Review Trail of Bits' config for PreToolUse guardrails. If you're running --dangerously-skip-permissions without any of these, you're accepting a risk that now has documented, weaponized exploits and documented, tested defenses. There's no excuse for the former without the latter.
Each link below shares sources, entities, or timing with this story.
For a month, Claude Code users were convinced the model had been "nerfed." Forums lit up. Conspiracy theories multiplied. People switched tools. Then on April 23, Anthropic did something unusual: they published a detailed post-mortem that named three specific bugs with exact d...
Two releases landed today and they're both significant. The headline security fix: PreToolUse hooks returning allow were bypassing deny permission rules — including enterprise managed settings. If you're running Claude Code in a managed enterprise environment with security hoo...
Two researchers in my set surfaced this independently, which is usually a sign it matters. Claude Code 2.1.166, first seen June 6, introduces a fallback-models setting: configure up to three models tried in order when the primary is overloaded or unavailable. It also adds glob...
This one rearranged my week. An essay published August 4 walks through Databricks' independent benchmark of coding harnesses against its own multi-million-line codebase. Pi, a harness with four built-in tools and a system prompt under 1,000 tokens, paired with Opus 4.8 at xhig...
The v2.1.205 release turned /doctor into a full setup audit that flags unused skills, MCP, and plugins against their context cost, deduplicates local vs checked-in CLAUDE.md, and flags slow hooks (Releasebot). A typical 5-server, 58-tool MCP setup burns ~55k tokens before your...
A developer built a website with Claude. Then noticed it looked identical to a dozen other websites. Same Inter font. Same purple-to-blue gradients. Same 16px border radius cards. Same layout patterns. They posted about it on r/ClaudeAI and 1,009 people upvoted because they'd...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.