GitHub Presses Big Red Password Reset Button After Third-Party Breach (theregister.co.uk)
John Leyden, writing for The Register: GitHub has reset the passwords of users targeted in an attack this week that relied on using stolen credentials from a breach at a third-party site. The software repository itself has not suffered a breach. Hackers behind the assault were trying to break into the accounts of users who had inadvisedly used the same login credentials on an unnamed site that had suffered a breach, as a statement by GitHub explains. GitHub said it had reset the passwords on all affected accounts before beginning the process of notifying those affected. "We encourage all users to practise good password hygiene and enable two-factor authentication to protect your account," GitHub sensibly advised.
Do anyone know which other third-party site was breached ? Or is it just an accumulated database of all historical breaches ..?
Good show, GitHub! I am very happy to see that they put security first and foremost.
I do say, it would have been a terrible disaster if somebody had breached the accounts of GitHub users, and done something dastardly like update some of the long-abandoned Rust libraries to actually compile with this week's Rust compiler, or made some badly needed bug fixes to the many JavaScript libraries that the original authors have lost interest in maintaining.
I've been surprised at the amount of intrusion attempts directly related to the Myspace leak, and how quick they started. One of my domains is a letter off from an ISP and its users routinely typo their addresses. I got an alert from HaveIBeenPwned that dozens of accounts on that domain were compromised in the Myspace leak, and the same day, bots started attacking those (non-existing) accounts through SSH and SMTP. The bad guys already have the infrastructure ready to go when a new leak comes out, they just plug in the list of credentials and start trying to login.
Hopefully they just send emails that say: 1. We have reset the password on your account because... hack.... 2. Next time you try to access your account, you will need to use the "reset password" feature
And please please DO NOT send a paypal style message that for security reasonz we need to verify your account, click here and tell us your social.
Just logged in and didn't have to reset my password.
I guess they don't say which percentage of accounts were affected.
If you aren't using it yet, you should. Indeed, I'd like all sites to enable 2-factor by default. It's not like most folks don't have phones or email accounts.
I work for a high-use API site, and I've been seeing these kinds of attacks regularly now for 6 months or more.
Basically, it's a barrage of user/pass attempts coming from hundreds, sometimes thousands of different IP addresses. I wrote custom filters to specifically identify these requests and black-hole them in the nginx proxy. Luckily, we require that 2FA is enabled on all accounts, so nothing seriously at risk,
I urge everyone to use 2FA on all sensitive sites where available. These kinds of attacks are going to become more commonplace.
I received an email that there was suspicious activity on my account, urging me to change my password. Since I don't know my password (I use a password manager), I looked it up. I'm 100% sure I have not used this particular password with any other account (it was 'randomly' generated by the password manager), so I guess they have emailed everyone.
Sig?