Meta Pauses Muse Chat Sharing After 6,800 Conversations Surface in DNS Records

What happened to Meta Muse chat sharing?

Meta paused Muse chat sharing after researchers found that shared conversation pages could be discovered through DNS records. Claroc published its GhostShares research on October 18, 2026, after finding that Muse conversation-sharing pages could appear in passive-DNS data even when recipients had not received the direct links. Meta said it was suspending the feature on October 20 while it reviewed the report.

The privacy concern is significant because a share link is normally treated as difficult to find unless somebody deliberately sends it to another person. Claroc found that Muse constructed a shared-page hostname using a conversation title and a random identifier. That design exposed descriptive topic information and created a path to the identifier that was intended to make the page hard to guess.

Meta introduced Muse on September 8, 2026, as a personal AI agent available through iOS, Android, WhatsApp, and muse.ai. Meta said Muse could work in a browser and access connected services after user approval. Those capabilities make careful data handling especially important, because an agent conversation can include details drawn from tasks, connected accounts, or material pasted into a prompt. Meta’s Muse announcement describes the product’s intended scope.

How did Muse conversation pages appear in DNS records?

Muse conversation pages appeared in DNS records because the share-page hostname contained both a readable title and a random identifier. Claroc said Muse used the cf.metaaiusercontent.com content domain for shared pages. A commercial passive-DNS query returned more than 6,800 share hostnames after the researchers filtered wildcard-DNS noise from the results.

Passive DNS is historical information about domain lookups and observed hostnames. It can help security researchers identify infrastructure, but it can also preserve hostnames that reveal more than a service intended. The relevant problem was not that every DNS record exposed a full chat transcript. The problem was that the hostname exposed enough information to identify a conversation topic and locate the otherwise difficult-to-guess share page.

The practical lesson is that an unlisted URL is not the same as a private document. Users should assume a conversation title can be sensitive when it mentions finances, medical information, workplace plans, account activity, or another identifiable subject.

What sensitive material did researchers find in Muse shares?

Claroc found that most sampled Muse shares were harmless, but some contained personal and business material that should not have been broadly discoverable. The researchers said they opened a few hundred sampled pages in an incognito browser without a Muse account or sign-in. The samples included a small-business loan application, a bank-fraud alert with a partial account number, a CEO-only revenue review, real-estate financial data, and a staff vacation calendar.

Those examples show why conversation-sharing tools need stronger privacy boundaries than a hard-to-guess link alone. A chat can begin with an ordinary request and later accumulate confidential pasted text, uploaded details, or business context. A visible title can also create harm on its own when it identifies a financial issue, a health question, or an internal company activity.

Users should apply the same caution to AI chats that they apply to cloud documents. A question about user chat data can become more consequential when a service changes ownership, access rules, or sharing behavior. The safest approach is to avoid putting full account numbers, passwords, government identifiers, customer records, or confidential workplace information into a consumer AI conversation.

Why does passive DNS history still matter after Meta paused sharing?

Passive-DNS history can still matter because old hostnames and their conversation titles may remain recorded after the underlying page stops opening. Claroc said it rechecked 40 shares that had previously opened without an account after Meta paused sharing. None remained accessible, but the researchers said the hostnames and titles remained in passive-DNS history.

The pause therefore addresses access to the sampled pages, not necessarily every trace of the hostname that external DNS datasets previously recorded. A title such as “loan application” or “revenue review” can disclose context even if the underlying conversation is no longer available. The exposure is more limited than continued access to a transcript, but it can still create privacy and reputational concerns.

Claroc said it reported the issue through Meta’s bug bounty program on October 8 and found no evidence that anybody had misused the exposed shares. That limit matters. The research documents an exposure pathway and sensitive examples, but it does not establish that a third party accessed or abused every discovered page. Claroc’s GhostShares research explains the hostname design and the researchers’ sampling method.

What should Muse users do after the chat-sharing pause?

