You know those moments when you’re deep in a rabbit hole and suddenly land on a repo that just blows your mind—maybe it solves a problem you didn’t know you had, or it’s just brilliantly written? Share your accidental gems—I need some fresh inspiration!
I just learned an expensive lesson and wanted to share this nightmare with you all. Maybe save someone else from the same mistake.
What happened:
- Was working on a SaaS project, quickly committed some environment files with AWS access keys to a private GitHub repo
- Thought "it's private, no big deal, I'll clean it up later"
- 4 hours later: AWS bill notification for $726.31
- Turns out someone spun up multiple EC2 instances, RDS databases, and was mining crypto (maybe)
Here's what I don't understand:
How did this even happen with a PRIVATE repository? I always thought private meant... well, private. Did GitHub have a breach? Is there some scanning that happens even on private repos? Or did I mess up somewhere else?
The AWS keys were literally added in that same day, so this wasn't some old exposure. Someone found them within hours of the commit.
Questions for the community:
How do attackers even find keys in private repos so quickly?
What tools do you use to scan your codebase for exposed credentials before commits?
Any recommendations for preventing this in the future? (Besides the obvious "don't commit keys")
Has anyone else experienced this with private repos specifically?
I've already:
- Revoked all AWS keys
- Set up AWS billing alerts (should have done this ages ago)
- Started using AWS Secrets Manager
- Enabled MFA on everything
But I'm still confused about the attack vector here. Any insights would be super helpful.
Update: AWS was understanding about the situation and credited most of the charges, but lesson learned the hard way.
GitHub.io and GitHub.dev have understandably (from the school's perspective) been blocked for years. As github.io could allow students to make game sites and GitHub.dev allows port forwarding through code spaces allowing to bypass blocks.
But I feel GitHub.com takes it to another level. We heard about this in March and our CS teachers allowed us write complents back to our network admins about why GitHub is useful. They said they would consider our opinions but today on the first day of school it was blocked.
The reason they provided is that students can share files to each other on GitHub. But like as students we have access to an unlimited Google drive account, email and like 5 other services that would be easier to share files among students than GitHub. Also all school supplied computers are Chromebooks except or exclusively the cs classrooms. Making GitHub really the only realistic way to save your code and work on it at home as other git websites are already blocked.
I actually see no reason for this every reason I think of either does make sense or has a better solution like.
Here is a few:
GitHub provides ai access - Just block GitHub.com/models also every other ai site besides chatgpt is unblocked so it doesn't seem like a priority.
GitHub could be used to download/find malware/exploits - if it is really such a concern any dedicated enough to find exploits on GitHub can find a way to read them outside of GitHub. Plus they could just block an repos on a case by case basis. We have a strict antivirus on cs computers and Chromebooks don't even have executables.
We also tried asking the school to allow ssh access to only [email protected] as there is no shell access and would only be used to pull/push, they declined as this was an "obviously impossible request for our security standards"
I'm actually so annoyed hopefully they get enough push back from ours clubs/classes but I am doubtful.
A while back I created an open-source web tool which included 2 months of research (chemical compositions, absorption rates, etc.) and implementation. I chose MIT as a license because it's just a small tool and I wanted anyone to be able to use and modify it.
I recently got a notification that someone starred and forked the repo. I was excited to maybe see someone contributing (even though in most forks nothing happens at all, at least in my case). I love the idea of someone adding new ideas, fixes or just modifying the code for something else.
I went to check out the fork but couldn't find it anymore. What happened? They removed the git history, re-initialized the repository, pushed it with some alibi commits and linked it to their portfolio (while keeping my name in the MIT license lol).
Yes, it's MIT and they can do whatever they want with my code and it's the reality of open source. But this just feels cheap and somehow kills motivation to continue contributing to open source.
How often does this happen to you? Maybe I should change my licensing to something else?
TL;DR (AI): I open-sourced a tool (MIT). Someone forked it, wiped the commit history to hide my authorship, and is claiming it as their own work for a portfolio. It's technically allowed (mostly), but incredibly annoying.
Before anything else: this is not an account recovery request.
This is about what happens when a support flow stops leading to a human being — or breaks due to a UI inconsistency that made it into production.
Right now, accounts can be flagged by automated systems or false reports and pushed into a dead loop. That is a serious failure mode, and there is currently no clear way out of it.
When an account gets flagged, it can effectively disappear — along with all of its repositories.
And what if you have maintained that repository for over 9 years, it is used by more than 230,000 projects, and it has thousands of stars? Apparently none of that matters. It still gets handled entirely by automation.
You do not get a proper explanation. You do not get a clear reason. Your account just disappears — no prior notice, no warning, no follow-up.
Then you open a ticket, and you automatically receive a response telling you that, if you do not want to see that message again, you should check a box confirming you have already contacted GitHub about this issue.
So you open another ticket — but there is no field where you can answer “yes” to that question.
So what do you do? You fill out the form, include the previous ticket number to show that you already contacted GitHub — and what happens?
You receive the exact same automated response again, telling you to check a box that does not exist.
That is not an appeal process. It is a dead loop.
The most disturbing part is not that systems can make mistakes. Any system can fail.
The disturbing part is that human review — the absolute minimum in a case like this — is no longer reachable.
And that is where this stops being about one account and starts becoming a trust problem.
Because trust in a platform starts to collapse when:
- automation can flag you
- automation can close your appeal
- and the official instructions send you to a step that no longer exists
At that point, this is no longer just a bad suspension.
It is a production failure in a system people rely on for work, reputation, open source, and income.
And if this can happen to someone maintaining code used by 230K+ projects, it can happen to anyone.
Including you.
---
Note:
I’m not asking for a review of my case. I’m not asking for privileges or priority.
I’m asking for something much more basic: a support process that is real, consistent, and reachable.
Because right now, this is not just about one account, one project, or one developer.
It’s about what happens when a system people depend on for work and income fails in a way they cannot recover from.
My income depends entirely on open source. Today, I genuinely don’t know how I’m going to pay rent next month or even cover basic expenses in the coming weeks.
But this is not about sympathy.
This is about a production system that, in its current state, can silently remove someone’s work, reputation, and livelihood — without a functioning path to resolution.
Ok this is very strange. I'm setting up a new computer so I generated a new SSH key for the machine and set it up on GitHub. Then I cloned one of my (private) repos via the SSH option. I made some edits, committed it, and tried to push. It then asked me for my username and email.
I'll replace the username with "boogerbuttcheek". Just keep in mind that it's pretty specific to me...
I accidentally inputted "[email protected]" as my email. I pushed and on GitHub it showed a random account as the author of the commit! The user is apparently from India?!
I ended up setting my email to the correct one, amending the commit, and pushing. Now the commit shows it being authored by me. However I'm concerned about the security of my GitHub account...
Why would this random user have "[email protected]" associated with their account? It's highly specific, and I also don't think I have the exact same name as a dude in India (although I guess it's possible).
Is it possible he saw my username online and decided to connect his GitHub account with that username? Why would it be 12345678?
I submitted a ticket to GitHub but it's Friday so... I appreciate any insight.
Some of my friends like the programs that make my desktop good, and then when they say “where do I get that?” I say it’s on GitHub and then they say “oh isn’t that the website where hackers upload stuff?”
What is a good explanation on why people on GitHub isn’t a hackers website?
Also they get bored immediately when I try to tell them.
Recently, I see a a zillion posts about new open-source projects. Like 10-20 a day. It’s crazy.
It’s pretty obvious that most of them are vibe-coded.
And nothing against vibe coding, it’s just that I think most of these projects are useless.
They are tailored to specific case, obviously really easy to create and will be completely unmaintained from the moment of inception.
Like nothing against people creating tools, but what’s the point of posting them here?
Edit: I also find it disingenuous to call these tools “open source projects”.
An open source project is when somebody with domain knowledge dedicates their free time to create something for the public, not when somebody prompts an AI to generate a tool.
That's on the same level as releasing your MidJourney images under a Creative Commons license.