Meta's Muse Agent Leaks Other Users' Bank Balances and Signal Messages
What happened
According to a TechCrunch report citing internal Meta employee posts, Meta's AI agent Muse has been cross-contaminating conversations during internal employee testing, surfacing data belonging to other users. One agent message disclosed specific Capital One and Charles Schwab account balances to an employee who had not requested them. Other prompts referenced childcare requests, career advice, and product orders the recipient never made. In a separate case, Muse reminded an employee on her personal phone to reply to a Signal message, an interaction the employee said she had no recollection of authorizing. Meta told TechCrunch that employees test pre-release versions of Muse with features not available to the public. The testing process is intended to surface issues so safety and privacy protections can be built in. Muse launched in September and has reached more than 10 million downloads.
Why it matters
- ·Cross-account data contamination in an AI agent is a data isolation failure under the General Data Protection Regulation (GDPR) and equivalent laws. Surfacing one person's financial account details to another can constitute unauthorized disclosure of personal data. This applies regardless of whether the product is in a testing phase.
- ·AI agents with broad device permissions may reach data sources employees did not knowingly authorize. The apparent access to Signal messages without recalled user consent illustrates this risk. It extends to enterprise data if staff use the same personal devices for work under a bring-your-own-device arrangement.
- ·With Muse already at over 10 million downloads, compliance teams cannot treat this as a contained lab incident. Acceptable-use policies, device management standards, and vendor assessments for consumer AI agents must address these data access risks before employee adoption outpaces controls.
Stay ahead of stories like this
Get every Global AI governance development like this one, plus the rest of the week's developments. Every Thursday.
Recent issues
- Regulators, courts, and markets are all testing whether AI companies' accountability structures hold up under real pressure, not just in policy documents.19 Nov
- The next quarter will test whether compliance programs can keep pace with AI systems that breach containment, reshape capital markets, and enable fraud at a scale no prior control framework anticipated.12 Nov
Free every Thursday. Unsubscribe anytime.
Governance controls affected
What to do now
- ☐Review your acceptable-use policy for consumer AI agents to confirm it addresses apps that request access to messages, contacts, and financial data on personal devices that also carry work content.
- ☐If your organization operates a bring-your-own-device program, ask your mobile device management team whether Muse or similar consumer AI agents are installed on enrolled devices, and what data those apps can access.
- ☐Add the Muse cross-account data contamination incidents to your AI vendor risk tracking log, and assess whether any enterprise AI products from Meta are in scope for a formal re-evaluation of data isolation controls.
- ☐Confirm that your AI incident classification criteria cover third-party consumer agents as a named category, so incidents like this trigger a review and are not dismissed as outside scope.
- ☐Brief your privacy and data protection function on the Signal access concern, and confirm whether your employee privacy notices address AI agents that may read personal communications on work-enrolled devices.
What to watch next
Meta has not disclosed a timeline for resolving the data isolation failures in Muse, and the incidents described involve a pre-release version whose controls differ from the public release. Compliance teams should monitor whether Meta publishes a formal incident summary or updates Muse's privacy disclosures and permission model. EU and UK regulators have already signaled attention to AI agent data practices. This includes the ICO's open investigation into agentic AI data handling noted in ICO Secures Developer Changes and Opens Agentic AI Data Protection Probe. Regulators may treat cross-account data contamination at this scale as a prompt for supervisory action. Organizations operating under the General Data Protection Regulation (GDPR) should watch for any determination on whether employee testing programs constitute processing of personal data subject to the regulation's full requirements.
