VPN marketing leans hard on fear: hackers lurking in coffee-shop Wi-Fi, "military-grade encryption," your passwords floating naked through the air without their product. The pitch works - VPNs are a multi-billion-dollar consumer category - But it quietly misrepresents where password theft actually happens. A VPN encrypts one specific segment of one specific path: the hop between your device and the VPN company's server. That's genuinely useful for privacy and for a handful of network attacks. It does nothing about the ways the overwhelming majority of passwords are stolen - Phishing pages, breached databases, and malware already sitting on the device. This article draws the boundary honestly: what a VPN covers, what it can't, and the piece almost everyone skips - Securing the VPN account itself.

What a VPN actually encrypts

A VPN creates an encrypted tunnel from your device to a server run by the provider. Everything you send is wrapped in strong encryption - Modern services use AES-256 or ChaCha20, the same cipher families that protect banking traffic - Carried to the VPN server, decrypted there, and sent onward to its real destination. Anyone positioned between you and that server (the café's router, a hostile hotspot, your ISP, a hotel network operator) sees only ciphertext addressed to the VPN.

Notice both boundaries. Before the tunnel: anything already on your device - Malware, a keylogger, your clipboard - Sits inside the encryption boundary and sees everything in plaintext. After the tunnel: traffic leaves the VPN server looking like ordinary traffic, and the destination website receives exactly what it would have received anyway. The VPN moved your trust; it didn't extend encryption end-to-end. End-to-end protection between you and a website is a different mechanism - TLS - And you already have it.

HTTPS was already encrypting your password

Here's the part the ads omit: when you type a password into any legitimate login page in 2026, it travels inside an HTTPS connection encrypted from your browser to that site's server. Well over 95% of page loads in major browsers are HTTPS, per Google's transparency reporting, and browsers actively warn before you submit a password over plain HTTP. The padlock's guarantees - Encryption plus verification that you're talking to the domain in the address bar - Are covered in HTTPS and TLS explained.

So on a hostile network without a VPN, an eavesdropper watching your login sees ciphertext they can't read; TLS was designed precisely for untrusted networks. What they can see is metadata - Which sites you visit (via DNS and connection targets) and when. A VPN hides that metadata from the local network and your ISP by pushing it into the tunnel. That's a real privacy gain. It's just not password protection, because your password was never traveling in the clear to begin with.

The honest residual risks on hostile networks are subtler: DNS manipulation steering you toward a fake portal, TLS-stripping tricks against sites misconfigured enough to allow a downgrade, and lookalike captive portals harvesting logins directly. A VPN does blunt the first two, which is why it still earns a place in the public Wi-Fi risk rundown - As one mitigation among several, not a force field.

How passwords actually get stolen - And whether a VPN helps

Set the marketing aside and look at the mechanisms behind real-world account takeovers - The breach post-mortems in Verizon's annual DBIR tell a consistent story: stolen credentials, phishing, and malware dominate, and none of them involve eavesdropping on your Wi-Fi.

How passwords get stolen How it works Does a VPN help?
Phishing pages You type the password into a convincing fake site No - The tunnel delivers you to the fake site just as efficiently
Database breaches The website itself is hacked; stored credentials leak No - Theft happens on the server, long after your traffic arrived
Credential stuffing Passwords leaked from one site are replayed on others No - Reuse is the vulnerability, not the network
Infostealer malware / keyloggers Software on your device captures passwords at the source No - Malware sits inside the encryption boundary
Shoulder surfing Someone watches you type No
Local network eavesdropping Sniffing traffic on shared Wi-Fi Mostly redundant with HTTPS; VPN adds cover for metadata and misconfigured sites
Evil-twin hotspots / DNS tricks Rogue access point redirects or intercepts Partially - The tunnel bypasses the rogue network's DNS and routing

The pattern is stark: a VPN meaningfully addresses only the bottom rows - The rarest attacks on the list - Because everything else happens off the wire. The credentials-first attacks that fill breach reports are covered in credential stuffing explained, and the malware column - Infostealers, arguably today's biggest single password threat - Steals credentials at the source, where no network encryption can reach. Against those, the defenses are unglamorous: unique random passwords from a password generator, a manager to hold them, two-factor authentication everywhere it's offered, and the link-checking reflexes from the phishing protection guide.

A VPN is a privacy tool that occasionally helps security. Password security lives in what you create, where you store it, and what you type it into - None of which a tunnel can see.

The password nobody thinks about: your VPN login

Here's the twist worth the price of admission: adding a VPN adds another password to your life - And it's an unusually consequential one.

Think about what a VPN account controls. Someone who logs in to it can see connection metadata, but with some providers they can also change your settings, add devices, or - In the worst configurations - Route your traffic through servers they choose. A hijacked VPN account inverts the product: the tool you bought to hide traffic from strangers now delivers your traffic to one. VPN providers get credential-stuffed like every subscription service, and leaked "combo lists" circulate with VPN logins specifically flagged because they're valuable.

Corporate VPNs raise the stakes further. Remote-access VPN credentials are a top target for ransomware crews - A single phished or reused VPN password has been the entry point in several headline incidents, including the Colonial Pipeline shutdown, where the compromised VPN account famously lacked MFA. If you administer one: unique per-user credentials, mandatory MFA, and prompt revocation when people leave.

For your personal VPN account, the checklist is short: a unique random password stored in your manager; two-factor authentication if the provider offers it (most major ones now support authenticator apps - You can see how those rotating codes work in our TOTP generator); and treat the account email as part of the perimeter, since it can reset everything.

Choosing and using a VPN sensibly

If you use a VPN, a few practices keep it a net positive. Prefer providers with independently audited no-log policies and modern protocols (WireGuard or OpenVPN) - You are structurally trusting them with your metadata, so their credibility is the product. Enable the kill switch so a dropped tunnel doesn't silently expose traffic you meant to cover. And resist the halo effect: the persistent finding in security-behavior research is that people take more risks when they feel protected. A VPN badge in the menu bar doesn't vet the link you're about to click or the login page you're about to fill.

One adjacent habit while you're thinking about networks: the Wi-Fi password on your own router protects everyone in your home the way a VPN never can, by keeping strangers off the network entirely - Generate a strong one with the WiFi password generator if yours is still the printed default.

The verdict

Do VPNs protect your passwords? Barely - And that's fine, because it isn't their job. A VPN hides your traffic patterns from local networks and ISPs, defeats rogue-hotspot tricks, and adds a redundant layer under HTTPS. Every mechanism that actually steals passwords at scale - Phishing, breaches, reuse, malware - Operates entirely outside its reach. Buy a VPN for privacy if that matters to you. Protect your passwords with length, uniqueness, a manager, and 2FA - And give the VPN account itself the same treatment, because it's a password-protected service like any other, and a uniquely sensitive one.

FAQ

Does a VPN stop hackers from stealing my passwords on public Wi-Fi?

It stops local eavesdropping, but HTTPS already encrypts your password on its way to any legitimate login page, so the marginal gain is smaller than advertised. The VPN's real added value on public Wi-Fi is hiding metadata and neutralizing rogue-hotspot DNS tricks. Phishing pages and malware - The common ways passwords are actually stolen - Work identically with or without the tunnel.

Can my VPN provider see my passwords?

Not for HTTPS sites, which is nearly everything: your traffic is TLS-encrypted end-to-end inside the tunnel, so the provider sees only which domains you contact and when. What the provider can see is that metadata, which is why choosing an audited, reputable service matters - You're moving trust from your ISP to them, not eliminating it.

Is a VPN safer than HTTPS for logging in?

They're different layers, not competitors. HTTPS encrypts and authenticates the connection between you and the specific website - That's what protects the password itself. A VPN encrypts everything between you and the VPN server, hiding it from the local network. Ideal is both at once, which is what you automatically get by using a VPN in a modern browser.

What happens if someone hacks my VPN account?

They can typically view your connection metadata and manage account settings, and in bad cases influence how your traffic is routed - Inverting the privacy the product promised. VPN accounts get credential-stuffed like any subscription. Give yours a unique random password and enable two-factor authentication with the provider.

Do I need a VPN if I already use a password manager and 2FA?

For password security specifically, no - The manager and 2FA address the attacks that actually account for most compromises. A VPN earns its keep on privacy grounds: hiding browsing metadata from ISPs and local networks, and on hostile networks where rogue portals and DNS games are plausible. Treat it as a complement to password hygiene, never a substitute.