🔥Stalecollected in 31m

OpenClaw: 270K Exposed Amid Uninstall Surge

OpenClaw: 270K Exposed Amid Uninstall Surge
PostLinkedIn
🔥Read original on 36氪

💡270K exposed OpenClaw agents warn devs of deployment pitfalls in viral AI tools.

⚡ 30-Second TL;DR

What Changed

Door-to-door OpenClaw uninstall services priced 20-299 RMB due to safety and cost concerns.

Why It Matters

Exposes rapid AI agent deployment risks, urging better security practices. Fuels China AI hype, boosting related stocks like MiniMax.

What To Do Next

Scan your OpenClaw deployments for exposed 18789 port and add firewall/authentication immediately.

Who should care:Developers & AI Engineers

🧠 Deep Insight

Web-grounded analysis with 5 cited sources.

🔑 Enhanced Key Takeaways

  • OpenClaw, formerly known as Moltbot and Clawdbot, achieved over 150,000 GitHub stars shortly after release due to its viral adoption for autonomous AI agent capabilities[4].
  • CVE-2026-25253 (CVSS 8.8) enables remote code execution via malicious JavaScript that leaks gateway authentication tokens, patched in version 2026.1.29[1][5].
  • Infostealers like RedLine, Lumma, and Vidar target OpenClaw's plaintext config files storing API keys and OAuth tokens[1].
  • ClawHub skill marketplace has faced repeated compromises with malicious skills, exacerbating risks beyond default configurations[1].

🛠️ Technical Deep Dive

  • OpenClaw gateway ships with authentication disabled by default, exposing instances to public internet access without firewalls[1].
  • Supports 'skills' as plugins for actions like file access, web browsing, and command execution, with autonomous decision-making on skill chaining[2].
  • Vulnerable to prompt injection attacks where malicious instructions in webpages, messages, or PDFs override programmed behavior[2][3].
  • Credentials including API keys, OAuth tokens, and bot credentials stored in plaintext config files[1].

🔮 Future ImplicationsAI analysis grounded in cited sources

OpenClaw deployments will require industry-wide AI agent security standards by end of 2026
Mastercard highlights OpenClaw's risks like prompt injection as necessitating shared standards to enable safe scaling across use cases including transactions[3].
Unpatched OpenClaw instances must be assumed compromised
CVE-2026-25253 allows full administrative control without prior access, and adoption outpaces community patching efforts[1].

Timeline

2025-12
OpenClaw introduced as open-source AI agent, rapidly advancing technically
2026-01
Viral adoption with over 150,000 GitHub stars, formerly Moltbot/Clawdbot
2026-02
CVE-2026-25253 disclosed, enabling remote code execution
2026-02
Version 2026.1.29 released patching CVE-2026-25253
2026-03
Security researchers document misconfigurations and 270K exposed instances
📰

Weekly AI Recap

Read this week's curated digest of top AI events →

👉Related Updates

AI-curated news aggregator. All content rights belong to original publishers.
Original source: 36氪