Platform News

Meta's Muse AI Surfaces Bank Balances From Other Accounts

Meta’s AI agent Muse is mixing up conversations and exposing private data, report says
Meta’s AI agent Muse is mixing up conversations and exposing private data, report saysAlexandra_Koch / pixabay

Meta employees report Muse AI leaked bank balances and Signal reminders from other accounts, per Reuters. The 10M-download agent launched in September; Meta says employee builds differ from public ones.

By Nathan Brooks

3 min read

At a glance

  • Reuters reviewed internal Meta posts showing Muse mixed up conversations and exposed private data across accounts
  • One leak included exact Capital One ($2,722.58) and Charles Schwab ($5,899.57) balances belonging to another user
  • Muse reminded one employee about a sister's Signal message despite no granted app access
  • Muse launched in September and has over 10 million downloads
  • Meta says employees test different Muse versions than the public

Meta employees say the company's AI agent Muse has been mixing up conversations across accounts and surfacing private user data that doesn't belong to them, according to a Reuters report published this week that examined internal company posts.

In one documented instance, Muse randomly dropped an extra message into a chat about weather and tide information: "BTW, two bank updates, your Capital One balance is $2722.58, your Charles Schwab balance is $5899.57." The balance figures weren't the user's own.

What exactly went wrong?

Employees reported several categories of leaked or misrouted content:

  • Childcare requests they never made
  • Career advice they never asked for
  • Product orders they never placed
  • Bank account balances belonging to other people

The most serious-sounding case involved access beyond Meta's own walls. One employee using Muse on her personal phone got a reminder from the agent to respond to a message from her sister on Signal — the end-to-end encrypted messaging app owned by the nonprofit Signal Foundation.

"This seems like an extreme privacy violation. I definitely did not grant it access to other apps, or recall being asked about this," the employee wrote in her internal post, according to the report.

The takeaway: Muse isn't just garbling text within Meta — it appears to be pulling data employees say they never authorized the agent to touch.

What has Meta said?

A Meta spokesperson addressed the reports in an email to TechCrunch, framing the incidents as part of normal product development.

"Employee testing is core to the product development process and the entire point is to get feedback, so we can implement safety and privacy protections and improve products," the spokesperson said. "Importantly, employees have access to different versions of Muse than the public, so they're often reviewing features, functionality, and behavior not available elsewhere."

That second point matters for readers trying to gauge risk. Meta's argument is that internal builds behave differently from what consumers see. But the company didn't dispute the specific incidents Reuters described, and it didn't explain why cross-account data bleed or third-party app access would be limited to employee-only versions.

In short: Meta confirms testing exists, but hasn't publicly confirmed or ruled out the same behavior in public builds.

How big is the blast radius?

Muse launched in September and has crossed 10 million downloads, making it one of the fastest-growing apps on record. That scale means any cross-account data leak isn't a lab curiosity — it's a potential exposure for millions of devices within weeks of launch.

The Signal incident raises a separate question: how an agent designed to work inside Meta's ecosystem detected activity in an encrypted third-party app on a personal phone. The reporting doesn't answer that mechanism, and Meta hasn't explained it.

Until Meta clarifies which versions exhibit this behavior and what data Muse can actually see, the safest read is that the mechanism behind these leaks remains unexplained — and the burden of proof sits with the company, not the employees filing the reports.

Source: techcrunch.com

Nathan Brooks

Show full bio

Staff writer covering companies, deals and strategy in Social platform news and policy at Reach Brief.

More from Nathan Brooks →

Related articles

« Previous articleNext article »