Exploiting Replay Protected Monotonic Counters to Brute-Force Windows Hello Pins
Comments on “Exploiting Replay Protected Monotonic Counters to Brute-Force Windows Hello Pins”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
TU Berlin researchers (ACM CCS '26) show that firmware TPM lockout state can be rolled back on x86 laptops with a low-cost SPI interposer. Winbond flash leaks its RPMC HMAC key under voltage glitching, and AMD's NV controller does not verify counter increments. The authors report recovering a 4-digit Windows Hello PIN in 40 hours instead of 69 days, and a 6-digit BitLocker PIN in 20 days instead of 19 years.
Why it ranked
No. 5 of 122 with a score of 0.75. The panel rated it highest on technical depth (0.96) and substantiated (0.94), lowest on practical relevance (0.64). Placed No. 5, where the score alone would also have put it: the fourth Security story of the day (−0.020). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Peer-reviewed-style security research with primary evidence and reproduction details on TPM/PIN brute-force via flash rollback; strong security and hardware relevance, moderately broad audience, low promotion.
- AI judgeJudge 3gpt-5.6-luna
- A primary security paper presents reproducible hardware attacks, implementation flaws, artifacts, and end-to-end Windows Hello/BitLocker demonstrations. It is highly technical and consequential, though exploitation requires prolonged physical access and specialized equipment.
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.75total under rubric v2.3
- Significance0.77
- Reader interest0.85
- Audience breadth0.69
- Practical relevance0.64
- Substantiated0.94
- Technical depth0.96
- New information0.93
- Counts against: Promotional0.03
- Counts against: Overclaim0.21
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.74 | 0.72 | 0.84 | 0.77 | 0.12 | +0.24 | +0.184 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.71 | 0.88 | 0.96 | 0.85 | 0.25 | +0.26 | +0.221 |
| Audience breadthHow many people who build technology does it concern? | 0.79 | 0.60 | 0.68 | 0.69 | 0.19 | +0.13 | +0.090 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.58 | 0.55 | 0.78 | 0.64 | 0.23 | +0.22 | +0.140 |
| 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.97 | 0.90 | 0.95 | 0.94 | 0.07 | +0.05 | +0.047 |
| Technical depthHow technically substantive is it? | 0.99 | 0.92 | 0.98 | 0.96 | 0.07 | +0.05 | +0.048 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.93 | 0.90 | 0.97 | 0.93 | 0.07 | +0.05 | +0.047 |
| 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.06 | 0.03 | 0.01 | 0.03 | 0.05 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.34 | 0.20 | 0.08 | 0.21 | 0.26 | −0.11 | −0.023 |
| Sum of contributions | +0.748 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.748 | ||||||
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-17/5/"><img src="https://rubric.hrih.si/badge/2026-11-17/5.svg" alt="Ranked #5 on Rubric, 17 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 7 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
The authors' setup finds a 4-digit Windows Hello PIN in 40 hours instead of 69 days using NV state rollback on locked, encrypted hardware.
The article gives no link or citation for it.
The article says “our setup finds a 4-digit Windows Hello PIN in 40 hours instead of 69 days”
The source says No source to compare with.
No source givenNumber
The rollback primitive reduces the worst-case time to brute-force a default-length 6-digit BitLocker TPM+PIN from 19 years to 20 days.
The article gives no link or citation for it.
The article says “reducing the worst-case time for a default-length 6-digit PIN from 19 years to 20 days”
The source says No source to compare with.
No source givenCausal conclusion
Winbond SPI flash leaks its HMAC key under voltage glitching, enabling arbitrary counter forgery.
The article gives no link or citation for it.
The article says “Winbond SPI flash – the leading NOR flash vendor with over 25% market share – leaks its HMAC key under voltage glitching, enabling arbitrary counter forgery”
The source says No source to compare with.
No source givenCausal conclusion
AMD's NV controller does not verify RPMC increments, so an interposer can suppress them unnoticed.
The article gives no link or citation for it.
The article says “AMD’s NV controller does not verify RPMC increments, so an interposer can suppress them unnoticed”
The source says No source to compare with.
No source givenNumber
Windows Hello is the primary authentication mechanism on over one billion Windows 11 devices.
The article gives no link or citation for it.
The article says “Windows Hello is the primary authentication mechanism on over one billion Windows 11 devices”
The source says No source to compare with.
No source givenGeneralization
On two AMD desktops (Zen 2 and Zen 5) without RPMC flash, reflashing an old image resets the fTPM's lockout counters.
The article gives no link or citation for it.
The article says “on two AMD desktops, reflashing an old image resets the fTPM’s lockout counters”
The source says No source to compare with.
Couldn’t checkNumber
The Windows Hello attack ran at about 4.14 tries per minute, a net 57 minutes for 236 PINs, a ~41x speedup over Microsoft's 10-minute timeout.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “net time to find the correct PIN was 57 minutes across 236 tried PINs, i.e. ~41 PINs per 10 minutes (4.14 tries/minute”
The source says No passage could be compared.
Source cited by the article: youtu.be/Yq2Wa-nj68g
No source givenQuote
Microsoft closed the report as moderate severity with no CVE or bounty, committing only to raise the recommended minimum Hello PIN length to 6 digits.
The article gives no link or citation for it.
The article says “Microsoft closed this case as “moderate severity”, defense-in-depth, below the bar for immediate servicing – issuing no CVE or bounty”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 7 pts, not on front page
Recorded for context only, checked 17 Nov 2026, 05:47 UTC. It played no part in the ranking.