OpenClaw User Adds TOTP 2FA After Agent Exposed API Keys in Plain Text

Security Incident Triggered TOTP Implementation
During a demo for coworkers, an OpenClaw user asked their agent to "show my tokens and passwords." The agent responded by displaying plain text credentials including:
- OPENAI API_KEY=sk-abcdefghijklmnopqrstuvwxyz1234567890
- ANTHROPIC_API_KEY=sk-ant-...
- TELEGRAM_BOT_TOKEN=7123456789:AAF...
- DATABASE_PASSWORD=MySuperSecretProdPass2025!
- GITHUB_PAT=ghp ...
The credentials appeared in "beautiful, plain, copypasteable text" on screen during the office demo, exposing what the user described as their "entire digital life."
The Secure Reveal Skill Solution
The user developed a skill called "Secure Reveal" on their NanoClaw playground that changes how OpenClaw handles credential requests. When anyone types commands like:
- "show my tokens"
- "what's my API key"
- "list passwords"
- "give me the bot token"
The agent no longer prints secrets in the main chat. Instead, it immediately sends a DM to the user's personal Telegram with: "🔐 Identity Verification — enter your 6-digit Authenticator code."
Only after the user enters the current TOTP code from Authy (or another authenticator) does OpenClaw send the actual value — and only via a Telegram message that auto-deletes after 10 seconds.
Wrong codes result in: "❌ Access denied." The system ensures "No secret ever touches the persistent chat history again."
Security Risks Addressed
The user identified several vulnerabilities that prompted this solution:
- Chat logs persist forever unless manually deleted
- Screenshot risks during demos or screen sharing
- Shoulder surfing in shared spaces
- Recorded meetings capturing sensitive information
- Future device compromise or physical access by unauthorized parties
The user noted that even with trustworthy coworkers, "Helpful AI + persistent secrets in chat history = massive single point of failure."
This approach is particularly relevant for developers who demo their agents to others, use OpenClaw on shared or less-secure devices, or want to avoid plain-text secrets living indefinitely in logs.
📖 Read the full source: r/openclaw
👀 See Also

Configuring OpenClaw for Encrypted LLM Inference Using TEE Enclaves
A developer shares how they configured OpenClaw to use Onera's AMD SEV-SNP trusted execution environments for end-to-end encrypted LLM inference, including configuration examples and technical tradeoffs.

EctoClaw: Safety Tool for OpenClaw Agents with Terminal Access
EctoClaw is a free open source safety tool for OpenClaw that checks every action four times before execution, runs actions in a strong sandbox, and records everything with proof.

Sandboxing OpenClaw: Enhancing Security In AI Coding
Discover the latest discussions from the OpenClaw community on sandboxing, a critical technique for securing AI coding agents. Explore why users believe it is essential for safeguarding AI innovations.

Independent Report on MCP Server Reliability and Security Findings
An independent analysis of 2,181 MCP server endpoints reveals 52% are dead, 300 have zero authentication, and 51% have wide-open CORS. The report includes methodology and a testing tool.