Terminal Hacking in New Vegas: Actually How It Works

Most players treat the hacking minigame like a puzzle game when it's really just a resource management exercise. The password system in Fallout New Vegas uses a 36-character charset — a through z and 0 through 9 — and every terminal has between one and five passwords. Each password unlocks the next tier of access. That's it. There's no pattern to the passwords themselves. They're randomly generated at terminal creation, so you'll never memorize a "common" password across saves. The only way to find passwords without guessing is through the skill check system. At Expert difficulty — the hardest tier — you get three attempts per password. Each attempt gives you feedback: either too high or too low. If you guess wrong, the password range collapses to either everything below your guess or everything above it. That's how you narrow it down. Here's the math nobody explains well. An Expert terminal has a 1 in 62,270,208,656 chance of guessing right on the first try if the password is six characters. Even with five characters it's roughly 1 in 21 million. This isn't a game you win by luck at Expert. You're supposed to use skill checks and the high/low feedback to solve it deterministically.

The skill check number matters a lot. Your Science skill minus the terminal's difficulty rating determines whether you get a usable hint. At 100 Science against an Expert terminal, you'll get meaningful feedback roughly three out of four times on the first attempt. At 75 Science, you're rolling around 50 percent chance per check. Below that, you're mostly guessing with better odds than raw chance alone.

Working the Numbers

The binary search approach works because the high/low system is deterministic. Start by guessing the midpoint of the current possible range. If the feedback says too high, your new upper bound becomes your previous guess minus one. If it says too low, your lower bound becomes your previous guess plus one. Repeat until you hit the exact password or run out of attempts. For a six-character password with all 36 characters possible, the range starts at 36^6, which is about 2.17 billion combinations. After one well-placed skill check, you cut that roughly in half. After two more checks, you're down to a few million. That's still too many to brute-force safely, which is why the skill checks exist — they give you the shortcuts that make this solvable under time pressure. I spent about forty-five minutes once trying to crack a Brotherhood of Steel terminal in the Mojave Outpost because I didn't have enough Science to reliably trigger the hints. Eventually I just reloaded and spent five minutes doing it properly. That was a good lesson in knowing when a terminal is actually worth your time versus when you should just walk away.

What Beginners Miss

The biggest mistake I see is people treating all password tiers equally. An Expert terminal might have three passwords, but the first one is usually short — three to four characters — and trivial to find. The second gets harder. The third can be a nightmare. Don't waste your best builds trying to crack a terminal when you could just pick the lock with a high Lockpick skill instead. Another thing: the perk system interacts with hacking in ways most players don't realize. Quick Brown Fox gives you a flat bonus to hacking but doesn't improve your skill check reliability. If you need consistent results on Expert terminals, point investing into Science gives you more predictable returns than stacking perks, since the skill check probability scales linearly with your base score. There's also a common misconception about the very hard terminals. They don't just have longer passwords — they have fewer skill check attempts before the terminal locks you out permanently. On very hard, you might only get two attempts per password instead of three. This makes the binary search approach riskier because a single failed skill check wastes a turn that you can't recover. These terminals are genuinely punishing, and there's no way around it other than having a high enough Science skill to make the checks nearly automatic.

When Hacking Isn't the Answer

Lockpicking is often faster. A good Lockpick build lets you bypass entire terminals in seconds, no guessing required. If your character isn't built for Science, don't force it. The game gives you alternatives for a reason. I've seen players blow hours on NCR terminal puzzles when a twenty-dollar lockpick would have solved it instantly. The companion system also helps. Boone can help you hack if you have him in your party and meet certain conditions. It's not a reliable crutch for heavy hacking builds, but it's there when you need it. The main bottleneck with hacking is character build dependency. If you want to run a pure Science hacker, you're giving up damage output, survival stats, and a lot of dialogue options. The investment pays off for terminals that matter — like the ones controlling missile silos or giving you access to unique weapons — but most random terminals you encounter along the way are better left alone. Prioritize the ones tied to quests or rewards that actually scale with your playstyle.

Practical Walkthrough

Here's how a real attempt goes. You approach an Expert terminal. Your Science skill is 85, so you expect decent check reliability. The terminal asks for a password. You click "Hacker" and enter a guess. Let's say you guess abcdef. The terminal says "too low." Now you know the password is above abcdef. You enter your next guess at the midpoint of the remaining range — something like mnopqr. The terminal says "too high." Range collapses again. Third attempt, you narrow it to a small window and find the password. That's the whole process repeated for each password tier. The frustration comes when you run out of attempts mid-range, which happens more often than people expect when your Science skill sits in the 70s. Above 90, you'll barely notice failures. Below 60, you should probably just leave the terminal alone and find another route. One edge case that caught me off guard: some terminals reset the password range if you wait too long between attempts. If you step away from the terminal or engage in conversation and then come back, the range may have shifted. This is especially relevant on very hard terminals where every attempt counts. Save before hacking, reload if you lose your place, and don't assume the terminal state persists through long breaks. It's a minor detail that cost me several hours when I first encountered it, and I still forget about it occasionally.