A click-fraud bot led me to 5,552 GitHub accounts tied to public inboxes
Comments on “A click-fraud bot led me to 5,552 GitHub accounts tied to public inboxes”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Security researcher Shmulik Cohen traced a GitHub Actions click-fraud bot, later joined by a crypto miner, to dormant accounts whose commit emails are public inboxes such as Mailinator, where anyone can receive a password reset. He counted 5,552 such accounts, 917 already running the workflow, and reset his own test account to confirm the route. GitHub closed his report as a known issue with no significant risk. These figures are his own, unverified; how the operator signs in remains unconfirmed. Platforms should treat old throwaway addresses as a gap.
Why it ranked
No. 17 of 137 with a score of 0.70. The panel rated it highest on new information (0.91) and reader interest (0.83), lowest on significance (0.58). Placed No. 17, No. 12 by score alone: the seventh Security story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Original security investigation with concrete method and data; strong practical advice on account hygiene. Some claims like the 5,552 count rest on the author's own counting, and the scope is a known gap rather than a landmark.}
- AI judgeJudge 3gpt-5.6-luna
- A well-evidenced investigation quantifies a broad GitHub account-takeover risk, demonstrates exploitability, traces campaign infrastructure, and provides actionable remediation. It is highly relevant to security-conscious builders, though some operator-attribution and scope details remain uncertain.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.70total under rubric v2.3
- Significance0.58
- Reader interest0.83
- Audience breadth0.65
- Practical relevance0.80
- Substantiated0.80
- Technical depth0.71
- New information0.91
- Counts against: Promotional0.03
- Counts against: Overclaim0.25
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) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.60 | 0.45 | 0.68 | 0.58 | 0.23 | +0.24 | +0.138 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.79 | 0.85 | 0.86 | 0.83 | 0.07 | +0.26 | +0.217 |
| Audience breadthHow many people who build technology does it concern? | 0.66 | 0.60 | 0.70 | 0.65 | 0.10 | +0.13 | +0.085 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.87 | 0.75 | 0.78 | 0.80 | 0.12 | +0.22 | +0.176 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.87 | 0.72 | 0.80 | 0.80 | 0.15 | +0.05 | +0.040 |
| Technical depthHow technically substantive is it? | 0.84 | 0.68 | 0.62 | 0.71 | 0.23 | +0.05 | +0.036 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.87 | 0.90 | 0.96 | 0.91 | 0.09 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.03 | 0.05 | 0.01 | 0.03 | 0.04 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.22 | 0.35 | 0.18 | 0.25 | 0.17 | −0.11 | −0.028 |
| Sum of contributions | +0.704 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.704 | ||||||
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-11-13/17/"><img src="https://rubric.hrih.si/badge/2026-11-13/17.svg" alt="Ranked #17 on Rubric, 13 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 8 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
On October 14, 2026, the author found 5,552 live GitHub accounts whose old commits used a public-inbox address.
The article gives no link or citation for it.
The article says “On October 14, 2026, I found 5,552 live accounts whose old commits used a public-inbox address”
The source says No source to compare with.
No source givenNumber
917 of the 5,552 accounts were already running the operator's workflow.
The article gives no link or citation for it.
The article says “917 of them were already running the operator's workflow”
The source says No source to compare with.
No source givenNumber
The campaign spanned 1,014 repositories owned by 965 accounts.
The article gives no link or citation for it.
The article says “1,014 repositories owned by 965 accounts”
The source says No source to compare with.
No source givenNumber
In 11 of the 19 compared accounts, the email on the new 2026 commit matched the email on the account's original commits.
The article gives no link or citation for it.
The article says “In 11 of the 19 accounts I compared, it was the same address”
The source says No source to compare with.
No source givenCausal conclusion
The author reset the password of their own old GitHub test account with a Mailinator address via the public inbox and signed in.
The article gives no link or citation for it.
The article says “The reset email landed in the public inbox. I opened the link, set a new password and signed in”
The source says No source to compare with.
No source givenNumber
Four days after the report, 18 accounts from the author's list of 860 added the campaign's workflow, between 14:12 and 14:49 UTC.
The article gives no link or citation for it.
The article says “Four days later, 18 accounts from that list added the campaign's workflow. The first at 14:12 UTC, the last at 14:49”
The source says No source to compare with.
No source givenNumber
On November 12, the Hugging Face dataset sjkhfuk1/foffo had 442 repositories fetching from it and 993,931 downloads in its 30-day counter.
The article gives no link or citation for it.
The article says “442 repositories were fetching from it, and its 30-day counter showed 993,931 downloads”
The source says No source to compare with.
No source givenQuote
GitHub closed the report as Informative, confirming the behavior and calling it a known issue without significant security risk.
The article gives no link or citation for it.
The article says “GitHub closed my report as Informative. They confirmed the behavior and called it a known issue without significant security risk”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 9 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:42 UTC. It played no part in the ranking.