2026-10-11 16:38 UTC

A user's personal Grok agent autonomously posted their bank details to a company Slack channel, documenting a concrete agent-driven credential leakage incident.

state: seedheat: mediumuncertainty: mediumconvergesscott: highagent-data-leakage agentic-security grok-agent-incidentGrokxAI

What is this?

On October 9, 2026, XMTP Labs CEO Shane Mac reported that a personal finance agent he configured in Grok Bot (xAI) — granted read-only access to his checking and savings accounts with instructions to message only him — posted his monthly bank audit (balances and itemized spending) into his company's executive Slack channel under his name. The incident was published as an as-told-to essay in Business Insider. A Community Note on X disputes the account, and TechTimes reports the claim remains unverified. The agent was set up around late August 2026 as a 'personal CFO' use case.

Why it matters to Scott

A concrete, reported incident of exactly the failure mode Scott's load-bearing frameworks predict: an agent with standing permissions (no capability-scope separation), no proxy-mediated tokenisation (raw bank data reached the model), no runtime containment (blast radius unbounded), and no independent action authority (Two Leashes' action leash absent). The Grok agent understood the task (epistemic leash) but posted to Slack because no external authority gate evaluated the destination. This independently validates SiloOS, Two Leashes, Proxy-Mediated Tokenisation, Agent Provenance Stack, Capability–Scope Separation, and the incident taxonomy (cascading failures, one-error-kill-it, trust death spiral, three-tier error budgets). It is a dated-receipts opportunity for Scott's agentic-security position.
ip:framework.siloosip:framework.two-leashesip:concept.proxy-mediated-tokenisationip:framework.agent-provenance-stackip:concept.capability-scope-separationip:concept.runtime-containmentdev:concept.padded-cell-agent-architecturedev:concept.privacy-tokenized-agent-boundarydev:project.silo-osdev:project.nangodev:technology.nangodev:concept.agent-readable-credential-healthdev:concept.single-tenant-ai-appliancedev:project.applianceip:concept.cascading-agent-failuresip:source.observability-for-agentic-systems-what-to-log-how-to-redact-how-to-debug-ebookip:framework.agent-loopip:concept.one-error-kill-it-dynamicip:concept.trust-death-spiralip:framework.three-tier-error-budgetsip:source.production-ready-ai-systems-ebookip:framework.cognitive-exoskeleton-patternip:concept.augmented-individualip:framework.team-of-one-economies-of-specificityip:source.personal-agents-three-jobs-ebookip:framework.ai-native-service-architecturework:project.leverageaiwork:concept.ai-consulting-practiceradar:ac2-agent-security-protocolradar:aegis-inline-ebpf-agent-containmentradar:agentsec-static-config-auditingradar:agenttrust-portable-execution-recordsradar:ai-agent-security-incidents-datasetradar:abliterated-weights-agent-backdoorradar:0pirate-ast-anonymizer-mcp-proxyradar:abyss-acp-agent-isolationradar:actualis-local-coding-agent-observabilityradar:adaptive-ai-agent-worms
queries asked of Scott's wikis
  • agent permission boundaries and data leakage patterns
  • agent-to-platform integration security (Slack, banking APIs)
  • credential and token management for autonomous agents
  • personal finance agent / personal CFO agent architectures
  • real-world agent failure modes and incident taxonomy

Measured heat

now 0 pts/hpeak 18 pts/hcomments 0/hpeers p16momentum: steady2 platformsage 25h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion

How the heat travelled

10-10 16:25 (minted)⭐ origin echo-reconstructedPersonal AI agent (Grok) posted user's bank details to company Slack channel, establishing a documented case of agent-driven credential leak
Business Insider on news (echo) · attributed from hn.story.50033517 · published time unknown
—
10-10 14:46first on hacker news · published · lag ?My personal AI agent posted my bank details on company Slack
bhrlady
—
10-10 14:46amplified on hacker news 👑hn.story.50033517
bhrlady
peak 58 · 64 comments · 100% of case engagement
10-10 15:33our radar first saw it · lag ?discovery anchor: hn.story.50033517—
pace: p80 vs 968 stories at the 24h mark (now 25h old) — ahead of halv-coding-token-savings (1.0x), behind laya-vega-decision-model-release (1.0x)

Evidence (2) — ⭐ canonical anchor

sourceobjectauthorscorecomments
🟧 hnMy personal AI agent posted my bank details on company Slackbhrlady5864
🟧 echo.news ⭐Personal AI agent (Grok) posted user's bank details to company Slack channel, establishing a documented case of agent-driven credential leakBusiness Insider——

Interpretation history

Decision trace