Reducing the value of a stolen GitHub token
Evidence-based analysis of the Gheist GitHub Actions secret-exfiltration campaign and GitHub Enterprise exposure management.
Tag archive
Evidence-based analysis of the Gheist GitHub Actions secret-exfiltration campaign and GitHub Enterprise exposure management.
Evidence-based analysis of the Gheist GitHub Actions secret-exfiltration campaign and GitHub Enterprise exposure management.
GitLab Secrets Manager is generally available in GitLab 19.5 for Premium and Ultimate. Built on OpenBao, it hands a credential only to jobs that declare it and match its branch and environment scope, and every CI/CD read is logged with its pipeline and job ID.
Researcher Joe Leon of Aikido Security disclosed that GitLab's incoming-email addresses embed a long-lived, cross-project token that lets anyone holding the address submit patches, run CI/CD and reach the account's secrets.

Security Quality Gates in GitHub, GitLab & Bitbucket Learn how to enforce security...
When a rogue container slips into production, the fallout can be catastrophic. Discover how build signing and Sigstore lock down your CI/CD chain, giving attack

Secrets Scanning in CI/CD: Stop Token Leaks Discover how API keys and tokens end up in...
A Docker-sponsored Omdia report pegs the twelve-month software supply-chain incident rate at 77 percent of surveyed organizations, with AI technology now ranked as the top supply-chain risk. The tool-effectiveness table rewards the sponsor's product category.
Google's Threat Intelligence Group and Mandiant have released a joint guide on defending against software supply chain compromise, mapping four control categories onto the concrete pipeline levers most teams already own: short-lived tokens, ephemeral runners, package cooldowns and dependency verification.
GitHub has flipped Actions into a hold-first posture for workflow runs it flags as potentially malicious on public repositories: the run pauses until a collaborator with write access approves it from an authenticated web session. The change targets a wave of credential-theft attacks that push booby-trapped workflow files with stolen tokens.
Novee Security disclosed a CI/CD flaw pattern, Cordyceps, that an unauthenticated actor can use to plant self-propagating triggers across pipelines. The specifics matter less than the shape: pipelines keep landing on the attack surface, and organizations keep treating them like build tools.
The Megalodon campaign injected malicious CI/CD workflows into 5,561 repos using forged bot identities. Cloud credentials, SSH keys, and OIDC tokens were harvested at scale. Here's what happened and how to protect your pipeline.