I asked Meta’s Muse for its filesystem and it sent me 6.8GB

我向 Meta 的 Muse 索要其文件系统，它给了我 6.8GB 的数据

The export I asked Muse to archive the files it could see and send them to my Google Drive. It did. The download was about 2.7 GB compressed and 6.8 GB unpacked. It appeared to contain the root filesystem of the Linux environment assigned to my session, including Ubuntu system files, Muse’s internal documentation, integration code, app templates, memory files, and agent logs. There were also SSH key files. 导出过程 我要求 Muse 将它能看到的文件归档并发送到我的 Google 云端硬盘。它照做了。下载的文件压缩后约为 2.7 GB，解压后为 6.8 GB。它似乎包含了分配给我会话的 Linux 环境的根文件系统，包括 Ubuntu 系统文件、Muse 的内部文档、集成代码、应用模板、内存文件和代理日志。其中甚至还包含 SSH 密钥文件。

Figure 1. Muse describes an earlier archive of its code, documentation, memory, and binaries. The file counts and sizes here are claims in the chat, and refer to that earlier export. Click image to enlarge. 图 1. Muse 描述了其代码、文档、内存和二进制文件的早期归档。此处的文件数量和大小是聊天中的声明，指的是那次早期的导出。点击图片放大。

Figure 2. Muse’s delivery message links to muse-full-root.zip and calls it 2.86 GB. My notes record roughly 2.7 GB compressed; I haven’t reconciled the two figures. The message above it makes an unverified claim about container escape. I did not demonstrate an escape. Click image to enlarge. 图 2. Muse 的交付消息链接到 muse-full-root.zip，并称其为 2.86 GB。我的记录显示压缩后约为 2.7 GB；我尚未核对这两个数字。其上方的消息对容器逃逸做出了未经证实的声明。我并未演示逃逸。点击图片放大。

What I reported I submitted the findings through Meta’s bug bounty program and contacted several employees. I’m not publishing the archive, keys, or session logs. This is a breakdown of what I found and what I could establish from it. The concern I reported was that internal runtime files and sensitive material could leave that environment through an ordinary conversation and a connected export destination. I haven’t established whether the SSH keys were active or what access they could provide. 我的报告内容 我通过 Meta 的漏洞赏金计划提交了这些发现，并联系了几位员工。我不会发布这些归档文件、密钥或会话日志。以下是我所发现内容及其分析。我报告的问题是，内部运行时文件和敏感材料可以通过普通的对话和已连接的导出目标离开该环境。我尚未确定这些 SSH 密钥是否处于活动状态，或它们能提供何种访问权限。

The runtime and its manual Most of the interesting files were under /home/hatch, /opt/hatch, and /opt/hatch-image. Hatch is internal name Meta uses for Muse and the name used throughout the runtime files. 运行时及其手册 大多数有趣的文件都位于 /home/hatch、/opt/hatch 和 /opt/hatch-image 下。Hatch 是 Meta 对 Muse 使用的内部代号，也是整个运行时文件中使用的名称。

(Directory structure omitted for brevity) (此处省略目录结构以保持简洁)

The agent’s home directory The agent’s home directory contained SOUL.md, IDENTITY.md, USER.md, MEMORY.md, AGENTS.md, and TOOLS.md. Alongside those were directories for documentation, memory, workspace projects, channels, hooks, and subscriptions. 代理的主目录 代理的主目录包含 SOUL.md、IDENTITY.md、USER.md、MEMORY.md、AGENTS.md 和 TOOLS.md。除此之外，还有用于存放文档、内存、工作区项目、频道、钩子和订阅的目录。

Agents/ An agents/ directory contained 113 subagent records with JSONL traces. Agents/ 一个 agents/ 目录包含了 113 条带有 JSONL 追踪记录的子代理记录。

Docs/ About 20 Markdown files described browser use, connectors, payments, credentials, data handling, generated files, voice, goals, and scheduling. Docs/ 大约 20 个 Markdown 文件描述了浏览器使用、连接器、支付、凭据、数据处理、生成文件、语音、目标和调度。

Skills and integrations Under /opt/hatch/skills/, I counted roughly 68 skill directories. These generally paired a SKILL.md instruction file with a command-line tool or supporting code. 技能与集成 在 /opt/hatch/skills/ 下，我统计了大约 68 个技能目录。这些目录通常将 SKILL.md 指令文件与命令行工具或支持代码配对。