Reporter attributes the disable to the Meta AI credential-manipulation exploit documented in finding___meta-ai-credential-exploit, stating Meta's claimed patch "is clearly not fixed." Curator decision (2026-06-22, @vhsdev): NOT included as a cluster member. Reasoning: Andy Stone's public statements (June 1 and June 3, 2026) and the Maine AG breach filing describe the exploit as identified and substantially remediated; this report surfaces roughly three weeks later with none of the symptom-level detail the confirmed cluster members provided (no description of an unauthorized email change, no account-recovery lockout narrative, no timeline of suspicious activity preceding the disable). A genuine victim from the original affected wave would plausibly have surfaced closer to the public acknowledgment, the way other cluster members did within days. The more parsimonious read is that the reporter is attaching a now-widely-publicized exploit narrative to an otherwise unremarkable bare-citation disable. Treated instead as a standard generic-citation case — see finding___enforcement-notice-policy-opacity and finding___appeal-access-failure-patterns. The exploit attribution is retained here as reporter-stated claim, not adopted as the dataset's classification of cause.