Know a great AI tool or AI news source? Submit it to AiByts
as told to4 min read

My personal AI agent posted my bank details on company Slack

Article URL: https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10 Comments URL: https://news.ycombinator.com/item?id=50033517 Points: 12 # Comments: 9

By bhrladyHacker News
My personal AI agent posted my bank details on company Slack

A CEO's personal AI agent accidentally shared sensitive financial data with their company's Slack channel due to a configuration error, highlighting risks in AI tool permissions and data handling.

What happened

Shane Mac, CEO of XMTP Labs, used a Grok Bot AI agent to manage personal finances. A misconfiguration caused the agent to send monthly financial reports to a company Slack channel named 'Exec-team' instead of his personal AI group chat, exposing bank balances and expenses.

Why it matters

The incident underscores the need for robust permission systems in AI tools to prevent accidental data leaks, especially as personal and professional digital environments increasingly overlap.

  • Verify destination channels for AI-generated outputs
  • Implement strict permission controls for AI tool access
  • Separate personal and work digital environments to prevent data overlap

The bigger picture

The incident highlights risks in AI agent configurations and the importance of clear boundaries between personal and professional data ecosystems.

This incident demonstrates both the power and potential risks of AI agents, emphasizing the need for better security measures and user awareness in AI tool deployment.

Technical details

  • Grok Bot AI agent with read-only access to banking accounts
  • Channel name confusion between personal and work Slack groups
  • Shared underlying connections across multiple AI agents

FAQ

What caused the AI agent to send data to the wrong channel?

The AI agent confused the destination channel due to identical names ('Exec-team') between personal and work environments, despite being configured for different purposes.

How was the issue resolved?

Grok Bot implemented stricter permission requirements, ensuring agents must explicitly request access to move information between channels.

What lessons can be learned from this incident?

Users should carefully manage AI agent permissions, verify output destinations, and maintain clear separation between personal and professional digital systems.

This summary and analysis were generated with AI from the original article and may contain errors. Read the original for the full story.

Read the full story

Originally published by Hacker News on Oct 10, 2026.

Read on Hacker News(opens in a new tab)

Comments

Sign in to join the discussion.

No comments yet — be the first to share your thoughts.