Distinct incident pattern: reporter describes a sequence of account theft followed by disable, rather than direct enforcement against the account holder. The stated mechanism — 'stolen overnight via the Meta AI exploit' — is reporter-attributed and unverified. The precise nature of the alleged exploit is not described in the available source text. The disable may have been triggered by activity on the compromised account after theft, rather than by the account holder's own conduct — a qualitatively different enforcement trigger than all other records in the dataset. ai_system_involvement set to UNKNOWN: the enforcement mechanism is unconfirmed, and the 'Meta AI exploit' attribution relates to the alleged theft vector, not necessarily to the enforcement decision itself. Policy citation is bare 'Community Standards' with no section — consistent with [[finding___enforcement-notice-policy-opacity]]; third record with this exact bare citation (after PA-2026-0002 and PA-2026-0015). No appeal possible: 'You cannot request another review of this decision' — permanent disable with no residual avenue. Meta Verified status and facial scan verification did not prevent the disable. Account handle @korn is a high-value username, potentially motivating targeted account theft. Engagement: 975K views, 8.3K likes, 672 retweets — highest in the dataset by significant margin, indicating broad public attention to this incident. Livelihood impact explicitly stated: 'the account is the sole source of my income.' Six hours of unsuccessful human support attempts consistent with [[finding___appeal-access-failure-patterns]]. Screenshots and archive captured by @vhsdev on 2026-06-02, curator: @vhsdev. Follow-up statement by reporter (curator-provided, source URL not captured): 'I had MFA/2FA on, account verified, facial scan, id scanned, everything protected. The exploit bypassed all of that, that's why it's an exploit.' This directly addresses the inference that verification layers might have been absent or insufficient — the reporter explicitly states all standard protections were active and bypassed. Parallels PA-2026-0001, where the curator also experienced unsolicited MFA challenges consistent with a third-party bypass attempt on a protected account. Public acknowledgment update (2026-06-06): Andy Stone (@andymstone, Meta Director of Policy Communications) publicly stated on June 1, 2026: 'This issue has been resolved and we are securing impacted accounts.' This constitutes the strongest platform acknowledgment in the dataset — a named senior official public statement explicitly addressing the exploit mechanism underlying this enforcement cluster. platform_acknowledged updated to true; confidence_score updated to 5. Second Andy Stone statement (June 3, 2026): Stone stated Meta is 'now working to restore access to affected individuals' — an explicit admission that affected accounts had not yet been restored as of June 3, stronger than the June 1 statement. The @manipulate post in the same thread documents the exploit was still active June 2, almost two days after the claimed patch, and offers the analytical framing that 'AI is not linear. The exploit evolves so long as the tooling is still there' — explaining why a patch may not hold against an evolving AI-driven attack vector.