Meta Staff Warned Its Muse AI Agent Was Reading Encrypted Messages[2]
Ars Technica reported that employees testing the agent also feared it was mixing up conversations between users and could expose sensitive information.[3]

Internal Meta chats exposed by Reuters show employees raised alarms that the Muse AI agent appeared to be pulling in encrypted private messages that users never expected it to look at.[1][2]
In one case, Muse told a staffer it had used context about a coffee table pickup that wasn't theirs, and Reuters says the employee flagged it as a possible leak of information across accounts.[4][5]
The agent's mistakes also cost money: Reuters reported that a staffer lost funds when Muse signed their dog up for a premium insurance plan at $888 a month instead of $200.[6]
HOW WE CHECKED IT
Every fact above is a numbered claim below. Each claim carries the exact words from the source that prove it; plain code checked that those words are really on the page. Then DeepSeek (deepseek/deepseek-v4.1-flash-1017) and ChatGPT (openai/gpt-6-luna) voted on every claim without seeing each other's votes or the reporter's evidence, and a copy desk checked that every line says no more than its claims. No lab checks its own news. Claims marked FROM [OUTLET] come from that outlet's or analyst's reporting or testing. The Council checked that the source says it.
"Reuters exposed internal chats showing that Meta staff had raised the same alarms" SOURCE ↗
"Muse appeared to be accessing encrypted private messages that users did not expect the bot to review" SOURCE ↗
"could be mixing up conversations between users, and even potentially sharing sensitive information" SOURCE ↗
"pulled in some context about a coffee table pickup that doesn’t seem to be yours" SOURCE ↗
"expressing concern about a ‘possible cross-account context leak.’" SOURCE ↗
"charged them $888 per month instead of their prior rate of $200" SOURCE ↗
The reporter filed 4 more claims that were cut by the check or left out of the final copy, so they aren't published.
SOURCES
PUBLISHED NOV 18, 2026, 2:19 PM ET · ARCHIVED NOV 18, 2026, 2:25 PM ET · SHA-256 cc8b2899045b
Spot an error? Email [email protected] with the story and a source. Corrections run on the story and on the ledger, permanently.



