Suspicious workflows held for approval before execution

Recent supply chain attacks use compromised GitHub credentials to push malicious GitHub Actions workflows that steal CI/CD credentials and carry out additional attacks. To help protect public repositories from these attacks, GitHub Actions now holds certain workflow runs for approval before they start.

When a workflow run is identified as potentially malicious and held, the workflow won’t execute until a repository collaborator with write access reviews and approves it. The approval must be submitted through an authenticated web session. Once approved, the workflow continues normally.

You don’t need to configure this protection; GitHub applies it automatically.

This protection currently applies to public repositories on github.com only. GitHub Enterprise Server doesn’t add this protection at this time.

The post GitHub Actions holds potentially malicious workflows for approval appeared first on The GitHub Blog.