Skip to content- Sources: primary, discussion
- Summary: Since 2026-09-15 the Gheist tool has committed .github/workflows/sync-check.yml on ci-sync- branches, printing base32-encoded secrets to the job log, downloading the log through the API and deleting the run. GitHub's approval hold for public repositories blocked every public run Wiz checked, but runs completed in private repositories and GitHub Enterprise Server, and a later variant targets self-hosted runners to sweep host credentials. Wiz says the campaign was ongoing and evolving as of 2026-10-24.
- Why it matters: Private repository and GHES owners should hunt for ci-sync branches and the gheist user agent, rotate every secret an affected repository could reach, and scope OIDC trust to protected branches.