Concern 182 · Working draft · editorial review in progress

Password and credential-stuffing acceleration

AI-assisted password attacks use learned patterns to improve guesses, while credential stuffing reuses passwords already stolen from another service.

Understanding the concern

These are related but distinct threats. Guessing tries likely candidates; credential stuffing relies on people using the same credentials in multiple places. AI research can improve candidate generation, but that does not remove the limits imposed by login controls or make every password easy to recover.

Offline guessing against stolen password data also differs from trying to sign in to a live account. Defenses such as unique credentials, appropriate password storage, and limits on failed attempts address different stages. Claims about cracking speed are meaningless without those conditions.

An example

A thief tries common key shapes, then separately tests a key stolen from another building where the owner may have reused the lock.

Illustrative unless identified as a documented case.

Words in plain English

AI
Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.

Evidence and its limits

The study evaluates guessing on password datasets; NIST distinguishes authentication controls and reuse risks. Neither supports a universal time-to-crack claim.

Explore these sources in the library →
Broader frameworks and background

These resources provide context. They do not establish every claim in this concern.

A question to discuss

Are we protecting against both predictable passwords and reuse of credentials stolen elsewhere?

Keep track of different views, what needs checking, and any next step in your own discussion notes.

Open discussion notes →
Principles for the conversation

Before you finish · reflect together

Virtues and principles to consider

Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.

Stewardship

Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.

Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.

Ask together: What are we responsible for caring for over time?

Prudence

Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.

Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.

Ask together: What is a careful next step, and when should we stop or change course?

Accountability

Accountability means being answerable for decisions and taking responsibility for repair. It requires more than saying that the software made the choice.

Name the person or team responsible, keep useful records, and give them authority to correct problems. Make the route to a complaint clear to the people affected.

Ask together: Who will answer for the outcome and help put things right?

Editorial ratings

These are editorial judgments from the register, not measured probabilities or predictions about your situation.

Severity
Catastrophic · 5/5
Likelihood
Documented at scale · 5/5
Time horizon
Now
Register risk score
25
About the register and scoring →
More ways to explore

Search for more writing

For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.

Explore a proposed use of AI →