A password-free network share is exactly what it sounds like: a folder on your local network that any connected device can browse, read, and copy from without entering credentials. Most people set them up for convenience, sharing photos between a laptop and a TV, or making documents accessible from every room. The problem is that Bitcoin wallet files, seed phrase text documents, and exchange screenshots often end up in those same folders, and that turns a convenience into an open door.
Why this risk is different from public Wi-Fi
Most Bitcoin security advice focuses on external attackers: hackers probing you from outside, phishing emails from strangers, malware downloaded from dodgy sites. A password-free share is an internal threat. The attacker doesn't need to break through your router. They're already inside your network, whether that's a housemate, a visitor who connected to your Wi-Fi, or malware that arrived on another device and is now scanning your local subnet.
Windows and macOS make file sharing easy, and that ease is the problem. SMB (the file-sharing protocol Windows uses) and AFP (the equivalent on older Macs) will broadcast the existence of open shares to every device on the same subnet. A scanning tool like NetDiscover or even the built-in network browser on most operating systems will find open shares in seconds. No password prompt. No log entry you'd notice. The attacker just navigates to the folder and copies what they want.
The same risk applies to NAS (network-attached storage) devices that ship with default credentials or no password at all. Synology and QNAP units are popular for home backup, and both have been targeted by ransomware groups specifically because so many units sit on home networks with weak or absent authentication.
What Bitcoin holders typically store on shared folders
The most dangerous files aren't always obvious. Consider what a typical Bitcoin holder might save in a shared location:
- A text file or spreadsheet listing wallet addresses and seed words, labelled something like "crypto backup" or "BTC info"
- Screenshots of QR codes from an exchange or wallet app
- A photo of a handwritten seed phrase taken for backup convenience
- An exported wallet file from a software wallet such as Electrum or Exodus
- A PDF from an exchange containing account details or API keys
Any one of these, sitting on an open share, gives an attacker everything they need to drain funds. The wallet file and a known password is enough for many software wallets. The seed phrase alone is enough for all of them. If you've stored your seed phrase in a text document on a shared drive, treat that seed phrase as compromised and generate a new wallet immediately.
How to check whether you have an open share right now
On Windows, open File Explorer and look at "Network" in the left panel. Any device that appears with a shared folder icon is broadcasting shares. Click on it. If you can browse the contents without entering a username and password, the share has no authentication. On macOS, open Finder, select "Network" in the sidebar, and try the same test.
To check your own machine, open Command Prompt on Windows and type net share. This lists every share your computer is currently offering to the network. Any entry without a "permissions" note attached to a user account is worth investigating. On macOS, go to System Settings, then Sharing, and look at what folders appear under File Sharing.
On a NAS device, log into the admin panel (usually via a browser at the device's local IP address) and check the user accounts section. If a shared folder is set to allow "Everyone" or "Guest" with read access and no password, that's the problem. Change it immediately.
How to close the gap without breaking your setup
You don't need to disable file sharing entirely. You need to put authentication in front of every share that could contain sensitive information. The fix is the same across platforms: require a username and password, and only give that credential to devices and people who genuinely need access.
On Windows, right-click the shared folder, go to Properties, then Sharing, then Advanced Sharing. Under Permissions, remove "Everyone" and add specific user accounts with the minimum access they need (usually "Read" for media folders, nothing at all for anything financial). On macOS, go to System Settings, Sharing, File Sharing, and use the "+" button to add users with explicit permissions. Remove any "Everyone" entry with read access from sensitive folders.
On a NAS, disable the guest account entirely and create individual user accounts for each device that needs access. Enable SMB signing if the device supports it. SMB signing prevents an attacker from intercepting and modifying traffic between devices on the same network, which is a separate but related threat.
Beyond locking the share itself, don't store Bitcoin-related files on a shared drive at all. Seed phrases belong on paper or on a metal backup stored offline, not in a folder that any networked device can read. If you need a digital backup, use an encrypted container. VeraCrypt creates encrypted volumes that look like ordinary files but require a password to open, even if someone copies the file off your share.
The network matters as much as the device
Even with password-protected shares, an open home network multiplies your risk. If your Wi-Fi password is weak or you've handed it out freely to visitors, those devices are inside your perimeter. Setting up a guest network for visitors keeps them separated from the subnet where your NAS and main computers live. Most consumer routers sold in the last five years support guest network isolation, where guest devices can reach the internet but can't see other local devices.
McLeod Pacific Investments advises every Bitcoin holder to treat their home network as a security layer, not just an infrastructure convenience. The same discipline that goes into securing a shared home network applies directly here. Network segmentation is not complicated to set up and it dramatically narrows the attack surface available to anyone who gets onto your Wi-Fi.
If you run a full Bitcoin node or a Lightning endpoint at home, those devices talk to the broader internet, which makes their local network position even more sensitive. A node on the same subnet as an open share is a combination worth taking seriously.
Specific mistakes that make this worse
Three patterns come up repeatedly when holders discover this vulnerability too late. First: syncing a cloud backup tool like Dropbox or Google Drive to a folder that is also a network share. Now the files are accessible locally without a password and uploaded to the cloud, doubling the exposure. Second: naming files helpfully. A file called "bitcoin-seed-phrase.txt" is found in seconds by any script scanning for crypto-related filenames. Third: forgetting that smart home devices, smart TVs, and games consoles are also on your network. These devices often run stripped-down operating systems with limited security, and a compromised smart TV can absolutely scan and read an open SMB share.
Password-free network shares don't feel dangerous because they're internal. That's exactly what makes them dangerous. Locking them down takes ten minutes. Recovering Bitcoin from a drained wallet takes much longer, and usually isn't possible at all.