Yes. A hardware wallet can contain vulnerabilities or be physically modified, and no device guarantees protection against every attack. It reduces risk by keeping your private keys—the secrets used to authorize spending—separate from your computer or phone and letting you check important details on its own screen.

Funds can also be stolen without breaking those protections. An attacker who obtains a usable wallet backup can restore the wallet elsewhere, while a misleading application can persuade you to approve a payment you did not intend. Understanding these different routes helps you recognize what the device protects and where your own checks matter.

Can malware steal funds through a hardware wallet?

A hardware wallet is designed to sign transactions internally without giving private keys to the connected computer or phone. Malware can still change what the application displays, replace a copied address, or request a harmful action. If you approve the attacker's payment details on the hardware wallet, the device can sign a valid transaction that sends funds to the wrong person.

Before sending, compare the full destination address and amount on the BitBox screen with the payment you intend to make, using recipient details from a trusted source. Do not approve if they differ. When receiving, verify your receiving address on the BitBox screen before sharing it with the sender. For examples of these attacks, read how attackers use fake apps and manipulated addresses.

Use the official BitBoxApp or trustworthy compatible wallet software. The device screen is your reference for transaction details, but do not ignore an authenticity warning or an anti-klepto protocol failure in the BitBoxApp. The latter means a check intended to prevent certain signatures from leaking private-key information has failed. Stop the affected action even if the device screen looks normal.

How phishing and exposed backups bypass the device

An attacker does not need your hardware wallet if they obtain the information needed to restore its wallet. A complete microSD backup or recovery words can restore the wallet without the original device or its password. If the wallet uses an optional passphrase, that exact passphrase is also required; it is separate from the device password and is not included in the backup.

Phishing tries to obtain these secrets through fake apps, websites, messages, or supposed support instructions. Never share recovery words or enter them into a computer, phone, website, support chat, or AI tool. BitBox Support will never ask for your wallet secrets or tell you to transfer funds to a supposedly protected wallet supplied by someone else. To check an unexpected contact, start a new inquiry through an independently opened official channel; see how to check whether a BitBox contact is genuine.

Keep backups offline, private, and separate from the device. The BitBox microSD backup is unencrypted, so the device password does not protect someone who obtains it. See BitBox backup options and their protection requirements.

What if the device is stolen or physically modified?

A thief with your device may try to guess its password or extract its secrets. BitBox02 and BitBox02 Nova combine encrypted wallet storage with a secure chip that limits and slows password guessing. These safeguards make unauthorized access harder; they do not justify assuming that every stolen device is harmless. Keep your device password private and difficult to guess. Someone with both the device and the information needed to unlock the wallet may be able to spend its funds.

A different risk arises when someone modifies or replaces a device before you receive it, or gains temporary access and returns it to you. Unlocking a modified device can expose secrets despite protections intended to resist theft. If you suspect physical interference, disconnect the device and do not unlock it, create or restore a wallet on it, or send funds to it while the concern remains unresolved.

Buy directly from BitBox or an authorized reseller, set up your wallet yourself, and never use recovery words supplied by a seller. Follow the checks before first use. The BitBoxApp's authenticity check verifies a certified device identity; a successful result does not prove that no extra electronics have been added. For the role and limits of these checks, read how BitBox reduces supply-chain risk.

Can firmware or hardware have vulnerabilities?

Yes. Firmware, the software running on a hardware wallet, can contain bugs, and hardware protections also have limits. A vulnerability could allow an attack that the device was designed to prevent. Keeping the BitBoxApp and device firmware up to date helps you receive available security fixes. For more background on how security research leads to fixes, read firmware updates in the age of AI.

BitBox combines safeguards rather than relying on a single check. Signed firmware restricts which software the device runs; open-source code, reproducible firmware builds, security reviews, and the bug bounty program support scrutiny and the discovery of weaknesses. None proves that every vulnerability has been found. For the design principles, see what makes a hardware wallet secure. The technical BitBox threat model describes its assumptions and limits.

What to do if you suspect a security problem

Stop the suspicious interaction and do not approve further actions. If you followed suspicious instructions, installed unknown software, or disclosed wallet information, follow what to do after interacting with a phishing attempt, choosing the section that matches what you actually did. Receiving a suspicious message alone does not establish wallet compromise or require a reset or fund transfer.

For a stolen device, suspected physical modification, an unresolved app warning, or an unexplained outgoing transaction, open the official BitBox Support contact form independently. Describe what happened and include the exact warning or relevant transaction identifier, if available. Never include recovery words, wallet backups, private keys, passwords, or passphrases.

A replacement device or a firmware update does not make an exposed wallet secret private again. If you suspect exposure, do not reset the device or restore the same backup as a supposed fix; use the appropriate response guidance before making changes that could affect access or evidence.