Live data from Hacker News

Heroku Security Notification

status.heroku.com

81–90 of 123 posts

Re: Heroku Security Notification

#81
post #24
post #20

Interesting I had an OLD project associated with a Gmail email address that would send emails in some cases. Yesterday I got a notification that someone tried logging into that Gmail account. The password was hard coded in the code…

I too have seen something very similar to this. I am extremely nervous all my private repos got compromised. Watching this very closely.

I’m assuming they have been.

This email was a one off that outside this code exists nowhere else.

Re: Heroku Security Notification

#82
post #38

This is as good a time as any to ask about Render. I've been eyeing it recently and I'm thinking about launching my next project with it. Does anyone have any takeaways from using Render vs Heroku?

It’s alright but things are still flaky given they are smaller and newer. It hung on spinning up a postgres instance. Builds are slower as well.

Re: Heroku Security Notification

#83

We're a small org with a github connected to heroku. All of our repos were cloned between April 8 and April 15 with the majority of them having no activity for several years. The audit logs don't show this, you can only see this information in the traffic graphs (/graphs/traffic). If you're seeing cloning of repos that you haven't touched in a while, you've likely been compromised.

Might be a hint if you really have not touched them at all in years. In other cases this might also stem from CI tools like GH actions.

Re: Heroku Security Notification

#84

We're a small org with a github connected to heroku. All of our repos were cloned between April 8 and April 15 with the majority of them having no activity for several years. The audit logs don't show this, you can only see this information in the traffic graphs (/graphs/traffic). If you're seeing cloning of repos that you haven't touched in a while, you've likely been compromised.

Are you on an enterprise plan or a personal one? I know personal plans have limited logs, but I'd hope the enterprise ones would show clones (in reality, they both probably should). Kind of defeats the purpose of an audit log if it doesn't.

Re: Heroku Security Notification

#85

Earlier quoted context omitted.

Normal Heroku usage doesn’t download a zip because it uses git directly, but I’ve seen plenty of CI tools download zips.

Including Heroku CI? We don't use an external CI tool (or really any other integrations except GH), but I do see these download logs.

For what it's worth, elsewhere in this comment section someone posted that Github Support says the zip downloads weren't related to this incident. Reading between the lines, the compromised repos were probably accessed using normal git clone actions.

Re: Heroku Security Notification

#86

We're a small org with a github connected to heroku. All of our repos were cloned between April 8 and April 15 with the majority of them having no activity for several years. The audit logs don't show this, you can only see this information in the traffic graphs (/graphs/traffic). If you're seeing cloning of repos that you haven't touched in a while, you've likely been compromised.

Are you on an enterprise plan or a personal one? I know personal plans have limited logs, but I'd hope the enterprise ones would show clones (in reality, they both probably should). Kind of defeats the purpose of an audit log if it doesn't.

We're on the Team plan

Re: Heroku Security Notification

#88

We're a small org with a github connected to heroku. All of our repos were cloned between April 8 and April 15 with the majority of them having no activity for several years. The audit logs don't show this, you can only see this information in the traffic graphs (/graphs/traffic). If you're seeing cloning of repos that you haven't touched in a while, you've likely been compromised.

For anyone not on a pro plan: I believe you can upgrade and still see the past two weeks of data. I cloned a few of my private repos last night to see how that affects my security logs and no logs appeared. I later upgraded to pro and visited ///graphs/traffic and can see the clone counts from before I upgraded. I also can see visitor counts from about a week ago. These clones still don't appear in the security logs though.

Re: Heroku Security Notification

#89

Earlier quoted context omitted.

Including Heroku CI? We don't use an external CI tool (or really any other integrations except GH), but I do see these download logs.

For what it's worth, elsewhere in this comment section someone posted that Github Support says the zip downloads weren't related to this incident. Reading between the lines, the compromised repos were probably accessed using normal git clone actions.

That was me who posted that :) seems unrelated, but still hoping to get that figured out anyway.

Re: Heroku Security Notification

#90
I'm not a security expert, but if you're reading this and wondering what to do, a good start could be to just assume your repo was accessed, and so to run a tool like gitleaks against your repo. If it detects anything sensitive, I'd see about revoking/deleting those secrets right away.

In general, it's good practice not to check anything sensitive into source code for precisely this reason (if your code is compromised you don't want your secrets to be as well). So it'd also be good practice to add something like gitleaks into your CI/CD pipeline for the future.

Post reply on HN