Yaël on Nostr: learned today that my old Trezor (circa 2014) has had its seed compromised. Haven't ...
learned today that my old Trezor (circa 2014) has had its seed compromised. Haven't used it in a while but spun it up today to see if I could use it in a multisig.
I sent a test transaction and it was immediately swept to the OKX exchange once it confirmed (saw it via mempool dot space).
Luckily it was only a small amount (test transactions are vital folks), but I sincerely have no idea how this happened. Always had a passphrase.
The only thing I can think of is perhaps a malicious Trezor Suite at some point?
Published at
2024-08-19 14:22:08Event JSON
{
"id": "556a4d344a90baa2a90ddac60ca7b9773988e15179c3f2c148a001152e0f11f7",
"pubkey": "a367f9eb1cb3a241a7f3646f31cd6d597bbbbf8eaeb5cd2e707d09b00633efea",
"created_at": 1724077328,
"kind": 1,
"tags": [],
"content": "learned today that my old Trezor (circa 2014) has had its seed compromised. Haven't used it in a while but spun it up today to see if I could use it in a multisig.\n\nI sent a test transaction and it was immediately swept to the OKX exchange once it confirmed (saw it via mempool dot space).\n\nLuckily it was only a small amount (test transactions are vital folks), but I sincerely have no idea how this happened. Always had a passphrase. \n\nThe only thing I can think of is perhaps a malicious Trezor Suite at some point? ",
"sig": "799bc9cb4bbacbd12049dadd66196bff5971fb40e2d299387dece95833c53d6faaeb09895a15338e7adcb6a69d8e5ff1e376472d29e63087497c554fa74df2c9"
}