platform_acknowledged: true). See methodology.
@soycarmencuevas publicly reports that Meta disabled their Instagram account (@carmencuevas01) on December 12, 2025, reportedly for unspecified Community Standards violations, with no prior notice or specific policy cited. The account was restored on May 20, 2026 — following a Meta Verified Support representative's informal acknowledgment that the initial disable was an error — and then re-disabled on May 25, 2026, five days after restoration. The reporter attributes the re-disable to exploitation of Meta AI's support chat system, which allegedly allowed unauthorized access attempts against Instagram accounts.
Sources
Research patterns
All findings →Experienced something similar? See Resources for escalation paths by jurisdiction—EU/DSA, India, Turkey, and more. For US-based cases, Signal Flare covers the full stack: state Attorneys General, the FTC, and congressional offices.
This record is published under GDPR Art 89 public interest exemption. Data policy
Are you the subject of this record? Request erasure
This is a multi-stage enforcement case spanning two distinct events separated by a 5-month limbo period. Event 1 (Dec 12, 2025): initial disable — opaque, no content cited, no policy sub-citation. Reporter submitted video selfie and government-issued ID and was placed in a 'permanent review process' for nearly five months with zero human contact. Event 2 (May 25, 2026): re-disable five days after restoration — reporter explicitly attributes this to 'exploitation of Meta AI's support chat system, which allowed unauthorized access attempts against Instagram accounts.' This mechanism maps directly to the Meta AI exploit cluster (PA-2026-0024, PA-2026-0032, PA-2026-0033). The initial disable is analytically most likely an automated DETECTION event (anomalous signals, no content cited); ai_system_involvement is set to DETECTION to cover the initial trigger. The re-disable mechanism is noted separately here. platform_acknowledged is set to false: a Meta Verified Support representative informally confirmed the initial disable was 'an error' and escalated to a specialized team during an April 27, 2026 contact via a secondary account, but this is an informal channel acknowledgment, not a public Meta statement. This is the first informal platform acknowledgment in the dataset that resulted in restoration followed by re-enforcement — making it analytically distinct from PA-2026-0018 and PA-2026-0027, where restoration was the terminal state. The re-enforcement cluster (PA-2026-0018, PA-2026-0027) and the Meta AI exploit cluster (PA-2026-0024, PA-2026-0032, PA-2026-0033) both apply here, making this a convergence case. Personal harm profile is among the most acute in the dataset: voice messages from reporter's late father lost in DMs. Engagement (27M impressions, 160 replies) is the highest single-post figure in the dataset by a significant margin. 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.