Browser Wallets at Work: HTTPS, DNS & VPN Security

I have checked my portfolio value in about 30 seconds at a friend’s place, borrowed their computer, plugged in my hardware wallet, and thought I was good because the padlock looked fine. That is exactly the kind of moment where people get burned.

In this article, based on Watch the video, I will explain how attackers can compromise an internet connection and steal crypto from users who access wallets in a browser. We will look at invalid HTTPS certificates, valid-but-wrong certificates caused by corporate or local certificate authorities, DNS poisoning, websites that ask for your 24-word seed, and which safety tools actually help.

Why network-based crypto theft happens

You are vulnerable to these kinds of attacks any time you are connected to an internet connection where you do not control or trust the modem, router, or DNS server being used.

That does not only mean public Wi-Fi. It can include:

  • A share house with other housemates
  • An internet cafe
  • A hotel network
  • A school or university network
  • A corporate work network
  • A dodgy VPN provider
  • Most free VPN providers, in my experience

The problem is that a browser wallet depends on the path between your computer and the website. If an attacker can influence that path, they may be able to redirect you to a fake site, serve a malicious download, or make your device trust something it should not trust.

Fake wallet page asking for a 24-word seed
A fake wallet recovery page asking for a 24-word seed

This is why “I only checked my balance” can still be dangerous. If you are using a browser-based wallet on an untrusted network, you may already be exposed before you sign anything.

What to look for when checking your wallet online

Invalid HTTPS certificates

The first thing I always watch for is an invalid HTTPS certificate.

If you are browsing a wallet and the browser shows a warning that the connection is not secure, stop immediately. Do not keep going. Do not click through it. You probably are not on the website you think you are on.

Browser showing an untrusted certificate warning
An invalid or untrusted HTTPS certificate warning

In my video, I show a browser with a “Not secure” address bar and a certificate dialog saying the CA root certificate is not trusted. That is a clear red flag. If you see that while accessing a wallet, leave the site.

Valid-looking but wrong certificates

This is where it gets more subtle.

A website can have a valid-looking HTTPS certificate even if it is fake. That happens when the certificate was issued by a local, corporate, or attacker-controlled certificate authority that your computer has been told to trust.

For example, I may open what looks like trezor.io and click through to the wallet. The browser may show a normal padlock because the certificate is technically valid on that machine. But the site is not really Trezor’s wallet. It has been issued by a local certificate authority on my home network for demonstration purposes.

A spoofed wallet page with a seemingly valid HTTPS setup
A fake wallet page demonstrating how a valid-looking certificate can still be wrong

This is the part that surprises people. A padlock does not always mean “this is the real site.” It means your browser trusts the certificate chain for this machine, on this network, at this moment.

Corporate and education network trust issues

If you are using a work or school computer, there may be extra certificate authorities installed by IT. In many organizations, that is done for legitimate monitoring or security purposes.

But when it comes to crypto, you need to ask yourself: do I want to trust the entire IT team in that organization with my wallet access?

That question matters because a corporate network can technically allow someone with administrative control to intercept HTTPS traffic if the right certificates are trusted on your machine. For everyday browsing, that may be acceptable under company policy. For accessing crypto wallets, I would be much more careful.

The biggest red flag: sites asking for your 24-word seed

The big one to look out for is a website that asks you straight up for your 24-word seed.

If a wallet site asks you to enter your recovery words directly into the browser, treat that as a scam unless you have a very specific, documented reason why that is safe and expected. In most cases, it is not.

Fake Trezor-style phishing page with a seed entry grid
A fake wallet site asking for recovery words

Never enter your 24-word seed into a website just because the page looks similar to a real one. Attackers can make convincing clones, especially when they control DNS or have a valid-looking certificate on that network.

How to stay safer with browser wallets

Use a hardware wallet and verify transactions on its screen

The first thing I recommend is using a hardware wallet and verifying the transaction address and amount on the device’s own screen for every transaction.

