INTELLIGENCE LOG / REPORT 001
Default router passwords: the pattern isn't the problem
Knowing the pattern on a router's password sticker doesn't make it crackable. Routers get opened when the maker generates the password badly or reuses it for the admin login.
In 2023 someone asked whether a factory Wi-Fi password made of five lowercase letters, four digits and five more letters was weak because of its visible pattern. I worked through the numbers and the published attacks. The pattern still leaves about 1.4 quintillion possibilities. The routers that did fall had passwords built from public device data, generators with tiny internal state, or the same secret reused for the admin login.
- 1,411,670,956,533,760,000possible passwords in the reported 5-4-5 format
- 60.3 bitsof entropy in that format
- about 17,700 yearsto try every one on a single RTX 4090
- 10 of 40routers in one study reused the Wi-Fi password as the admin password
The short version
Back in 2023 someone on a forum asked whether a router's factory Wi-Fi password was weak because it always followed the same shape: five lowercase letters, four digits, then five more letters. Anyone who's seen two of those stickers can spot the pattern, so it feels like a shortcut.
It isn't much of one. Knowing where the digits sit takes the search down from roughly 64 quintillion guesses to 1.4 quintillion. On one high-end graphics card that's still about 17,700 years of guessing. The pattern leaks around 5.5 bits and leaves 60.3.
When I went through the published cases where default router passwords did fall, the shape of the password was never the reason. The maker built the password from something an attacker could read off the air, used a generator with a tiny internal state, or used the same secret for the admin login. Those are process failures, and you can't see any of them by looking at the sticker.
The arithmetic
Ten positions take one of 26 letters and four take one of 10 digits, so the format allows 26^10 × 10^4 = 1,411,670,956,533,760,000 passwords. That works out to 60.3 bits. Fourteen random lowercase letters with no fixed layout would give 26^14, about 6.45 × 10^19. So the layout cuts the space by a factor of 45.7x, which is about 5.5 bits.
For speed I used a community Hashcat benchmark: one stock RTX 4090 ran WPA-PBKDF2-PMKID+EAPOL at 2.5333 MH/s. [S1] Dividing the space by that rate gives about 17,700 years to try everything. A real attacker could rent far more hardware than one card, and the rate moves with the driver, the device and the capture, so treat the times below as a way to compare formats. They aren't a prediction for any particular password.
| Password format | Candidates | Entropy | Full search |
|---|---|---|---|
| 14 characters, letters and digits (62 symbols) | 1.24 × 10^25 | 83.4 bits | about 155 billion years |
| 14 lowercase letters | 6.45 × 10^19 | 65.8 bits | about 807,000 years |
| 16 hexadecimal characters | 1.84 × 10^19 | 64.0 bits | about 231,000 years |
| The reported 5-4-5 format | 1,411,670,956,533,760,000 | 60.3 bits | about 17,700 years |
| 10 hexadecimal characters | 1.10 × 10^12 | 40.0 bits | 5.0 days |
| 8 uppercase letters | 2.09 × 10^11 | 37.6 bits | 22.9 hours |
| 10 digits | 10^10 | 33.2 bits | 1.1 hours |
| 8 hexadecimal characters | 4.29 × 10^9 | 32.0 bits | 28.3 minutes |
| A published generator reconstruction (2^31 seeds) | 2.15 × 10^9 | 31.0 bits | 14.1 minutes |
| Belkin models that derived the key from the WAN MAC | n/a | n/a | no search needed |
Look at the last two rows. A password that looks like 14 random characters can come out of a generator with a 31-bit seed, or out of no secret at all. [S1] [S2] [S10]
How router passwords actually get broken
The password comes from public data
CVE-2012-4366 covers Belkin routers that built the default WPA2 passphrase from eight digits of the WAN MAC address. The router's own beacons gave away what you needed to work it out. [S2]
The generator is small
Researchers at Radboud University reverse-engineered the default-password generators in routers that were popular in the Netherlands. The generators held far less internal state than the printed passwords suggested, and the team got keys out of that. Password length didn't matter to them. [S3]
One secret does two jobs
A 2024 peer-reviewed study looked at 40 routers from 14 brands. 10 of them used the Wi-Fi password as the default admin password, so anyone on the network could also log in to the router. The authors reported 30 vulnerabilities to vendors across the wider study. [S4]
Mass attacks go after the admin side
Mirai got to roughly 600,000 infected devices at its peak with a list of 62 username and password pairs. Most were cameras, DVRs and home routers. It logged in to exposed management services and never went near anyone's Wi-Fi key, which tells you where to start fixing. [S5]
People have been cataloguing default keyspaces for years. There's a long Hashcat forum thread going back to 2016 and two smaller lists on GitHub that map SSID families to formats. [S10] [S13] [S14] They're a good starting point, but they're community notes. None of them is kept up with vendors, tied to firmware versions, or corrected in the open, which is what you'd want before putting one in a procurement file.
I also looked for a criminal campaign that got in by recovering a patterned factory Wi-Fi password. I didn't find one. Every large campaign in my source set used management services, admin credentials or unpatched bugs. That only tells you what I could find, and it doesn't prove no such attack has happened. Cracking a Wi-Fi key also needs someone within radio range, which keeps it local.
What the rules say now
Regulators have moved on to the generator too. The UK's PSTI regime has applied since April 29, 2024. Passwords have to be unique per product or set by the user, and a unique password can't be built from counters, public information or product identifiers unless encryption or keyed hashing protects the derivation. [S6] [S11]
ETSI TS 103 848 says the same for home gateways: preconfigured Wi-Fi and admin passwords must differ from one gateway to the next. [S7] NIST IR 8425A sets out a baseline for consumer routers. [S8] California has counted a unique preprogrammed password, or a forced change on first use, as a reasonable security feature for connected devices since January 1, 2020. [S9]
In the EU, the Cyber Resilience Act brings in reporting as well. Its Article 14 duties for actively exploited vulnerabilities and severe incidents apply from September 11, 2026, and the product requirements follow on December 11, 2027. [S12]
I'm citing these to show where the requirement now sits. Whether a given product or manufacturer meets any of them is a separate question, and this report doesn't answer it.
What I'd do
If you make or ship routers
- Draw each unit's password from the operating system's random source, the one you'd use for keys.
- Give Wi-Fi, local admin and remote support their own credentials.
- Keep serial numbers, MAC addresses and anything in the SSID out of the derivation.
- If you can't make the preset password strong enough for the people likely to attack it, have the owner change it at setup.
If you run or buy them
- Change the admin password when you set the router up.
- Use a separate Wi-Fi passphrase, and check that guests can't reach the admin page.
- Note the date firmware support ends. Get updates only from the vendor's own site or app.
- Ask the supplier how factory credentials are made, how they're reset, and whether they're shared between functions.
How I did this, and what I didn't do
This is desk research. I checked a research packet against the sources it cited and kept only claims I could trace to a source or reproduce by arithmetic. I dropped live counters, unconfirmed vendor attributions and incident totals nobody could source.
I calculated the candidate counts and bit strengths myself from the character sets. The times divide those spaces by the published benchmark, so they aren't measurements from my lab.
The April 2023 forum post that started this is no longer online, and I never confirmed which router brand it described, so I don't name one. The CVEs and papers describe the models and dates they tested. They don't show that any router on sale today is affected.
I didn't touch router hardware, network services, wireless traffic or anyone's credentials. On September 25, 2026 I rewrote the report for readability. Every figure and source is the same as in the August edition.
Sources
- S1RTX 4090 Hashcat v6.2.6 benchmarkCommunity measurement · Chick3nman, GitHub Gist · October 14, 2022
- S2CVE-2012-4366Primary · NIST National Vulnerability Database · November 19, 2012; record updated June 16, 2026
- S3Scrutinizing WPA2 Password Generating Algorithms in Wireless RoutersPeer reviewed · USENIX WOOT 2015 · August 2015
- S4Exposed by Default: A Security Analysis of Home Router Default SettingsPeer reviewed · ACM AsiaCCS 2024, author copy · July 2024
- S5Understanding the Mirai BotnetPeer reviewed · USENIX Security 2017 · August 2017
- S6The UK Product Security and Telecommunications Infrastructure regimePrimary · GOV.UK · Effective April 29, 2024
- S7Cyber Security for Home Gateways, ETSI TS 103 848 V1.1.1Primary · ETSI · March 2022
- S8Recommended Cybersecurity Requirements for Consumer-Grade Router Products, NIST IR 8425APrimary · NIST · September 2024
- S9California Civil Code section 1798.91.04Primary · California Legislative Information · Effective January 1, 2020
- S10Keyspace List for WPA on Default RoutersCommunity reference · Hashcat Forum · 2016 to 2024
- S11PSTI Security Regulations 2023, Schedule 1Primary · UK Legislation · Effective April 29, 2024
- S12Cyber Resilience Act reporting obligationsPrimary · European Commission · Reporting applies from September 11, 2026
- S13Wifi-WPA-Keyspace-ListCommunity reference · sheimo, GitHub · Last updated September 2017
- S14SSID keyspace tableCommunity reference · n0kovo, GitHub · March 2022
Found an error?
Write to mission@ssx360.com. I'll fix it on this page and log the change on the corrections page.
Permanent link: ssx360.com/research/001
