Gheist campaign plants secret-dumping workflows using stolen GitHub tokens
Comments on “Gheist campaign plants secret-dumping workflows using stolen GitHub tokens”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Wiz Research reports Gheist, a campaign that uses stolen GitHub tokens to push a sync-check workflow to every reachable repository, dump secrets into the run log in base32 to evade masking, fetch the log through the API, and delete the run. Wiz recovered over 13,500 branches from 850+ accounts. GitHub's approval hold stopped public-repo runs, but not private or Enterprise Server ones, where cloud credentials were later used. Wiz's figures are self-reported; rotate exposed secrets and scope OIDC trust to protected branches.
Why it ranked
No. 1 of 62 with a score of 0.81. The panel rated it highest on new information (0.95) and practical relevance (0.93), lowest on audience breadth (0.71).
Every answer behind this is in the table under Score.
Score
0.81total under rubric v2.2
- Significance0.73
- Reader interest0.90
- Audience breadth0.71
- Practical relevance0.93
- Substantiated0.87
- Technical depth0.93
- New information0.95
- Counts against: Promotional0.08
- Counts against: Overclaim0.13
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| Significance | 0.71 | 0.62 | 0.86 | 0.73 | 0.24 | +0.24 | +0.175 |
| Reader interest | 0.86 | 0.88 | 0.97 | 0.90 | 0.11 | +0.26 | +0.235 |
| Audience breadth | 0.69 | 0.72 | 0.72 | 0.71 | 0.03 | +0.13 | +0.092 |
| Practical relevance | 0.95 | 0.90 | 0.94 | 0.93 | 0.05 | +0.22 | +0.204 |
| Substantiated | 0.91 | 0.80 | 0.90 | 0.87 | 0.11 | +0.05 | +0.043 |
| Technical depth | 0.99 | 0.88 | 0.91 | 0.93 | 0.12 | +0.05 | +0.046 |
| New information | 0.94 | 0.93 | 0.99 | 0.95 | 0.06 | +0.05 | +0.048 |
| Promotional | 0.04 | 0.12 | 0.08 | 0.08 | 0.08 | −0.19 | −0.015 |
| Overclaim | 0.13 | 0.15 | 0.12 | 0.13 | 0.03 | −0.11 | −0.015 |
| Sum of contributions | +0.814 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.814 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-26/1/"><img src="https://rubric.hrih.si/badge/2026-10-26/1.svg" alt="Ranked #1 on Rubric, 26 Oct 2026" width="238" height="28"></a>Claim check
Claim check: 1 matches source · 7 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
Wiz Research recovered more than 13,500 planted branches from more than 850 compromised accounts in the Gheist campaign.
The article gives no link or citation for it.
The article says “We have recovered more than 13,500 planted branches from more than 850 compromised accounts”
The source says No source to compare with.
No source givenDate
Wiz Research has been tracking the Gheist campaign since September 15, 2026.
The article gives no link or citation for it.
The article says “Since September 15, 2026, Wiz Research has been tracking Gheist”
The source says No source to compare with.
No source givenNumber
Roughly two-thirds of implicated accounts were no longer available on GitHub as of October 24.
The article gives no link or citation for it.
The article says “roughly ⅔ of implicated accounts are no longer available on GitHub”
The source says No source to compare with.
Matches sourceDate
Since July 28, 2026, GitHub has held potentially malicious workflow runs in public repositories until a collaborator approves them.
The cited source says the same thing.
The article says “Since July 28, 2026, GitHub has held potentially malicious workflow runs in public repositories until a collaborator approves them”
The source says “GitHub Actions now holds certain workflow runs for approval before they start”
Source cited by the article: github.blog/changelog/2026-07-28-github-actions-holds-potentially-malicious-workflows-for-approval
No source givenCausal conclusion
Every public Gheist run Wiz checked sat at action_required, so the malicious payloads never ran in public repositories.
The article gives no link or citation for it.
The article says “Every public Gheist run we checked, across all variants including the self-hosted job, sits at action_required. The control worked, and the malicious payloads never ran”
The source says No source to compare with.
No source givenCausal conclusion
GitHub's approval hold does not apply to private repositories or GitHub Enterprise Server, where Actions ran on attacker branches without approval.
The article gives no link or citation for it.
The article says “that hold doesn't apply to private repositories or GitHub Enterprise Server”
The source says No source to compare with.
No source givenNumber
On October 6, 391 accounts renamed about 1,461 repositories to cracked-software lures, wiping 610 ci-sync branches as a side effect.
The article gives no link or citation for it.
The article says “On October 6, 391 accounts renamed about 1,461 repositories to cracked-software lures like fl-studio-crack and solana-sniper-lite. The rename wiped 610 ci-sync branches as a side effect”
The source says No source to compare with.
No source givenNumber
57 accounts from Gheist's first phase were also victims of the Megalodon campaign in May.
The article gives no link or citation for it.
The article says “57 accounts from Gheist's first phase were also victims of Megalodon in May”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 47 pts, front page
Recorded for context only, checked 26 Oct 2026, 07:27 UTC. It played no part in the ranking.