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

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 ...

GameConqueror 0.09 -- Linux Game Hacking Tool

If you are a game hacker If you've been looking for a `CheatEngine for Linux` Then you can't miss this. ============================================== GameConqueror is a game hacking tool for linux, it's written in PyGTK and uses scanmem as its backend. It's supposed to be with most useful features of CheatEngine for Linux. Currently, I've implemented almost everything about scanning, involving variant data types and scan types: Data Types: int{8/16/32/64}, float{32/64}, unknown type(int or float) and unknown width(will try each of them), byte array and string Scan Types: equal, greater, less, changed, unchanged, increased(by), decreased(by) This should be enough for most cases, so I decided to release it at the current status. ============================================= Here's how you can get it PPA (for Ubuntu users) https://launchpad.net/~coolwanglu/+archive/scanmem (I've not test it in 32bit environments or Jaunty, do please inform me if it doe...

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...