This matters because even if you are redirected to a phishing website, the hardware wallet can still show you where the funds are actually going. If the destination address or amount does not match what you intended, do not sign it.

A trusted screen gives you one more layer of protection against a compromised browser session.

Always connect to crypto sites over HTTPS

Always connect to crypto-related websites via HTTPS. These days, decent wallets and exchanges should force HTTPS anyway.

If the site is not using HTTPS, that is another reason to stop and reconsider. You do not want your wallet traffic exposed on an untrusted network without at least a basic transport-layer security layer.

Use local wallet software where available

Another way to reduce risk is to use local wallet software when it is available.

This can be:

  • An installed desktop app, such as Ledger Live
  • A standalone wallet program, such as Electrum
  • A downloadable local version of a web wallet

Some wallets allow you to download a copy and run it locally on your computer. You still access the local version through your browser, but you are no longer relying on the network path between you and the wallet provider in the same way.

MyEtherWallet opened from a local file path
A web wallet opened locally from a file path

This does not make every attack impossible, but it reduces your exposure to certain network-level attacks that rely on redirecting you away from the real wallet provider.

Portable Firefox can be safer than portable Chrome or Brave in some corporate settings

If you are in a corporate environment and need to use someone else’s PC, I would suggest using your own portable copy of Firefox rather than portable Chrome or Brave.

The reason is that Firefox does not automatically trust all certificate authorities installed on the host computer by default. In my test, when I tried to continue through to a wallet with a locally issued certificate, Firefox blocked it because I had not explicitly told Firefox to trust that certificate authority.

Portable Chrome and Brave are different in this context. They can automatically trust certificate authorities that the PC trusts, which means they may accept a local or corporate certificate without giving you the same warning.

Firefox recommended over Chrome/Brave for some shared-PC scenarios
Comparison showing Firefox as safer than Chrome/Brave in certain shared PC environments

This is not a statement that Firefox is perfect. It can be configured to trust all certificates on the computer, and in many educational or corporate environments it may already be set up that way. But a fresh portable copy of Firefox on a USB drive can add another layer of protection when you are trying to access crypto wallets on an untrusted machine.

Learn how to verify download signatures

A simple network attack can redirect you to download a malware-infested version of a wallet instead of the legitimate one.

That is why learning how to verify download signatures is important. If you download wallet software, you should be able to check that it matches what the official project says it should be. This helps protect against malicious downloads caused by DNS redirection or other network-level interference.

Use a trusted VPN on untrusted networks

Another way to stay safe is to use a trusted VPN service when you are on an untrusted network.

A VPN allows your device to connect through the VPN provider directly to the internet, essentially bypassing your local network and ISP for that traffic. But it must be a trusted VPN service. A free or bad VPN could deliberately redirect you to phishing sites.

VPN traffic path bypassing the local ISP
A diagram showing device traffic routed through a VPN provider

Setting up a VPN back to your own home network can also be a great option if you have the technical ability to do it safely. The SoftEther project makes this easier, but setting it up properly is beyond the scope of this article.

What will not keep you safe

I want to be clear about a few things that people often think protect them, but may not in these scenarios.

Google DNS on a hostile network

Using Google as your DNS server on a hostile network will not necessarily keep you safe. It is easy for a router or server on the network to redirect all DNS requests through a specific DNS server, and this can happen transparently to the user.

If the local network controls your traffic, changing your preferred DNS in the browser may not be enough.

Portable Chrome or Brave on someone else’s PC

A portable copy of Brave or Chrome for corporate environments or shared PCs will not automatically protect you from locally trusted certificates. These browsers can trust certificate authorities that the host PC trusts.

That means a valid-looking local or corporate certificate may still be accepted without a strong warning.

Browser plugins like MetaCert

Browser plugins such as MetaCert are useful in some contexts, but they will not keep you safe against redirects via DNS poisoning to a host with a valid certificate.

MetaCert showing green while the site is still unsafe
A browser plugin showing a positive security indicator on an unsafe fake wallet

