Join our Newsletter — 33% off our NHI Course

What would it take for proof of work to curb credential stuffing?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20210
Topic starter  

TL;DR: Bot abuse gets more expensive when invisible proof of work shifts the burden onto attacker compute, Arkose Labs says. Login flows then need to judge whether the challenge materially raises abuse cost before account compromise begins.

Editorial analysis by NHI Mgmt Group, based on content published by Arkose Labs: “Beyond CAPTCHA: Proof of Work Is Invisible Economic Barrier Against Sophisticated Threats”.

By the numbers:

  • Arkose Labs says its proof of work approach delivers an 85% false positive reduction versus CAPTCHA-only approaches.
  • Arkose Labs says the approach achieves a 95% completion rate for users.

Key questions

Q: Why does proof of work change the economics of credential stuffing?

A: Because each attempt consumes attacker compute, the marginal cost of mass login abuse rises with volume.

Q: What signs show that bot challenges are failing or too weak?

A: If successful automated logins remain high, challenge completion is near-perfect for suspicious traffic, or the same device patterns keep reappearing, the control is not imposing enough cost.

Q: How should security teams slow automated login abuse without adding CAPTCHA friction?

A: Use invisible computational challenges on the highest-risk entry points, then verify outcomes server-side and adapt difficulty to device capability.

Practitioner guidance

  • Target high-risk identity flows first Apply invisible proof of work to login, registration, and high-value transaction paths where automation pressure is highest and where added user friction would be most damaging.
  • Tune challenge difficulty by device capability Use device classification and adaptive difficulty levels so low-power devices are not overburdened while high-capacity automation receives stronger computational cost.
  • Treat solve-time signals as detection inputs Feed challenge completion time, latency variance, and execution context into account risk scoring so the control contributes to bot classification and campaign detection.

Bottom line: Proof of work shifts bot defence away from visible friction and toward request-time computational cost, which is more compatible with high-volume identity flows.

Glossary terms: Proof Of Work, Credential Stuffing, Invisible Challenge, Attack economics

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 5 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20698
 

Proof of work introduces identity friction at the machine layer, not the human layer. That distinction matters because the control is aimed at automated abuse paths before they become account events. In identity terms, the defender is pricing the request, not interrogating the person, which makes the control useful where user experience and abuse resistance have to coexist. Practitioners should recognise this as request-time governance for machine-paced abuse.

A question worth separating out:

Q: When is invisible bot verification better than interactive CAPTCHA?

A: Invisible verification is better when user experience, accessibility, and conversion are material concerns and when the abuse problem is high-volume rather than human judgement based. Interactive CAPTCHA is still useful in limited exception cases, but it is a poor default when sophisticated solvers and friction costs both matter.

👉 Read our full editorial: Proof of work raises the cost of bot attacks beyond CAPTCHA



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.