Loading story…
Anthropic introduced Claude Code mods, JavaScript or TypeScript functions that can intercept session events and change prompts, tool calls, permission handling, and the application interface. The feature is enabled by default in Claude Code version 2.1.287 and later, with mods distributed through the existing plugin mechanism. Mods expand a customization ecosystem that already includes project memory, workflow hooks, settings, and Model Context Protocol (MCP) tool connections.
Mod code executes locally with access to the developer’s machine through Claude Code, making publisher trust and source-code review important security controls. Anthropic recommends inspecting mod source code and installing only mods from trusted publishers. For Team and Enterprise users, and machines with managed settings, Anthropic’s sec-default guard loads before user-installed mods and prevents them from overriding permission-deny rules by default. Outside those guarded environments, mods can override some permission decisions. Security teams should verify which guardrails apply before approving mods; the reported concern is an extension trust boundary, not a disclosed compromise or confirmed vulnerability.
Track how attackers are adapting to this technology.
1 event from the most recent confirmed update back to the earliest known activity.
Anthropic introduced JavaScript and TypeScript mods that can modify prompts, tool calls, permission handling, and the interface, enabled by default in Claude Code 2.1.287 and later. Mods execute locally; Team, Enterprise, and managed environments load a security guard that prevents user-installed mods from overriding permission-deny rules by default.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
5 references tracked. Mallory keeps watching after this page renders.
thenewstack.io
Open sourcecode.claude.com
Open sourcecode.claude.com
Open sourcecode.claude.com
Open sourcecode.claude.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Anthropic said **Claude Code Auto Mode** will become the default for Pro, Max, and Team users after testing showed people routinely approve risky coding-agent actions. Internal results cited by the company found users approve **97%** of permission prompts, while a study with more than 1,000 participants found humans detected only **13.6%** of dangerous commands overall and just **5%** after 50 prompts; Anthropic said Auto Mode detected about **89%** of those risky actions. The company said it has added hard denies for data exfiltration, protections for secrets and confidential data, checks on Git destinations and destructive Git operations, and API-side screening for prompt injection attempts. Separate testing reinforced the same pattern: a browser-based simulation built by Belgian developer Alex Wauters recorded more than **40,000** game runs and **409,000** approval decisions, with players allowing roughly **one in three** malicious requests. Scope violations, typosquatted packages, and suspicious `curl` requests were among the prompts that frequently slipped through, especially under time pressure, highlighting approval fatigue as a core weakness in human review. Anthropic and outside researchers both said automated controls are not a complete fix, but argued that stronger permission models, sandboxing, cloud devcontainers, contextual hooks, and layered defenses are more reliable than depending on repeated human approvals alone.
Aug 11, 2026
Anthropic announced **Claude Code Security**, an embedded capability in *Claude Code* that scans customer codebases for vulnerabilities and suggests patches, initially rolling out to a limited set of enterprise/team customers for testing. The company said the feature was stress-tested via internal red-teaming, Capture-the-Flag exercises, and collaboration with **Pacific Northwest National Laboratory**, and positioned it as a way to reduce reliance on manual security reviews as AI-assisted “vibe coding” increases and attackers also use AI to accelerate weakness discovery. In parallel, Anthropic released **Claude Sonnet 4.6**, emphasizing improved coding performance, stronger “computer use” capabilities, and expanded developer tooling (e.g., adaptive/extended thinking modes, beta context compaction, and API tools for web search/fetch and code execution). Separate commentary highlighted the security risk of **agentic coding assistants** (e.g., *Claude Code*, *Cursor*, *GitHub Copilot*) operating with broad privileges—file access, shell execution, and secret handling—and argued that the emerging **Model Context Protocol (MCP)** ecosystem needs stronger, future-proof identity controls; additional industry guidance promoted **MLSecOps** as a way to integrate security into AI/ML development lifecycles, though it did not report a specific incident or vulnerability.
Jun 29, 2026
Security researchers disclosed multiple vulnerabilities in **Anthropic’s Claude Code** AI coding assistant that could enable **arbitrary command execution** and **exfiltration of Anthropic API credentials** when developers clone/open a malicious repository. Check Point Research reported the issues abuse Claude Code configuration and initialization paths—particularly **project hooks** (e.g., untrusted `.claude/settings.json`), **Model Context Protocol (MCP) servers**, and **environment variables**—to trigger shell command execution and data theft. Anthropic’s advisory for **CVE-2026-21852** describes a project-load flow where a crafted repo can set `ANTHROPIC_BASE_URL` to an attacker-controlled endpoint, causing Claude Code to send API requests **before** the trust prompt is shown, potentially leaking the user’s API key. The disclosed issues include two high-severity code-injection paths (CVSS **8.7**) and one information-disclosure flaw (CVSS **5.3**): a consent-bypass/hook-based injection issue fixed in *Claude Code* **1.0.87** (Sept 2025), **CVE-2025-59536** fixed in **1.0.111** (Oct 2025), and **CVE-2026-21852** fixed in **2.0.65** (Jan 2026). Separate coverage framed Anthropic-related developments as market-moving, noting investor attention around Anthropic’s AI code-security tooling; however, the actionable security impact in this reporting is the risk that simply opening an attacker-controlled repository can lead to **RCE** and **credential leakage**, reinforcing the need to treat untrusted repos and tool initialization behaviors as a supply-chain and developer-workstation risk.
Jun 29, 2026