lolcreds

Public credential defaults and exposure patterns for authorized security testing.

Neo4j

Neo4jdatabase4 credentials1 default credential

Credentials4 documented
01

Initial neo4j User Password

neo4j / default-neo4j

Neo4j creates a default neo4j user for initial database access. Historical/default startup credentials use neo4j/neo4j and require changing the password before normal use.

static defaultuser definedsecretusername/password

Default credentials

neo4j:neo4j

Location

public interface
Bolt, Browser, Cypher Shell, HTTP API, and Neo4j Ops Manager integrations
database

system database auth records and password hashes

config file

initial password files, deployment manifests, and dbms security settings

logs

debug.log, security.log, query logs, and authentication errors

Notes

neo4j/neo4j is the initial password pattern; modern deployments force a password change or accept a deployment-provided initial password.

02

Database User Password

neo4j / database-user-password

Neo4j native users and roles authenticate for database, cluster, and API access through native auth or external providers.

user definedgenerated on installsecretusername/password

Location

database

system database user, role, and auth metadata

public interface
Bolt, Browser, HTTP API, Cypher Shell, and drivers
secret store

password vaults, Kubernetes Secrets, and deployment secret stores

source code

application configs, tests, and driver connection settings

logs

security logs, driver debug output, and query logs

03

Driver URI / Application Credential

neo4j / driver-connection-secret

Applications store Neo4j URIs, usernames, passwords, bearer tokens, and client certificate keys for driver connections.

user definedsecretusername/password

Location

config file

application.yml, .env files, driver configs, Helm values, and Docker Compose files

environment
NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD, NEO4J_AUTH
secret store

CI/CD variables, cloud secret managers, and Kubernetes Secrets

source code

application repositories and integration tests

logs

driver connection errors and debug traces

04

TLS, Cluster, and Backup Secrets

neo4j / ssl-cluster-secrets

Neo4j deployments use TLS private keys, cluster discovery secrets, backup credentials, and sometimes Kerberos/LDAP bind credentials for enterprise security.

generated on installuser definedsecretsecret value

Looks like

pattern
pattern

private key material for Neo4j Bolt/HTTPS or client certificate auth

-----BEGIN (RSA |EC |ENCRYPTED |)PRIVATE KEY-----

Location

config file
neo4j.conf, certificates/

TLS, auth provider, clustering, and backup settings

secret store

certificate stores, Kubernetes Secrets, and vaults

artifact

database backups, dumps, and diagnostics bundles

logs

cluster, TLS, backup, and auth provider logs

Scope

Authorized use

LOLCreds helps map the credential surface of real products: known defaults, generated values, credential locations, and exposure patterns.