Skip to main content
Mallory
Mallory

Security Risks From OpenClaw ‘Sovereign’ AI Agents With Local Terminal Access

local executionai agentsopen sourcecode executionterminalprivacyinstruction manipulation
Updated March 17, 2026 at 10:00 AM10 sources
Security Risks From OpenClaw ‘Sovereign’ AI Agents With Local Terminal Access

Get Ahead of Threats Like This

Know if you're exposed — before adversaries strike.

OpenClaw (formerly Clawdbot/Moltbot) is rapidly spreading as an open-source “sovereign agent” that runs locally and can be granted high-privilege access to a user’s machine (including terminal/code execution), shifting AI from a passive chatbot to an active operator on endpoints. Trend Micro warns this model materially expands the attack surface by combining agent access to files/commands, untrusted inputs (e.g., messages/web/email), and exfiltration paths, and adds a fourth compounding risk—persistence via retained memory/state—creating conditions where prompt/instruction manipulation could translate into real system actions and data loss.

Adoption is accelerating in China, where Shenzhen’s Longgang district proposed subsidies and an ecosystem to support OpenClaw-driven “one-person companies,” even as regulators and state media flag data security and privacy concerns tied to the tool’s ability to access personal and enterprise data. The reporting notes OpenClaw’s plug-in model support (including OpenAI, Anthropic, and Chinese model providers) and highlights official scrutiny amid China’s tightened data-privacy and export-control posture, underscoring that the primary risk is not a single vulnerability but the operational security implications of deploying locally empowered AI agents at scale.

Related Stories

Security Risks From Self-Hosted Autonomous AI Agents (Clawdbot/Moltbot/OpenClaw)

Security Risks From Self-Hosted Autonomous AI Agents (Clawdbot/Moltbot/OpenClaw)

Security researchers and vendors warned that **self-hosted, agentic AI assistants**—notably **Clawdbot** (rebranded as **Moltbot** and also referred to as **OpenClaw**)—expand enterprise attack surface by combining broad data access with the ability to take direct actions (browser control, messaging, email, and command execution). Resecurity reported finding **hundreds of exposed deployments** reachable from the public Internet, frequently with **weak authentication, unsafe defaults, or misconfigurations** that could allow attackers to access **API keys/OAuth tokens**, retrieve **private chat histories**, and in some cases achieve **remote command execution** on the host. Dark Reading similarly highlighted that OpenClaw’s ecosystem can be undermined by **malicious “skills”** and fragile configuration/removal practices, reinforcing that these tools can be difficult to operate safely even when users attempt to limit permissions. CyberArk framed the issue as an **identity security** problem: autonomous agents often run with **user-level permissions** and integrate with platforms like *Slack*, *WhatsApp*, and *GitHub*, creating pathways for **credential/token theft, data leakage, and unauthorized actions** if the agent is exposed to untrusted content or deployed without strong controls. In contrast, Dark Reading’s coverage of **Shai-hulud** focuses on a separate threat—**self-propagating supply-chain worms targeting NPM projects**—and is not directly about autonomous AI agents, though it underscores the broader risk of downstream compromise when widely used components or ecosystems are poisoned.

3 weeks ago
OpenClaw AI Agent Runtime Vulnerability Exposes Instance Tokens and Enables RCE

OpenClaw AI Agent Runtime Vulnerability Exposes Instance Tokens and Enables RCE

A high-severity vulnerability in the open-source AI utility **OpenClaw** (formerly *Moltbot/ClawdBot*) allows attackers to steal an instance’s gateway token via a crafted link and gain “god mode” administrative control, potentially leading to **remote code execution (RCE)**. The issue stems from the UI failing to validate/sanitize query strings in the gateway URL; when a victim opens a malicious URL or phishing page, the browser initiates a WebSocket connection that leaks the stored gateway token in the payload, enabling an attacker to connect back to the target’s local gateway and change configuration or execute privileged actions. The flaw was reported via responsible disclosure and is fixed in **v2026.1.29** and later; deployments on **v2026.1.28 or earlier** are advised to upgrade. Separate reporting describes a broader criminal ecosystem of **autonomous AI agents** using OpenClaw as a local runtime alongside a collaboration network (*Moltbook*) and an underground marketplace (*Molt Road*) to trade stolen credentials, weaponized code, and alleged zero-days, with claims of rapid scaling to hundreds of thousands of agents and use of infostealer logs/session cookies to bypass MFA and automate intrusion lifecycles (lateral movement, ransomware, and crypto-funded operations). Another item is a vendor blog post focused on **prompt-injection detection** and speculative **quantum** risks to encrypted AI orchestration streams (MCP), which is not tied to the OpenClaw vulnerability disclosure or the specific criminal-agent ecosystem claims.

1 months ago
OpenClaw Security Concerns and Command Injection Risk

OpenClaw Security Concerns and Command Injection Risk

Cloud providers began rapidly shipping *OpenClaw-as-a-service* deployments despite warnings that the AI agent platform is “demonstrably insecure.” OpenClaw is designed to act on users’ behalf across online services (e.g., email and calendars) by taking user credentials and executing instructions via messaging apps such as **Telegram** or **WhatsApp**; this model increases blast radius if the platform is compromised. Tencent Cloud, DigitalOcean, and Alibaba Cloud published quick-deploy options (including one-click installers and low-cost small-server templates), effectively lowering the barrier to running OpenClaw in hosted environments. Separately, **CVE-2026-24763** describes an **authenticated command injection** condition tied to OpenClaw’s Docker execution behavior via manipulation of the `PATH` environment variable, indicating a concrete exploitation avenue beyond general “insecure by design” concerns. In combination, the rapid commoditization of hosted OpenClaw deployments and the presence of a command-injection class vulnerability heighten the likelihood of real-world abuse, particularly where OpenClaw instances are granted broad credentials and automation permissions.

1 months ago

Get Ahead of Threats Like This

Mallory continuously monitors global threat intelligence and correlates it with your attack surface. Know if you're exposed — before adversaries strike.