My GitHub Account Suspended – False Report Investigation & Appeal | Anurag Gautam
🚨 My GitHub Account Was Suspended — I Believe It Was Due to a False Report
Hello everyone — my name is Anurag Gautam, and I am writing this post to document a serious incident related to my developer journey.
My GitHub account anuxagfr was recently suspended. After carefully reviewing my own activity and investigating the possible sources of this action, I genuinely believe that the suspension was triggered by a false, malicious, or automated report, not by any intentional violation from my side.
- Present a clear record of what happened.
- Share the investigation and evidence I found.
- Ask GitHub for a fair and transparent review.
- Help other developers understand how false reports can impact them.
📌 GitHub Suspension Overview
| GitHub Username | anuxagfr |
|---|---|
| Status | Suspended |
| Support Ticket ID | #3923113 |
| Reason Displayed | Security / Misuse report (no detailed explanation provided) |
Despite this, my account was locked. All my repositories, experiments, and learning history became inaccessible in a single moment. For any developer, this is not just a simple “account issue” — it is a direct hit on months or years of hard work.
🔍 How I Started Investigating the Suspension
When I saw the suspension notice, the first step was to double-check my own activity: I reviewed my commits, repositories, and recent logins. I found nothing that looked suspicious or outside normal developer use.
Next, I searched online to see if there was any reference to my username or IP in public security or abuse reports. While doing this, I came across the following search result:
https://www.google.com/search?q=dugganusa.com
From there, I found a related blog post:
https://www.dugganusa.com/post/dear-github-security-you-re-welcome
The overall tone and activity on this site raised questions, especially when combined with other factors I describe below.
📂 Evidence #1 — Unnatural Blog Posting Activity
The blog connected to this case appears to have an extremely unusual posting pattern. Based on the visible archive data (as seen in the screenshot I checked), the monthly post counts looked like this:
| Month | Number of Posts |
|---|---|
| December 2025 | 27 |
| November 2025 | 5727+ |
| October 2025 | 138 |
| September 2025 | 12 |
| August 2025 | 21 |
- Publishing more than 5700 posts in a single month is extremely unlikely for a single human operator.
- Many posts appear to have little to no views, as if they were generated only to fill the site with “activity.”
- This kind of pattern is consistent with automated or scripted posting, not natural content creation.
When such a source is involved in reporting accounts, it raises a very important question: Should automated or suspiciously-generated content be trusted as a primary basis for serious actions (like suspending a developer’s account)?
📂 Evidence #2 — GitHub Profile Potentially Linked to Reports
A GitHub profile associated with this activity (from the screenshot I saw) contains the following information:
| Username | pduggusa |
|---|---|
| Name | dugganusa |
| Bio | "Deploying, Breaking, Repeating" |
| Linked Profiles | security.dugganusa.com · ORCID · LinkedIn |
| Observed Pattern | Security-themed, with possible focus on reporting/suspension-related content. |
- Appears very focused on “breaking” and security actions.
- May be involved in repeated reporting activity against other accounts.
- Could be using automated tools or mass-reporting strategies.
When taken together with the abnormal blog posting history, this suggests that my account might have been caught in a wave of aggressive or automated reporting rather than a careful, manual review of my actual behavior.
🧾 Additional Context — My Other Accounts Were Hacked
Another important piece of context is that, around the same time period:
- My Instagram account was hacked.
- My Facebook account experienced unauthorized access.
- If my credentials or identity were compromised, someone else could have abused them.
- A third party might have used my devices, IP address, or accounts to generate activity that was later misinterpreted or reported.
- This creates a realistic possibility that I am being framed, or that my accounts were misused in a way that triggered automated flags.
Because of this, I believe it is essential that GitHub checks not only the report itself, but also the origin of the report and the pattern of login/IP activity on my account.
💬 My Official Request to GitHub
- A manual review of my account suspension, instead of only automated checks.
- A review of the reporting source, including its activity history and credibility.
- Verification of whether my GitHub activity truly violates any policy (I am confident it does not).
- Restoration of my account
anuxagfrso I can continue my work and learning.
I fully respect GitHub’s need to protect the platform from abuse, malware, and attacks. My request is not against security — it is a request to ensure that the same security system is not misused against innocent developers.
📊 Timeline Summary (At a Glance)
Key timeline:
- 🔐 Social accounts (Instagram & Facebook) hacked / accessed without permission.
- 🔍 I begin investigating unusual patterns and possible connections.
- 🌐 I discover dugganusa.com, the blog activity, and the related post.
- 👤 I notice a security-themed GitHub profile apparently linked to multiple reports.
- 🚫 My GitHub account
anuxagfris suspended based on a security/misuse flag.
| Date / Event | Details |
|---|---|
| Social Media Incidents | Instagram & Facebook compromised around same period. |
| Blog Discovery | Found 5727+ posts in November 2025 from dugganusa-related site. |
| GitHub Profile Observation | Profile pduggusa / dugganusa with strong security-breaking focus. |
| GitHub Suspension | Account anuxagfr suspended under “security / misuse” category. |
To me, this pattern is too aligned to be a coincidence, and it deserves careful review.
⚠ Why This Case Matters for Other Developers
This is not just about my single account. If automated or suspicious reporting from external sources can trigger a permanent or long-term suspension, then:
- Any innocent developer could lose their account due to false accusations.
- Hacked accounts could be used to generate activity that later appears “malicious.”
- Security systems could be abused by individuals with personal agendas.
📩 Contact / Verification Details
| Name | Anurag Gautam |
|---|---|
| amitgautam4570@gmail.com | |
| Affected GitHub Account | anuxagfr |
I am fully willing to cooperate with any investigation or security verification GitHub wishes to perform. I can provide additional context, device information, or any logs that may help clarify the situation.
🔍 Final Words
GitHub has always been an important part of my learning and professional growth. I appreciate the platform and its role in the developer community. My only request is a fair re-evaluation of this suspension, with attention to the evidence and patterns I have outlined here.
If you are part of GitHub’s support or security team, thank you for reading this. If you are a fellow developer, I hope this post reminds you how important it is to secure your accounts and keep your own records and backups.

Join the conversation