GitHub code-signing certificates stolen (but will be revoked this week)
There was a breach, so the bad news isn't great, but the good news isn't too bad...
Stay informed about the latest Github infosec updates, security breaches, and protection strategies with our comprehensive information security news.
Search across headline titles and summaries.
Background for this topic.
GitHub is a hosted software-development platform built around Git repositories. It supports public and private source-code hosting, change review through pull requests, issue tracking, automated workflows, and package distribution. Its repositories and automation are important security assets because they can contain proprietary code, deployment instructions, credentials, and the components used to build released software.
Material risks include accidentally committing secrets, exposing private repositories through misconfigured permissions, and allowing compromised dependencies or workflow actions to run in trusted build environments. Pull requests from untrusted contributors can also become an execution path when workflows handle them unsafely. Security practice includes least-privilege access, strong authentication, protected branches and required reviews, secret scanning and rapid credential revocation, and auditing workflow permissions. Repository history, dependency metadata, and commit provenance can support vulnerability management and incident investigation, but deleting a leaked secret from the latest file does not remove it from historical commits or existing clones.
Weekly headline count for the current query.
There was a breach, so the bad news isn't great, but the good news isn't too bad...
Latest episode - listen now! (Or read the transcript if you prefer.)
If you spew projects laced with hidden malware into an open source repository, don't waste your time telling us "no harm done" afterwards.
Latest episode - listen now!
Learn how to find out which apps you've given access rights to, and how to revoke those rights immediately in an emergency.
Training data stashed in GitHub by mistake... unfortunately, it was *real* data