- Change your password on https://hub.docker.com
- Check https://github.com/settings/security
- Reconnect oauth for Automated Builds
- Roll over effected passwords and API keys stored in private repos / containers
Quick take:
- Password hashes
- Github tokens
- Bitbucket tokens
- Your Automated Builds might need new tokens
Checking my github logs - It looks like they've known about this for at least a full 24 hours. Most people aren't going to have this looked at until Monday which kind of sucks. Hopefully there is more of a postmortem coming.
Is anyone from github able to comment on this as well?
There doesn't seem to be a way for us to tell if a repo was read by these keys over that time period.
For either method, you can audit the activity of your account on the GitHub security page: https://github.com/settings/security. For example, upon having deliberately got my 2FA token wrong, "user.two_factor_requested" and "user.failed_login" events were logged for me.
- Google: https://www.google.com/landing/2step/
- Github: https://github.com/settings/security
- AWS: http://aws.amazon.com/mfa/virtual_mfa_applications
- Facebook: https://www.facebook.com/settings?tab=security
- Twitter: https://twitter.com/settings/security
- Dropbox: https://www.dropbox.com/account/security
- Lastpass: http://helpdesk.lastpass.com/security-options/google-authent...
- More: https://twofactorauth.org/
"We have reviewed our logs and it doesn't appear that any actions were taken by the attacker other than to authorize the 'GitHub XRP Giveaway' application against your account.
You should be able to find the OAuth events for that application in your account's security history:
https://github.com/settings/security
We do not believe that the application's authors were responsible for the break-in, rather that the attackers were attempting to game the giveaway.
Ripple's explanation of the giveaway can be found here: https://ripple.com/blog/git-in-the-game-2020-xrp-giveaway-fo...
Also recommend enabling 2 factor authentication.
Recommend enabling 2 factor auth.
Edit: There are also logs for your organization in https://github.com/organizations//setting...