According to @PeckShieldAlert, @SpecterAnalyst reported a $50M USDT address poisoning incident where the victim wallet 0xcB8078...00819 first sent a $50 test to 0xbaf4b1aF7E3B560d937DA0458514552B6495F8b5 and later mistakenly copied a lookalike 0xBaFF2F13638C04B10F8119760B2D2aE86b08f8b5, resulting in a 50M USDT transfer to the poisoned address (source: @PeckShieldAlert). No protocol exploit was indicated; the loss stemmed from misdirecting funds due to an attacker-seeded lookalike address, confirming an address poisoning vector rather than a smart contract breach (source: @PeckShieldAlert). For traders, this highlights elevated operational risk on high-value USDT moves and the need to verify full destination strings, use address allowlists, and avoid copying from transaction history or memos to reduce execution risk (source: @PeckShieldAlert). Label and monitor the disclosed addresses in transaction tools and adjust routing or venue selection when handling large USDT transfers to limit slippage and settlement risk (source: @PeckShieldAlert).