Muse users should stop sharing sensitive conversations and review any prior shared chats that involved financial, personal, or workplace information. Meta has suspended the sharing feature, so users cannot rely on creating a new share link as a normal workflow while the review is underway. Users who copied a share URL into email, a group chat, a document, or a work ticket should remove the link where they control the destination.

1. Review prior Muse conversations that you shared outside your own account.
2. Remove shared links from documents, messages, and project tools if the chat includes sensitive details.
3. Change or monitor affected account information if a conversation contained a partial account number, fraud notice, password, or security code.
4. Use a new conversation with redacted details if you need AI help with a financial, employment, or personal matter.
5. Contact the relevant bank, employer, or service provider if a shared chat exposed information that could affect an account or workplace system.

Users should not treat deleting a pasted link as proof that every historical record disappeared. The direct risk is lower after Meta’s pause, based on Claroc’s recheck, but the hostname may remain in third-party passive-DNS history. Users who suspect account exposure should contact the affected institution rather than relying on an AI chat for recovery guidance.

Has Meta fixed the Muse sharing problem?

Meta has paused Muse sharing, but the available information does not confirm a permanent technical fix or a date for the feature’s return. Meta said it was suspending sharing while reviewing Claroc’s report. Claroc’s recheck found that 40 previously accessible shares no longer opened without an account after the pause.

A suspension is a containment measure, not necessarily a full explanation of what changed in the product architecture. A complete fix would need to prevent conversation titles and identifiers from being exposed through share-page hostnames, while also ensuring that any remaining shared pages use appropriate access controls. Meta has not publicly detailed those technical changes in the material available for this article.

The most sensible approach is to wait for Meta to explain whether it will restore sharing, what protections it has added, and whether existing users need to take further action. Reporting on Meta’s response notes that the company suspended the feature after being contacted about the research. The report on Meta’s response also describes the sensitive material involved.

How should users share AI conversations more safely?

AI conversations are safest to share only after users remove identifying details and confirm that the service provides explicit access controls. A shared chat can contain more than the final answer. It may include prior prompts, pasted records, attachments, browser task details, or information supplied through a connected service. Meta said Muse can act in a browser with user approval, which increases the importance of reviewing what a conversation contains before it leaves a private account.

Users should separate general questions from sensitive facts. For example, ask about the steps for disputing a fraudulent charge without pasting the alert, account information, or transaction history. Share a summary rather than a raw transcript when a colleague needs context, and use an organization-approved collaboration system for confidential work material.

AI agent security also requires caution when a tool acts beyond a chat window. Readers evaluating automated browsing should understand how AI agents can affect websites when they handle instructions and external pages. Stop using a sharing feature if its privacy settings are unclear, and ask the vendor or your employer’s security team for guidance before sharing regulated, client, or internal business information.

FAQ

Is Meta Muse chat sharing available now?

Meta Muse chat sharing is paused as of October 20, 2026. Meta suspended the feature while reviewing Claroc’s report that Muse share pages could be discovered through passive-DNS records.

Did DNS records expose every Muse conversation?

DNS records did not expose every Muse conversation, based on Claroc’s research. Claroc identified more than 6,800 share hostnames, and sampled pages included both harmless chats and some sensitive personal or business material.

Could people open Muse share pages without an account?

Some Muse share pages opened without a Muse account or sign-in before Meta paused sharing. Claroc said it accessed a few hundred sampled pages in an incognito browser, then found that 40 rechecked pages no longer opened after the pause.

Should Muse users delete old shared links?

Muse users should remove old shared links from places they control if the conversations contain sensitive information. Removing a link can reduce future exposure through that destination, although prior hostnames and titles may remain in passive-DNS history.

Has Meta said when Muse sharing will return?

Meta has not provided a public return date for Muse chat sharing in the available information. Users should wait for Meta to describe the technical changes and privacy protections before relying on the feature again.