Skip to main content

Dates in Leaked Passwords

I have been playing with data from haveibeenpwned.com, especially I was exploring 8-digit passwords that look like dates.


I checked all dates between 19000101 and 20231231, where

- The date must be in the YYYYMMDD format

- Some invalid dates are also included, e.g. 19120231


Further, by default I only analyzed valid dates after 19240101.


By Year

1986 is the most popular year. It roughly forms a normal distribution. The distribution might review the distribution of the ages of the users (of the leaked services).


By Month & Day

It is clear that October, November and December are more popular than other months, but I think this is is because people may use 1912312 rather than 19120312.

We can also see a pattern for each month, especially 1st is more popular than other days.

Other than those, the passwords are roughly evenly distributed among all days.

The most popular dates are:
  • 0101, #=81516
  • 1010, #=79997
  • 1212, #=71724
  • 1111, #=62065
  • 1001, #=61109
Seems that they are just nice & easy patterns to type.

And the least popular dates are:
  • 0229, #=7075
  • 0731, #=20302
  • 0730, #=20846
  • 0531, #=21543
  • 0131, #=21646
0229 is obvious, but all other dates are all about the end of months, maybe this is not an coincidence.


By Day

31st is the least popular, which is obvious.

There's a sudden drop between 12th and 13th, which I don't really understand. This might contradict with my idea above, that people may type 9 instead of 09.



By Year & Month & Day

The most popular ones are:
  • 19870212, #=12359
  • 19821108, #=10812
  • 19941028, #=10097
  • 19810301, #=9528
  • 19960122, #=8906
The least popular ones (but appear in the database) are:
  • 19410417, #=1
  • 19410504, #=1
  • 19350824, #=1
  • 19290519, #=1
  • 19290525, #=1
Besides the popularily of the years, I cannot really draw any conclusions.


Invalid Dates

The most popular invalid dates are:
  • 19860229, #=362
  • 19820229, #=296
  • 19870229, #=228
  • 19890229, #=203
  • 19860230, #=192

Conclusions

By no means are the results scientific, it's just me having some fun.
If there's anything to remember, never use 19870212 as your password!

Comments

Popular posts from this blog

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...