Urgent: Ticket ID 4701050 - Compromised account recovery pending since Aug 26 #208486
Replies: 4 comments 3 replies
|
Sorry you're dealing with this. Since this involves a compromised account and an existing support ticket, I don't think another community member can safely resolve the underlying issue here. I'd avoid posting any sensitive ownership information, recovery codes, passwords, or private SSH material in this discussion. Since you already have Ticket #4701050 open, the safest path is to keep all account-verification details inside the official GitHub Support ticket and continue following up there. Hopefully a GitHub Support/security staff member can pick up the ticket and verify ownership through the appropriate process. |
|
If you feel my response sufficiently answered the discussion, feel free to mark it as the answer whenever you think it's appropriate. And if you need anything else from my side, just let me know. 👍 |
This comment was marked as low quality.
This comment was marked as low quality.
|
Ugh, four weeks with zero response on a compromised account is brutal. Have you tried pinging GitHub Support directly via Twitter/X (@githubsupport)? Sometimes public tags there get a faster pair of eyes on stuck tickets than community forums. Hope you get back in soon! |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Other
Body
Hello,
My account (Amurgas31) was compromised on August 26, and the unauthorized actor changed the password and 2FA settings. I submitted a support ticket on the same day (Ticket ID: 4701050).
All associated email accounts were immediately secured, and I replied to the support thread with additional details, but I have not received a human response in nearly four weeks.
I am facing critical academic and project deadlines. Could a moderator please help escalate this ticket to the security team? I am ready to provide any required ownership verification (SSH keys, local commit logs, etc.).
Thank you.
All reactions