Skip to content
Zenteck
Latest
Analysis

How Meta Muse Accidentally Published Thousands of Private Work Chats

ByAlex Silva3 min read0 comments
meta-muse-shares-expose-private-chats-via-dns
Photo: ZenteckMeta Muse shares expose private chats via DNS

Listen to article0:00 / 0:30

When you ask an AI assistant to summarize a sensitive meeting or draft a loan application, you expect that data to remain private. However, according to a report by Ars Technica, security firm Claroc discovered that Meta's new AI agent, Muse, makes shared conversation links shockingly easy for outsiders to find.

As detailed by Ars Technica, the vulnerability stems from a fundamental design choice rather than a traditional code bug. When a user generates a link to share a chat, Muse includes the actual conversation title directly inside the web address on the cf.metaaiusercontent.com domain.

Because these URLs contain descriptive titles alongside random strings, monitoring systems and passive DNS services log them. Researchers reported that running a single query allowed them to harvest 6,800 active links, exposing highly sensitive internal documents.

What Kinds of Data Were Exposed?

The security researchers opened a fraction of the discovered links and found proprietary business information that was never meant for public indexing. The exposed data included:

  • Confidential executive search notes naming contacts at a frontier AI lab
  • Internal revenue reviews marked directly for a company's CEO
  • Small-business loan applications detailing requested funding amounts
  • Workplace vacation schedules and internal performance reports

How to Protect Your Work on Monday Morning

If your team uses Meta Muse for daily productivity, you must change your sharing habits immediately to avoid leaking company secrets. Follow these steps to secure your workflow:

  1. Avoid generating web links: Never use Muse's built-in URL sharing feature for any conversation containing proprietary data, financial figures, or personal information.
  2. Purge history regularly: Delete sensitive chats and shared links from your account dashboard as soon as you finish reviewing them.
  3. Audit tool permissions: Since Muse requires deep access to your accounts to automate tasks, restrict its usage strictly to non-confidential personal workflows until Meta patches the architecture.

The Verdict: Can You Trust Muse at Work?

As Ars Technica points out, this discovery follows earlier criticisms regarding device-level vulnerabilities. While Meta positions Muse as a trustworthy autonomous agent for everyday tasks, exposing corporate financials through passive DNS records proves that security guardrails are still lacking.

Sources

  1. Meta Muse exposes users' personal and business secrets when they share conversations — arstechnica.com

Frequently asked questions

How did researchers find the Meta Muse links?
Researchers used passive DNS search services to query URLs containing conversation titles hosted on the metaaiusercontent.com domain.
Are all Meta Muse conversations public?
No, only conversations where users actively generated and shared a web link are exposed to discovery.
How can I prevent my Muse chats from leaking?
Stop using the URL sharing feature for work-related data and delete sensitive chat histories immediately after use.