Click on a team name below for more details about its composition, resources, and methodology for
tackling the contest.
The above counts for CPUs and GPUs are very high-level and discard the differences between higher-end and lower-end cores. The core-count for teams using clusters or EC2 are rough equivalents based on the number of compute-hours they report having used. See each teams' specific writeup for more details.
| Name | Score | Active Members | CPU Cores (est) | GPU Cores (est) | Primary Tools | Eligible |
|---|---|---|---|---|---|---|
| hashcat | 38576 | 11 | 29 | 21 | hashcat, oclhashcat (many others) | Yes |
| Insidepro Team | 36017 | 16 | 40 | 20 | EGB, PasswordsPro, Saminside, Hashcat, OclHashcat, JTR, Ophcrack | No |
| CrackHeads | 31175 | 2 | 120 (EC2 and a cluster) | 1 | John the Ripper, probabilistic cracker, oclhashcat | Yes |
| john-users | 29196 | 10+ | ~30 | 1 | John the Ripper, custom code to distribute & assimilate results (some others) | Yes |
| iPhelix | 22623 | 1 | 8 | 3 | oclHashcat, hashcat, ighashgpu, John the Ripper, probabilistic cracker | Yes |
| Nightingale | 22443 | ? | ? | ? | ? | Yes |
| bartavelle | 20563 | ~4 | 123 (peak: 204) | 0 | John the Ripper, custom distributed cracking code | No |
| PHX2600 | 12488 | ? | ? | ? | ? | Yes |
| smelly_weigand | 7862 | ? | ? | ? | ? | No |
| 4yvak | 7569 | ? | ? | ? | ? | Yes |
| Bill E Ghote | 6530 | 1 | 2 | 0 | John the Ripper, OphCrack, RainbowCrack | Yes |
| Benny Lava | 5891 | ? | ? | ? | ? | Yes |
| 16Crack | 3753 | 1 | 6 | 0 | 16Crack | Yes |
| RPISEC | 3550 | ? | ? | ? | ? | Yes |
| Rippin and Tearin | 2629 | 2 | 4 | 0 | John the Ripper, ophcrack | Yes |
| 0x90 | 696 | ? | ? | ? | ? | Yes |
| P1neapp1e | 213 | ? | ? | ? | ? | Yes |
| Analog Conspiracy | 5 | ? | ? | ? | ? | No |
The above counts for CPUs and GPUs are very high-level and discard the differences between higher-end and lower-end cores. The core-count for teams using clusters or EC2 are rough equivalents based on the number of compute-hours they report having used. See each teams' specific writeup for more details.