Join our Newsletter — 33% off our NHI Course

Uncovering LLM-Generated Password Patterns: A Deep Dive

 

(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 21735
Topic starter  

TL;DR: GitGuardian found that LLM-generated passwords follow detectable patterns, and its scan of 34 million GitHub passwords surfaced 28,000 likely LLM-generated examples, with Anthropic, Qwen, and Google accounting for 63% of cases. Predictable secret generation turns AI-assisted password creation into an NHI governance problem, because secrets that are easy to classify are also easier to exploit.

Editorial analysis by NHI Mgmt Group, based on content published by GitGuardian: “The Bot Left a Fingerprint: Detecting and Attributing LLM-Generated Passwords”.

By the numbers:

Key questions

Q: What breaks when teams let LLMs generate passwords?

A: Password generation breaks when teams use an LLM as the source of a secret, because the output is shaped by probability rather than entropy.

Q: Why are AI-generated passwords risky even when they look complex?

A: They are risky because complexity is not the same as entropy.

Q: How should security teams handle secrets in AI-generated code?

A: Security teams should treat AI-generated code as another source of credential exposure, not as a special case.

Practitioner guidance

  • Disable LLMs as password generators Require vaults or dedicated password managers to generate all production secrets, and block AI-generated passwords from being accepted as source-of-truth credentials.
  • Scan agent hooks for secret creation Inspect AI agent hooks, prompts, and commit outputs for passwords, API keys, and other secrets before they reach repositories or deployment files.
  • Treat predictable passwords as compromised-by-design Flag any password created by an LLM for immediate replacement, because recognisable structure makes it easier to classify and attack later.

Bottom line: LLM-generated passwords are structurally different from entropy-based secrets because their patterns can be detected, classified, and attacked.

What's in the full report

GitGuardian's full article covers the statistical fingerprinting and wild-password classification detail this post intentionally leaves for the source:

  • The 8,000-password test dataset built from 40 LLM models and 11 providers
  • Model-by-model uniqueness and substring analysis across Anthropic, Qwen, Llama, Gemma, and GPT families
  • Markov-chain classification thresholds and scoring logic used to identify likely LLM-generated passwords
  • Examples of how AI-generated passwords appear in Terraform files, .env files, and source code

👉 Read GitGuardian's analysis of LLM-generated passwords and secret predictability →

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: 5 months ago
Posts: 21568
 

Predictable secret generation is a governance failure, not a convenience feature. A password produced by an LLM is not simply user-chosen with AI assistance, it is a machine-generated artifact shaped by probability. That makes it fundamentally different from entropy-based secret issuance and far more exposed to pattern-based identification. Practitioners should treat AI-generated secrets as a controlled identity lifecycle event, not as a productivity shortcut.

A few things that frame the scale:

  • AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
  • According to Forrester Research, a single password reset can cost around $70.

A question worth separating out:

Q: Should organisations allow AI agents to use production credentials?

A: Only if those credentials are task-scoped, closely monitored, and revocable without affecting unrelated systems. In most cases, production credentials create unnecessary blast radius. A safer pattern is short-lived access, explicit approvals for non-read actions, and strong separation between agent identity and human privilege.

👉 Read our full editorial: LLM-generated passwords are predictable and now detectable in the wild



   
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.