{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigl3g3st5pipxze22wufzh5m6ap7ygijdjr5b6oa54obqf5vd2unm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mpqf24pyeb42"
  },
  "path": "/t/wrongful-cyber-abuse-deactivation-wave-requesting-human-escalation-case-id-c-b8svafvhcxqa/1385625#post_1",
  "publishedAt": "2026-07-03T09:39:41.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hello everyone and OpenAI team,\n\nI am posting here because I became a victim of the recent automated false-positive ban wave and my account was deactivated for alleged “Cyber Abuse”.\n\nMy automated appeal on the website was instantly rejected within 10 minutes by a bot (Case ID: C-b8SvaFvhcXqa), leaving me with absolutely no way to reach human oversight through the regular support channels.\n\n**Account details:**\n\n  * **User ID:** user-6R3SQmE5rzyl32nPRbiEEKvj\n\n\n\nI have used this account for years via a dedicated static IP address. I strictly utilize the official **Codex CLI** and **Hermes** framework for standard DevOps administration, configuring basic files, and content creation. I have 2FA enabled and have never shared my credentials.\n\nIt’s clear that the automated security classifier mistook benign system configuration scripts for malicious activity. Could a community manager or staff member please escalate this case to the specialized engineering team for a manual override? Years of my critical work history are currently locked due to a system glitch.\n\nThank you.",
  "title": "Wrongful \"Cyber Abuse\" Deactivation Wave - Requesting Human Escalation (Case ID: C-b8SvaFvhcXqa)"
}