Exodus
Read all reviews for Exodus →
Exodus Wallet Left Me Exposed to Unauthorized TRX Withdrawals
I recently experienced a devastating loss in TRX—not because I entered my seed phrase somewhere shady, but due to Exodus seemingly mishandling an incoming micro-deposit from an unknown source. Here’s what happened: • I received a small unexpected TRX deposit from an unknown wallet. It seemed harmless at first—just a few TRX, supposedly from airdrop or test transfer. • Shortly after, an unauthorized withdrawal cleared out a large portion of my balance without my approval. The culprit transaction was: Hash: 5c5e8da255c5f14ee9020d870132eed497f7b9375bff46d7cac2e0bcf17dd1df This transaction represented a withdrawal from my wallet that I didn’t authorize (i.e. no interaction confirming it from my end). It appears the small deposit somehow triggered an exploit or a permission that allowed toxins or malicious contract logic to empty the account. ⸻ ⚠ Why I’m Holding Exodus Accountable: • No alert or confirmation prompt: Exodus showed zero warning when the withdrawal executed. No sign of a suspicious contract or permission grant. • No isolation for unknown incoming TRX: Even a minor deposit triggered a withdrawal event—something wallets like MetaMask, Binance Wallet, or hardware wallet interfaces typically alert on (e.g., token approvals, new contract interactions). • Support was unhelpful: When I contacted Exodus, they said they couldn’t help since it wasn’t due to phishing. They offered no recourse or explanation. • Lack of advanced safeguards: No transaction signing protections, no per-contract whitelists, no revoke feature for weird incoming tokens or micro‑deposits. ⸻ 📉 Full Impact and Frustration: Because Exodus didn’t warn me, I lost all the crypto and live savings in the wallet. It’s not just about human error—it’s about software design that fails when unexpected tokens or contracts interact with a wallet. I should not lose funds because I happened to receive random TRX.