Edition of Friday 13 November 2026

Dosu Security Incident Post-Mortem

Comments on “Dosu Security Incident Post-Mortem”

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

On November 2, 2026, an attacker breached Dosu's production systems by starting from a free account and exploiting a flawed access policy on org invitations to take over Dosu's internal org. They then harvested integration credentials and reached the database, CI pipeline and cloud project.

Read the original at dosu.dev. 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. 23 of 137 with a score of 0.71. The panel rated it highest on reader interest (0.89) and new information (0.85), lowest on audience breadth (0.61). Overclaim counted against it (0.55). The judges disagreed most on overclaim (spread 0.48), so the story is marked contested. Placed No. 23, No. 9 by score alone: the eleventh Security story of the day (−0.080), and close to “Phala Confidential AI Compromised”, No. 5 on Thursday 12 November 2026 (−0.018). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Detailed, primary-source security incident post-mortem with timeline, IOCs and concrete flaws; highly relevant to builders, though self-serving framing and AI-hype claims temper substantiation and calibration.
AI judgeJudge 3gpt-5.6-luna
A detailed primary incident account documents chained authorization, integration, CI, database and cloud failures with actionable indicators. It is highly relevant to security and infrastructure builders, but broad claims about AI-reviewed code and attacker capability exceed the evidence.

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.71total under rubric v2.3Contestedjudges differ by 0.48 on overclaim

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.68
  • Reader interest0.89
  • Audience breadth0.61
  • Practical relevance0.84
  • Substantiated0.85
  • Technical depth0.84
  • New information0.85
  • Counts against: Promotional0.06
  • Counts against: Overclaim0.55

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.720.600.720.680.12+0.24+0.163
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.860.920.900.890.06+0.26+0.232
Audience breadthHow many people who build technology does it concern?0.500.750.580.610.25+0.13+0.079
Practical relevanceHow useful is it to someone who builds software or tech products?0.880.850.780.840.10+0.22+0.184
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.870.850.820.850.05+0.05+0.042
Technical depthHow technically substantive is it?0.880.850.780.840.10+0.05+0.042
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.800.900.850.850.10+0.05+0.043
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.060.100.030.060.07−0.19−0.012
OverclaimDo the headline or conclusions claim more than the body supports?0.580.300.780.550.48 , above the contested threshold−0.11−0.061
Sum of contributions+0.713
Claim-check penalty0.000
Total, as published0.713

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 #23 on Rubric, 13 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-13/23/"><img src="https://rubric.hrih.si/badge/2026-11-13/23.svg" alt="Ranked #23 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.

  1. No source givenDate

    The main intrusion into Dosu's production systems ran from 04:11 to 07:59 UTC on November 2, with earlier scanning starting October 31 and last probes on November 4.

    The article gives no link or citation for it.

    The article says

    “The main intrusion ran from 04:11 to 07:59 UTC on November 2. Earlier scanning started on October 31, and the last probes of our public endpoints came on November 4”

    The source says

    No source to compare with.

  2. No source givenDate

    Supabase, Dosu's database provider, detected the malicious activity and alerted Dosu at 08:17 UTC on November 2.

    The article gives no link or citation for it.

    The article says

    “detected the malicious activity and alerted us at 08:17 UTC on November 2”

    The source says

    No source to compare with.

  3. No source givenCausal conclusion

    The attacker gained access via an incorrect RLS policy check on org invitations that let them create an invitation to any org and make themselves owner of Dosu's internal org.

    The article gives no link or citation for it.

    The article says

    “An incorrect RLS policy check let the attacker create an invitation to any org”

    The source says

    No source to compare with.

  4. No source givenCausal conclusion

    Integration credentials and API keys were not exposed because credentials are encrypted and API keys are hashed, even though the attacker reached the tables holding them.

    The article gives no link or citation for it.

    The article says

    “The attacker reached the tables that hold them, but credentials are encrypted and API keys are hashed”

    The source says

    No source to compare with.

  5. No source givenNumber

    The attacker used the ARTEX penetration testing framework, which sent more than 80,000 requests in 90 minutes and found the flaw within hours.

    The article gives no link or citation for it.

    The article says

    “It sent more than 80,000 requests in 90 minutes and found the flaw within hours”

    The source says

    No source to compare with.

  6. No source givenNumber

    The flaw was not detected in multiple penetration tests, including one the week before the incident.

    The article gives no link or citation for it.

    The article says

    “The vulnerability wasn't detected in multiple penetration tests at various points in time, including one the week prior to the incident”

    The source says

    No source to compare with.

  7. No source givenNumber

    Dosu's AI agent refused every request for credentials when the attacker tried prompt injection against it.

    The article gives no link or citation for it.

    The article says

    “The agent refused every request for credentials”

    The source says

    No source to compare with.

  8. No source givenGeneralization

    Dosu concludes that all code not reviewed by a frontier model is at risk and that writing and reviewing code without AI has become irresponsible.

    The article gives no link or citation for it.

    The article says

    “All code that a frontier model hasn't reviewed is at risk. It has become irresponsible to write and review code without AI”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:42 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 “Dosu Security Incident Post-Mortem”

More on Rubric

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

  1. Score 0.74

    Backdooring Codex