hot wallet

A hot wallet is a wallet whose private key or signing capability is used on an Internet-connected device. This entry explains how hot and cold key environments differ, why hot wallets fit small daily balances, and how to reduce approval, phishing, malware, and operational risk.

For educational purposes only; not investment advice. Investing may result in loss.

Direct answer

A hot wallet keeps its private key or signing capability on an Internet-connected device, such as a browser extension, mobile app, or desktop program. It can send transactions and connect to applications quickly, but its key, interface, and signing flow are more exposed to malware, phishing sites, and remote compromise.

Hot and cold describe key environments, not asset types. If a recovery phrase was generated or imported on an Internet-connected phone, turning the phone off later does not provide the same isolation as keeping the phrase offline from the start. An exchange account is also online and convenient, but the exchange usually controls the keys; it is therefore a custodial account, not a self-custodied hot wallet.

Being hot does not make a wallet automatically insecure. Reputable software can use secure hardware, encrypted storage, and operating-system sandboxes. Even so, an online device handles web pages, QR codes, clipboards, notifications, and third-party apps every day, which expands the attack surface. Treat a hot wallet like a pocket wallet rather than keeping all assets in one frequently used address.

How it works

When a wallet is created, the software generates seed material and derives private keys and addresses. To send a transaction, the wallet unlocks the relevant key locally, signs the transaction, and broadcasts the signed data. When a user connects to a DeFi application, the site learns the disclosed address; it receives a signature only after the user approves a signing request.

“Connect wallet” normally does not transfer assets by itself, but later signatures can have financial consequences. A message signature may log in to a service or authorize an order or permit; a transaction signature can call a contract; and a token approval lets a designated spender use tokens up to the approved amount. A wallet popup does not make a request trustworthy. Check the domain, network, contract, amount, and permissions before approving it.

A wallet password protects the local encrypted vault, not the underlying recovery phrase. Malware that controls the browser after the wallet is unlocked may replace addresses, manipulate signing prompts, or read the clipboard. Anyone with the recovery phrase can restore the wallet elsewhere and bypass the local password, so changing that password does not contain a recovery-phrase compromise.

Example

Assuming that the user has long-term assets worth 100,000 yuan, they only need 2,000 yuan per week to participate in on-chain activities. Long-term assets can be placed in a cold-storage or otherwise less-interacted address, and the hot wallet only retains 2,000 to 5,000 yuan and a small amount of gas. Even if an approval phishing attack drains the hot wallet, the balance limits the exposure.

During a swap, the user follows a search advertisement to an imitation site whose domain differs by one letter. The site first asks to connect the wallet, then presents a “security verification” that is actually an unlimited token approval. If signed, the approval may let the attacker use the token contract to transfer the address’s balance without learning the recovery phrase. Disconnecting the site does not revoke an on-chain approval; the user must submit a separate transaction on the same network to set the allowance to zero.

Another scenario is address poisoning. An attacker creates a lookalike address and sends a tiny transfer so that it appears in the user’s history. If the user later copies the wrong history entry, they may send 5,000 USDC to the attacker. Do not rely only on the first and last four characters: obtain the full address from a trusted source, use a verified address book, and make a small test transfer first.

Risks

A hot wallet is exposed to malware, phishing, session theft, malicious browser extensions, excessive smart-contract permissions, clipboard replacement, and operator error. Limit balances and approvals, separate wallets by function, verify domains and recipient addresses, and prepare asset-migration and revocation procedures. A hot wallet is a convenience layer, not a substitute for offline key storage.

Common misconceptions

Myth 1: Authorization is revoked when disconnecting from the website

Disconnecting only cancels the front-end session. The authorization on the chain still exists, and a revocation transaction needs to be submitted separately.

Myth 2: The wallet has a password, and it does not matter if the mnemonic phrase is leaked

An attacker can use the mnemonic phrase elsewhere to recover the private key, completely bypassing the local password.

Myth 3: Signing messages will not affect assets

Some messages can constitute orders, permits or login authorizations. The signature type and actual content should be read.

Myth 4: The address is permanently safe after a small amount of testing

Subsequent copies may still be replaced by Trojans, and each transaction should be checked before signing.

Sources

Blockchain Technology Overview - NIST (accessed: 2026-08-20)
Ethereum security and scam prevention - Ethereum.org (accessed: 2026-08-20)
ERC-20: Token Standard - Ethereum Improvement Proposals (accessed: 2026-08-20)