ACCOUNT HACKED | Require reinstatement of main account

[shounak114-afk]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Code Search and Navigation

Body

Hey Community Team, I have raised a request for getting my main account back: Ticket ID: 4490182
Can anyone help me with this.

[Stark-SK]

Hi,

GitHub Community members won’t be able to directly access or speed up support tickets like Ticket ID: 4490182, since account recovery requests are handled only by GitHub Support for security reasons.

1 - The best thing you can do is wait for a response from the GitHub Support team through the email associated with your ticket.

2 - Make sure to check your inbox and spam/junk folders regularly in case they reply with verification questions or next steps.

3 - Avoid opening multiple tickets for the same issue, as this can slow down the handling process.

4 - If it has only been a few days, that is still within a normal response window for account recovery cases, which can take longer than standard support requests.

Unfortunately, no one in the Community forum can directly intervene in account recovery cases, but once Support responds, follow their instructions carefully and provide any requested proof of ownership as quickly as possible.

[GARJE-01]

The advice above is correct that only GitHub Support can restore access to a compromised account.

While you're waiting for a response, it may help to gather information that could assist with ownership verification if Support requests it, such as:

• Previous email addresses associated with the account.
• Approximate account creation date.
• Names of repositories you owned or maintained.
• Billing information (if the account had paid services).
• SSH public keys or GPG keys previously associated with the account.
• Recent GitHub login locations/devices you recognize.

I would avoid opening additional recovery tickets for the same account unless instructed by Support, since multiple tickets can sometimes make the review process harder to track.

For security reasons, the Community team and other users won't be able to access or review account recovery requests directly, so continuing through ticket #4490182 is the correct path.

[jojozepp]

Wouldn't touch copilot pro with a ten foot pole especially if you need any type of support. Any type, and I mean any type of account or payment problems will be met with crickets. Stay away at all costs. It really feels like copilot wants to die a quick death. I highkly suggest you all find alternatives. I did.

[shounak114-afk]

Bruh, how slow can one company be. there are clear signs of Personal Access Token Creation, changing of username, changing of primary email, removal of old email and setting it to gibberish, all in literally 15 minutes. Not even my mobile application is able to access this. They should really change the process, to be faster in such cases.

[GARJE-01]

The additional detail about the sequence of events makes this sound very different from a routine account-recovery request.

If the username, primary email, and account credentials were all changed within a very short timeframe, that provides a fairly strong indication that the account was compromised rather than intentionally modified by the account owner.

Unfortunately, GitHub Support is still the only team that can restore access or revert account changes, and community members cannot escalate recovery tickets directly. However, account-takeover cases often require ownership verification before any action can be taken, which may explain why the process takes longer than users expect.

A few suggestions while waiting:

• Continue using the existing support ticket rather than opening new ones.
• Keep any evidence of the compromise (emails about username changes, email changes, PAT creation, login alerts, screenshots, etc.).
• Reply promptly if Support requests verification information.
• Check all email folders regularly, including spam and junk folders.

I completely understand the frustration, especially when the activity appears obviously unauthorized from the account history. Hopefully Support can review the ticket soon and help restore access to the account.