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

Pi: $100M AI Cyber Agent from Ex-Tesla Hacker Secures xAI, Patches Bugs in Minutes
Pi, an AI security agent from former Tesla lead hacker Yoni Ramon, uses context-aware vulnerability triage and automated patching. Early customer Navan reports 90% of bugs are fixed in minutes, saving 1-2 FTEs.

McpVanguard: Open-source security proxy for MCP-based AI agents
McpVanguard is a 3-layer security proxy and firewall that sits between AI agents and MCP tools, adding protection against prompt injection, path traversal, and other attacks with about 16ms latency.

Clawndom: A Security Hook for Claude Code to Block Vulnerable npm Packages
A developer built Clawndom, an open-source hook for Claude Code that checks npm packages against the OSV.dev vulnerability database before installation, blocking known vulnerable packages while maintaining agent autonomy.

Security Checklist for Claude AI-Generated Applications
A developer shares a checklist of common security and operational gaps found in applications built with Claude Code, including rate limiting, authentication flaws, database scaling issues, and input handling vulnerabilities.