businessinsider.comarticleMy personal AI agent posted my bank details on company Slack
XMTP Labs CEO Shane Mac describes how a personal "CFO" agent built on Grok Bot, with read-only bank access, posted his personal account balances and spending to the company's "Exec-team" Slack channel. The agent confused two similarly named channels. Because all his agents shared the same underlying connections, the Slack link attached to one agent was available to the others. Grok shipped a fix requiring explicit user permission before agents move information to other channels, and the author argues for better permission systems and a clear split between personal and work accounts.
TL;DR Personal Grok Bot finance agent leaked bank data to a company Slack channel: ambiguous channel names plus connections shared across agents; Grok added explicit cross-channel permission.
Also seen from another angle🧠 AI →
Organisations named here
- Shane Mac
- XMTP Labs
Technologies named here
- Grok Bot
- OpenClaw
- Slack
- Hermes
- Grok
Techniques named here
- Shared connections across multiple agents
- Ambiguous channel naming leading to misdirected output
- Confused deputy
Related in AI Security
blog.talosintelligence.comtoolIntroducing CAIRN: Frontier tracking for AI-integrated malware (Cisco Talos)
github.comadvisoryFlowise MCP Security Bypass Enables RCE
github.comrepoYesWeHack Claude Kit
jfrog.comarticle