gitwtfhub

wtf is lolcreds-data?

haxxm0nkey/lolcreds-data — explained in plain English

Analysis updated 2026-05-18

45Audience · ops devopsComplexity · 1/5LicenseSetup · easy

TL;DR

A public, community-maintained catalog of known default credentials and where to find them, built from vendor docs and advisories to help teams check and fix their own systems.

Mindmap

mindmap
  root((repo))
    What it does
      Catalogs default credentials
      Documents credential locations
      Links to public advisories
    Tech stack
      YAML data files
    Use cases
      Audit product default logins
      Harden deployments
      Reference during security reviews
    Audience
      Ops devops
      Researcher
    Data rules
      Public sources only
      No leaked secrets allowed

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Check whether a product you deploy, like Grafana, ships with a default admin password you need to change.

REASON 2

Look up where a service's credentials typically live, such as a config file or environment variable, during a security audit.

REASON 3

Contribute a new product entry or improve an existing one with better public references.

What's in the stack?

YAML

How it stacks up

haxxm0nkey/lolcreds-dataavlcode/avlcodeazureshores/bitcrusher
Stars454545
LanguagePython
Setup difficultyeasyeasyeasy
Complexity1/53/52/5
Audienceops devopsops devopsgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min
Free to reuse and share as long as you credit the original source.

Wtf does this do

This repository holds the data behind LOLCreds, a public catalog of known default credentials, credential locations, and exposure patterns for real software products, cloud services, appliances, and deployment tools. The idea is to give security teams and administrators one place to check whether a product they use ships with a default username and password, a generated token, or some other credential that people commonly forget to change. Each product gets its own YAML file under an entries folder. A single entry can describe several kinds of credentials, such as a static default password, a token generated automatically at install time, or a locally created admin account, along with where that credential typically lives, like a config file, an environment variable, a web login page, or a secret manager. Entries also note what the credential can access if left unchanged, and they link out to the vendor documentation, advisories, or release notes the information came from. The example included in the README covers Grafana, showing entries for its default admin login, a distribution-specific password used by a popular Kubernetes Helm chart, locally created user passwords, and service account tokens, each with details on where to find or change them. Contributions are welcome for adding missing products, fixing categories, or improving references, but the project is explicit that only publicly documented information belongs here: no private credentials, leaked secrets, live API keys, or breach data should ever be submitted. The data itself is released under the CC BY 4.0 license, which allows reuse as long as the original source is credited.

Yoink these prompts

Prompt 1
Check this repo's data for whether Grafana or a similar tool I'm deploying has any known default credentials.
Prompt 2
Show me how entries in this repo describe where default credentials are typically stored, like config files or environment variables.
Prompt 3
Help me write a new YAML entry for a product following the structure shown in this repo's example.
Prompt 4
Summarize what kinds of credential exposure patterns this catalog tracks across different products.

Frequently asked questions

wtf is lolcreds-data?

A public, community-maintained catalog of known default credentials and where to find them, built from vendor docs and advisories to help teams check and fix their own systems.

What license does lolcreds-data use?

Free to reuse and share as long as you credit the original source.

How hard is lolcreds-data to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is lolcreds-data for?

Mainly ops devops.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.