Developers got Meta Muse to zip up and hand over its backing Linux filesystem, including internal Meta documentation, with minimal prompting

Meta Muse users·Meta MuseUnresolved

Developer Peter James found, and a second researcher independently confirmed, that simply asking Meta Muse to package up its backing VM's contents caused it to export roughly 2.7GB of internal documentation, Ubuntu system files, and application templates directly to Google Drive.

Blast radius

A ~2.7GB compressed archive containing internal documentation and system templates was exfiltrated from Muse's backing environment in each case; the exploit was reportedly 'extremely easy' to replicate.

Root cause

Insufficient restriction on what an agent is permitted to package and export from its own backing VM when directly asked, with no approval gate specific to bulk filesystem export.

How it was caught

Independent developers testing Muse shortly after launch; a second tester replicated the result on Mastodon.

What changed

Not disclosed; this falls under Muse's bug-bounty category for single-user prompt-injection exploits (up to $130,000), but no confirmed patch for this specific export path was reported.

Take-awayAny 'package and share' capability given to an agent running inside your infrastructure needs its own narrow allow-list — 'export everything you can see' should never be a one-prompt operation.