OpenClaw's Credential Problem Is Structural, Not Incidental
Between January 27 and February 3, 2026, three critical security incidents hit OpenClaw: 341 malicious skills discovered in ClawHub marketplace (12% of registry) 1.5 million agent API tokens expose...

Source: DEV Community
Between January 27 and February 3, 2026, three critical security incidents hit OpenClaw: 341 malicious skills discovered in ClawHub marketplace (12% of registry) 1.5 million agent API tokens exposed via Moltbook social network breach 21,639 publicly exposed OpenClaw instances identified by Censys One-click RCE vulnerability (CVE-2026-25253, CVSS 8.8) disclosed OpenClaw has 250,000+ GitHub stars in 60 days—the fastest-growing open-source project in history. The scale of adoption makes this vulnerability pattern consequential. Where Credentials Are Stored OpenClaw stores API keys and bot tokens in plaintext JSON files at ~/.openclaw/openclaw.json. This is documented in official docs and acknowledged in community discussions. A critical bug (#9627) revealed that config write operations resolve environment variable references like ${VAR_NAME} and replace them with actual credential values in plaintext JSON. Users attempting environment variable indirection discovered that routine updates p