Meta has suspended a Muse conversation-sharing feature after researchers showed how public DNS records could lead people to sensitive personal and business documents. The problem was in the address: Muse included the conversation’s title in a share-page hostname, making its subject discoverable in records of domain lookups.[1]
Claroc’s research team found more than 6,800 hostnames after filtering out scanning noise and opened a few hundred pages. Most were harmless, it said; a minority exposed material such as personal financial paperwork and internal business documents. The hostname count describes discoverable shares, not a count of confirmed sensitive-document exposures.[1]
A title became a discovery route
A share link is often treated as something a user distributes to chosen recipients. In Muse’s design, people with the link could open the page without signing in. Claroc found that the descriptive title and identifier embedded in the hostname also made it possible to reconstruct links from passive-DNS results. The link could therefore reach someone who had never been sent it.[1]
DNS translates domain names into the addresses browsers use to reach servers. Passive-DNS services retain observations of those lookups. A descriptive hostname can consequently reveal information even when a page is excluded from search-engine indexing. A crawler rule controls cooperative crawling; it does not require a visitor to authenticate.[1]
How the exposure worked
| Stage | Muse behaviour described by Claroc | Consequence |
|---|---|---|
| Share creation | Publishes a conversation at a link | Anyone with the link can open it |
| Address construction | Includes the conversation title in the hostname | The address itself describes the content |
| DNS observation | Lookup records enter passive-DNS history | Shares can be discovered outside search engines |
| Feature suspension | Previously accessible pages stop opening | Historical hostnames can still retain titles |
Access closed; the address history remained
After Ars Technica asked Meta about the findings, the company said on October 20 that it was suspending the feature, according to the reporting linked in Claroc’s update. Claroc then rechecked 40 shares it had previously opened without an account. None opened, and the content-serving hostnames returned an error. The researchers said the titles were still present in passive-DNS history.[1]
That distinction explains why closing a page and removing its traces are separate tasks. Disabling access prevents a new visitor from retrieving the document through that route. It does not necessarily remove an address already recorded by another service. A title may itself reveal a project, transaction or personal matter even after the underlying page disappears.
The design lesson is specific: sharing controls must account for what an address discloses, as well as who can load the page. Non-descriptive identifiers reduce information in the hostname; authentication and revocation govern access to the content. Together, those choices make the audience for a shared conversation much easier to define.
Sources & further reading
- GhostShares: A Shared Muse Chat Exposed Prep for a Confidential Call With a Frontier AI Lab Leader Claroc Research · 18 Oct 2026 · Accessed 25 Oct 2026