A cryptocurrency holder with significant EVM-based assets faces a practical security decision: whether to keep a hot wallet on a daily device or to move assets into cold storage and accept slower transaction workflows. If cold storage is the choice, the question becomes whether that cold storage can integrate with a convenient interface. Rabby Wallet supports hardware wallet pairing, but the relationship between a browser extension and a hardware device raises a crucial question—whether the connection introduces new attack surfaces or whether true air-gapped security is actually achievable within that workflow.
The distinction matters because cold storage is meaningful only if it remains cold. A hardware wallet kept offline but paired with a compromised browser extension can still leak transaction details, counterparty information, or even the derivation paths of unused addresses. Conversely, a hardware wallet that is never connected to any online interface becomes difficult to use for legitimate transactions. Understanding what Rabby actually does when signing through a hardware device—and what it does not do—is essential to evaluating whether cold storage remains genuinely isolated or whether convenience has reintroduced risk.
How hardware wallet support actually works in Rabby
Rabby Wallet integrates with hardware wallets through standard protocols, most commonly USB or Bluetooth connections managed by the host computer’s operating system. When a user connects a hardware device—typically a Ledger, Trezor, or similar—the browser extension can discover the device and display accounts derived from the hardware wallet’s master seed. At this point, Rabby acts as an interface layer: it prepares transactions, displays information about where funds are being sent, shows fees and gas estimates, and formats the transaction for signing.
The critical boundary is where Rabby stops and the hardware device takes over. When a user approves a transaction, Rabby sends the transaction details to the hardware wallet rather than signing it locally. The hardware device receives the information, displays it on its own screen, allows the user to verify the destination, amount, and contract interaction, and then performs the signing operation using its isolated private keys. The signed transaction is returned to Rabby, which then broadcasts it to the blockchain network.
This architecture means that private keys never leave the hardware device. Even if Rabby were completely compromised, a hardware wallet would still refuse to sign transactions that differ from what the user approved. That is the core security promise. However, the architecture also means that the hardware wallet is only as secure as the channel through which it receives transaction information. If Rabby displays one transaction but sends another to the hardware wallet, the user might approve a transfer they did not intend. Similarly, if the operating system hosting the browser extension has been compromised, it could intercept or modify the transaction data before it reaches the hardware device.
According to the EIP-6963 multi-wallet provider standard, hardware wallets integrated with Rabby should follow standardized wallet interface specifications for discovering and connecting to hardware devices. This standardization helps ensure that the connection protocol itself is not introducing proprietary vulnerabilities. However, standardization does not eliminate the risk that the operating system or browser itself could be compromised.
Air-gapping: what it actually means for Rabby
An air-gapped system is one that has no network connection. The classic air-gap model involves a computer that is powered off when not in use, never connects to the internet, and receives or sends data only through physical media such as USB drives or hardware wallets. In that scenario, a purely offline computer cannot be attacked by network-based malware, and transactions cannot be automatically broadcast without the user’s explicit decision to move them to a connected device.
Rabby Wallet is not an air-gapped application. It is a browser extension that runs on a networked device, connects to blockchain nodes, queries account balances, checks historical transactions, and displays real-time gas prices. An online Rabby interface is inherently connected to the internet. The only way to achieve a true air-gap would be to run Rabby on a completely offline computer and manually transfer transaction data to a connected device using external media or to accept that transaction simulation and balance displays would not function.
What Rabby’s hardware wallet support does achieve is a form of signature air-gapping—the private key remains isolated and signing occurs offline, even though data flows to and from the device. The threat model in this scenario is not that the private key will be stolen directly, but rather that the user might sign a malicious transaction without realizing it. The hardware wallet mitigates this by displaying the transaction on its own secure screen, where the user can verify it matches their intent before confirming.
This is genuinely valuable, but it is not the same as being completely air-gapped. A completely air-gapped cold wallet would involve no online component whatsoever. A signature air-gapped setup using Rabby still involves an online browser extension on the user’s device, which can see transaction histories, observe which addresses are being used, learn approximate account balances, and communicate with various dApps and blockchain nodes. The hardware device prevents key compromise and unauthorized signing, but it does not prevent the online component from collecting or leaking information about the user’s activities.
Threat model: what the hardware wallet protects and what it does not
The hardware wallet’s strongest protection is against private key theft. Even if malware has full access to the host computer, it cannot extract the signing keys stored on the hardware device. Similarly, the hardware wallet protects against clipboard hijacking attacks, where malware modifies a destination address before the user confirms it—because the hardware device displays the address on its own screen, not the computer’s screen, and the user can verify it there.
The hardware wallet also protects against a category of threat called transaction substitution. If the browser or operating system intercepts a transaction prepared by Rabby and modifies it to send funds to a different address, the hardware wallet will display the modified destination. The user can then reject the signing request, preventing the unauthorized transaction.
What the hardware wallet does not protect against includes account enumeration, where an attacker observes which addresses are controlled by a particular user or how many tokens are held; transaction linkage analysis, where patterns in on-chain activity reveal relationships between addresses; and social engineering, where the user is tricked into voluntarily approving a transaction they did not understand. A hardware wallet will faithfully sign whatever the user approves. If the user has been misled about what they are signing—for example, if they believe they are signing a simple transfer when they are actually approving a smart contract that will drain their account—the hardware wallet will proceed as instructed.
This is why transaction simulation, which Rabby provides, is important. By showing the expected state changes before asking the user to sign, Rabby can help prevent the user from accidentally approving unexpected behavior. However, transaction simulation is only as reliable as the node providing the information and the code analyzing the response. Sophisticated attacks might involve giving a misleading simulation result or obscuring the true effect of a contract interaction.
Device compromise and the limits of isolation
A hardware wallet’s isolation is only meaningful if the device offering the isolation has not itself been compromised. In typical scenarios, a user’s computer—which runs a browser and Rabby Wallet—is far more likely to have been compromised than the hardware wallet, simply because the computer is constantly exposed to downloaded files, visited websites, and installed software. For that reason, the hardware wallet’s isolation is genuinely protective in most realistic threat models.
However, if the user’s computer has been compromised in specific ways, the isolation can be bypassed. For example, if malware has modified the USB drivers or the device communication layer, it might be able to intercept or replay previous transactions or perform transaction substitution more subtly. If the operating system has been compromised with root-level access, it could theoretically record the screen output of the hardware wallet or observe the USB communication in ways the user cannot detect.
A more immediate risk is the recovery phrase. Many users store the hardware wallet’s recovery phrase on the same computer as Rabby, often in a notes application or a photo. If the computer is compromised, that phrase can be stolen, and the hardware wallet can be recreated on an attacker’s device. For cold storage to remain cold, the recovery phrase must be stored completely offline—written on paper, stored in a vault, or kept in another form of physical media that is never connected to any networked device.
When you download rabby wallet and set it up with a hardware device, the critical security step is not the integration itself but the management of recovery phrases and backups. Rabby helps by ensuring that the local extension wallet does not need to hold the private keys, but Rabby cannot protect recovery information that the user stores carelessly.
Practical workflows: offline signing without air-gapping everything
In practice, users often implement a hybrid approach that keeps most assets in cold storage while maintaining an online interface for transaction preparation and monitoring. One workflow involves creating a hardware wallet, connecting it to Rabby on a daily-use computer only when signing is necessary, and then disconnecting it immediately after. Between transactions, the hardware device remains physically disconnected, reducing the window in which it could be attacked through USB or Bluetooth.
A more advanced workflow uses an air-gapped computer exclusively for transaction preparation: the user imports the hardware wallet’s public key into an offline Rabby instance, prepares transactions there, and then uses external media or a manual transaction broadcast process to complete the operation. This requires more technical skill and reduces convenience, but it significantly reduces the attack surface on the online component.
Another option is to maintain a separate signing device. Some users operate an air-gapped computer dedicated solely to hardware wallet management, keeping it offline except when connecting the device for signing operations. That computer never browses the web, never installs arbitrary software, and is powered off most of the time. In that scenario, Rabby would only be used on the offline device, and the online device used for balance checking or transaction broadcasting would not have access to private keys or recovery information.
Each of these workflows trades off convenience for security. The question of whether to use Rabby with a hardware wallet in a fully air-gapped scenario is not a binary yes-or-no; rather, it depends on the user’s threat model and how much inconvenience they are willing to accept. The Ethereum Foundation’s documentation on wallet security emphasizes that there is no one-size-fits-all solution and that users should consider their own risk tolerance.
Network-level considerations and node visibility
Even with a hardware wallet signing offline, Rabby still communicates with blockchain nodes to fetch account balances, transaction histories, and gas prices. These communications can potentially reveal which addresses are being monitored. An attacker observing network traffic could learn that a particular IP address is associated with specific Ethereum addresses, even if the actual transactions are signed offline.
Rabby does not force users to use a privacy-preserving node connection. By default, it may communicate directly with public RPC endpoints or nodes operated by infrastructure providers. Alternatively, users can configure Rabby to connect to a private node—either running locally or hosted privately—to reduce the amount of information leaked to third parties.
Using Tor or a VPN can obscure the IP address from which Rabby is communicating, adding another layer of privacy. However, this does not prevent the blockchain itself from revealing transaction patterns. Regardless of whether a user’s IP address is hidden, all transactions are ultimately broadcast to the blockchain network and are permanently visible on the public ledger. For users concerned about transaction privacy on Ethereum, NIST Cybersecurity Framework principles recommend compartmentalizing sensitive addresses and avoiding linking them through on-chain behavior, which is a user-level practice rather than something Rabby can enforce.
Regulatory and custodial considerations
Because Rabby Wallet is self-custodial, users retain full control of their private keys but also assume complete responsibility for loss or theft. This is materially different from using a custodial service, where the provider holds the assets and is typically subject to regulatory oversight. The UK Financial Conduct Authority (FCA) has published guidance on crypto asset custody and self-custody risks, noting that individuals holding their own keys should understand that loss of those keys may be irrecoverable.
In the United States, the CFTC has noted that self-custodial arrangements can reduce certain counterparty risks but increase user-level operational risks. Neither regulatory framework currently requires specific security practices for self-custodial wallets, but both emphasize that users should understand what they are responsible for.
For users in jurisdictions with anti-money-laundering or know-your-customer requirements, maintaining a self-custodial wallet does not exempt them from those obligations if they are engaging with regulated exchanges or services. Using Rabby with a hardware wallet does not change the regulatory status of the user’s activities; it only changes who is technically responsible for securing the keys.
Best practices for cold storage with Rabby and hardware wallets
If the goal is to use Rabby with a hardware wallet in as secure a manner as possible, several practices reduce risk. First, create the hardware wallet on a computer that is subsequently disconnected from the internet for the majority of the time. This reduces the window in which the device could be initially compromised during setup. Second, write the recovery phrase on paper and store it offline, never photograph it or type it into any digital device. Third, if you are storing significant assets, consider using an air-gapped computer for transaction preparation—prepare the transaction on an offline Rabby instance, then broadcast it from an online device without the keys present.
Fourth, regularly verify that hardware wallet firmware is up to date, as manufacturers release security patches. However, do not update firmware from an untrusted network; if possible, update from a computer you control and trust. Fifth, use a PIN on the hardware device if it supports one, adding another barrier to unauthorized transactions even if the device is physically stolen. Sixth, compartmentalize: keep different types of assets on different hardware wallets or different accounts on the same device, so that a compromise of one account does not immediately put all assets at risk.
Seventh, test your backup and recovery process before depositing significant funds. Confirm that you can recreate the wallet from the recovery phrase, that the addresses match what the hardware device shows, and that transactions can be signed and broadcast. This verification takes time but prevents the discovery of a problem when you urgently need to access your assets. Finally, maintain an inventory of which accounts are stored where and which recovery information belongs with which device, so that in an emergency you can act quickly without scrambling to reconstruct what is where.
Frequently asked questions
Can I use Rabby Wallet with a hardware wallet that is never connected to the internet?
No. For Rabby to function, it must run on a connected computer where it can query blockchain data, display balances, and prepare transactions. The hardware wallet itself remains offline and only connects when signing, but Rabby cannot operate in a completely air-gapped state. If your goal is a completely offline cold wallet, you would need to use the hardware wallet’s own interface or a dedicated offline tool, not Rabby.
Does using Rabby Wallet with a hardware wallet prevent my recovery phrase from being stolen?
No. The hardware wallet protects the private key during signing, but it does not protect the recovery phrase. If you store your recovery phrase digitally—on the same computer as Rabby, in cloud storage, or in a photo—it can be stolen if that computer is compromised. The recovery phrase must be stored completely offline, on paper or another physical medium, to remain protected.
Why would I use Rabby Wallet hardware wallet support instead of just using the hardware wallet’s own interface?
Rabby provides a more streamlined interface for EVM-compatible networks, better support for dApp interactions, and transaction simulation before signing. If you do not need those features, the hardware wallet’s native interface is simpler and reduces the number of applications involved. Rabby’s value is primarily for users who frequently interact with decentralized applications or who prefer a unified interface across multiple EVM networks.