In my demonstration, both MetaCert and NetCraft were happy as can be on a fake Trezor-style wallet running on my own home network. The plugins were not detecting the problem because the attacker had created a situation where the computer considered the HTTPS certificate valid.

So if you are relying only on browser security badges or extensions, you may still be exposed to sophisticated local-network attacks.

What to do if you spot a scam

If you think a network is compromised, do not just give it another go and hope it will be fine. It probably won’t.

Here is what I would do:

  1. Stop using the wallet immediately.
  2. Do not enter your seed phrase, private key, or password into any suspicious site.
  3. Disconnect from that network.
  4. If appropriate, report it to the network administrator.
  5. Consider reporting it to their boss if the admin may be involved.
  6. Report serious cases to local law enforcement where applicable.

Reporting only to the network administrator may not be enough if they are the ones running the attack. Also remember that on unsecured Wi-Fi, the attacker may not even be on site. The network itself can be the problem.

Practical checklist before checking a wallet online

Before you access a crypto wallet in a browser, run through this quick mental check:

  1. Do I control or trust this modem, router, and DNS setup?
  2. Is the website using HTTPS correctly?
  3. Does the certificate look right for the real site?
  4. Am I on a work, school, public, hotel, cafe, or shared network?
  5. Am I being asked to enter my 24-word seed into the browser?
  6. Can I verify the transaction address and amount on a hardware wallet screen?
  7. Should I use local wallet software instead of the hosted web version?
  8. Would a trusted VPN reduce my exposure here?

If any answer makes you uncomfortable, do not proceed. Crypto is irreversible, so being cautious is worth more than convenience.

Conclusion

Browser wallets are convenient, but they can be dangerous on networks where you do not control or trust the infrastructure. Invalid certificates are an obvious warning sign, but valid-looking certificates from local or corporate certificate authorities can be far harder to spot. DNS poisoning and malicious downloads make the problem even worse.

The safest approach is to reduce your exposure: use a hardware wallet with on-device verification, prefer HTTPS, consider local wallet software where available, be careful on shared PCs, learn download signature verification, and use trusted VPNs when needed. And if something looks wrong, leave the network immediately.

Questions from viewers

Common questions from the comments on this video, with my answers.

How is the DNS poisoning attack on hardware wallet websites actually executed?

It is surprisingly straightforward and can be set up in about half an hour by anyone with the right knowledge. The device handling DNS on the network simply returns the address of a different webserver for the specific subdomain used by the wallet (like wallet.trezor.io). This allows the attacker to serve a convincing, modified version of the wallet page that looks legitimate but is controlled by them.

Why are Chrome and Brave considered unsafe in corporate or shared environments even if they are fine at home?

They are safe at home, but in work, school, or internet cafe settings, your computer is likely configured to trust additional local certificate servers. This is normal for accessing internal sites without errors, but it also means IT administrators can issue certificates for phishing sites. Your browser will see these as valid because they come from a trusted local authority, allowing attackers to intercept your traffic without triggering standard security warnings.

Does bookmarking the genuine website prevent DNS poisoning or man-in-the-middle attacks?

No, bookmarking does not help in the scenarios I cover. If you are using a managed PC at work, school, or a shared PC at an internet cafe, the person controlling that environment has access to both your device and the network's DNS server. They can redirect your traffic regardless of where you click. However, using a trusted VPN can bypass these local controls and protect you.

Is it dangerous to download firmware updates from a potentially compromised website?

Most decent hardware wallets only accept firmware that is cryptographically signed by the vendor, and there have been no demonstrated wild attacks that successfully bypass this signature check. Additionally, vendors usually publish firmware hashes and prompt you to confirm them on the device itself. While malicious firmware could theoretically do harm, the built-in verification steps make it significantly harder for an attacker to silently install bad software via a fake site.

Stuck with a wallet recovery?

I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.

Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.

Found this useful?

These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.

Stuck on this?

Book a one-hour session and I’ll walk you through it, or ask about a trusted recovery.

Recovery guides

More guides