Ethereum wallet drainer steals 59 ETH from inactive holder
The eight-year-old wallet had survived intact; the four-year pause before the user touched it again made it a sitting target for a long-dormant phishing kit.
Every Zipp story tagged #Phishing, newest first.
The eight-year-old wallet had survived intact; the four-year pause before the user touched it again made it a sitting target for a long-dormant phishing kit.
Using GIWA’s expected Chain ID, attackers made a counterfeit network look credible. The incident shows that a matching chain identifier does not authenticate the RPC endpoint or bridge users connect…
The attack shows how compromised media accounts and impersonated journalists can turn familiar interview workflows into a security risk for crypto executives.
The case highlights how attackers can bypass platform security by persuading users to move funds themselves, then launder the cryptocurrency through a chain of conversions and cash-outs.
The case highlights how impersonation can turn a trusted exchange brand into a tool for stealing crypto, while the plea deal drew a shorter sentence than prosecutors sought.
On-chain forensics traced $1.1M in months, but the underlying device-code auth vulnerability that powered EvilTokens is already being groomed for Gmail and Okta.
The hardware remained intact, but recovery-phrase reuse and trusted email infrastructure gave attackers paths around the device.
The campaign targeted compromised Windows endpoints, not Coinbase, MetaMask or official extensions, while HP disclosed no victim count or aggregate loss.
No Bitcoin keys or funds were exposed, but names and delivery addresses can make recovery-word phishing look credible long after a wallet purchase.
Wallets remain safe, but a third-party newsletter breach exposed email lists across multiple Bitcoin firms. The danger is in following the email's recovery-seed instructions.
Trezor's second third-party breach in two months, and this time attackers sent phishing from the vendor's own domain, not a look-alike address.
Hardware-wallet security extends beyond the device itself: a vendor breach can make phishing alerts look credible and turn user trust into the attack surface.
Attackers reaching users through Trezor's own legitimate email channel is the real escalation: even offline seed storage doesn't shield users from phishing through the vendor's front door.
Hardware-wallet owners face phishing and physical-targeting risk as roughly 67,000 more records resurface from a vendor Trezor believed had purged them. The 90-day deletion policy did not hold.
The expanded exposure raises phishing and physical-security risks for hardware-wallet users, while Trezor says its own systems and hardware wallets remain secure.
Sensitive KYC docs paired with public Bitcoin addresses turn a non-custodial service's privacy promise into a target list, with phishing and physical safety now the live threats.
No breach has been confirmed, but the volume of reset attempts targeting prominent crypto figures points to a coordinated effort exploiting X's open username-based reset flow.
Nine of the 40 IDs first shipped as benign sports-score tools, the kind of identity swap that turns a trusted extension into a wallet drainer after the user already approved it.
The exposure is the third wallet-industry customer-data incident in months, all routed through commerce or shipping vendors rather than the wallets themselves, putting the spotlight on the…
Private keys and seed phrases are untouched, but names, physical addresses and contact details are now in the wild, giving attackers a clean phishing dataset that will linger well past the patch.