Edition of Friday 30 October 2026

Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour

Comments on “Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Radware researchers report at least 83 attacks on 61 public GitHub repositories, including Trivy, MLflow, Brave and Google LangExtract, with 77 of them posted within 43 minutes on September 1. Malicious commands were hidden in HTML comments inside issues, pull requests or comments, aiming to run in CI/CD workflows and steal credentials. Radware suspects one coordinated attacker using 74 likely compromised accounts. The findings are Radware's own assessment, with no independent confirmation cited. Teams should review which events trigger their workflows.

Read the original at theregister.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 15 of 127 with a score of 0.73. The panel rated it highest on new information (0.88) and reader interest (0.87), lowest on substantiated (0.59). Placed No. 15, No. 9 by score alone: the seventh Security story of the day (−0.080), and close to “Gheist campaign plants secret-dumping workflows using stolen GitHub tokens”, No. 1 on Monday 26 October 2026 (−0.009). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Detailed, sourced security report on a real supply-chain campaign hitting popular open source repos and CI/CD; technically specific and actionable for builders, though excerpt is partial and unrelated to the recent stories list.
AI judgeJudge 3gpt-5.6-luna
A timely, technically relevant supply-chain campaign affecting many public repositories, with concrete attack mechanics and credible researcher attribution. The short excerpt limits substantiation and depth, but the reported scale and CI/CD credential risk are highly consequential.

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.73total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.70
  • Reader interest0.87
  • Audience breadth0.72
  • Practical relevance0.80
  • Substantiated0.59
  • Technical depth0.65
  • New information0.88
  • Counts against: Promotional0.05
  • Counts against: Overclaim0.26

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.710.620.780.700.16+0.24+0.169
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.820.840.940.870.12+0.26+0.225
Audience breadthHow many people who build technology does it concern?0.730.720.720.720.01+0.13+0.094
Practical relevanceHow useful is it to someone who builds software or tech products?0.770.800.820.800.05+0.22+0.175
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.470.660.630.590.19+0.05+0.029
Technical depthHow technically substantive is it?0.680.680.580.650.10+0.05+0.032
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.810.900.920.880.11+0.05+0.044
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.080.040.030.050.05−0.19−0.010
OverclaimDo the headline or conclusions claim more than the body supports?0.400.200.180.260.22−0.11−0.029
Sum of contributions+0.731
Claim-check penalty0.000
Total, as published0.731

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.

Ranked #15 on Rubric, 30 Oct 2026
<a href="https://rubric.hrih.si/editions/2026-10-30/15/"><img src="https://rubric.hrih.si/badge/2026-10-30/15.svg" alt="Ranked #15 on Rubric, 30 Oct 2026" width="245" height="28"></a>

Claim check

Claim check: 7 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenNumber

    Radware researchers identified at least 83 attacks against 61 public GitHub repositories, including Google LangExtract, Trivy, Brave browser and MLflow.

    The article gives no link or citation for it.

    The article says

    “Researchers identified at least 83 attacks against 61 public GitHub repositories, including popular open source projects such as Google LangExtract, Trivy, Brave browser, and MLflow”

    The source says

    No source to compare with.

  2. No source givenNumber

    Of the malicious items, 77 were published during a 43-minute span on September 1, and the remaining six occurred within the next two minutes.

    The article gives no link or citation for it.

    The article says

    “Most (77) of the malicious items were published during a 43-minute time span on September 1, with the remaining six occurring within the next two minutes”

    The source says

    No source to compare with.

  3. No source givenNumber

    The attacker used 74 different GitHub accounts, many of which had legitimate development histories and were likely compromised.

    The article gives no link or citation for it.

    The article says

    “This attacker used 74 different GitHub accounts, many of which had legitimate development histories, meaning they were likely compromised”

    The source says

    No source to compare with.

  4. No source givenGeneralization

    Radware researchers suspect a single individual is behind the supply chain campaign.

    The article gives no link or citation for it.

    The article says

    “Nakibly and fellow Radware researcher Zvika Babo say they suspect a single individual is behind this supply chain campaign”

    The source says

    No source to compare with.

  5. No source givenCausal conclusion

    Radware assesses that the activity was coordinated because dozens of accounts posted the same type of payload on the same day, within a narrow time window, to the same infrastructure.

    The article gives no link or citation for it.

    The article says

    “Considering that dozens of accounts posted the same type of payload, on the same day, within a narrow time window, and to the same infrastructure, it is reasonable to assess…”

    The source says

    No source to compare with.

  6. No source givenQuote

    Gabi Nakibly said the attacker's likely final aim was a supply-chain attack: gaining repo credentials to change the code and push malicious changes to others.

    The article gives no link or citation for it.

    The article says

    “Our guess is that the final aim was a supply-chain attack in which the attacker gains credentials for the repo, and then he has the power to change the contents”

    The source says

    No source to compare with.

  7. No source givenFirst, only or fastest

    The attack chain is novel and extremely stealthy, with malicious commands hidden in HTML comments so the content is not visible in the rendered page.

    The article gives no link or citation for it.

    The article says

    “the attack chain is part of what makes this supply-chain campaign novel, and extremely stealthy”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 6 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 30 Oct 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.79

    Zlib 1.4