Trezor Data Breach Phishing: Revision history

15 September 2023

• curprev 13:3213:32, 15 September 2023‎ Azoundria talk contribs‎ 14,535 bytes −37,505‎ No edit summary

19 July 2023

• curprev 15:0015:00, 19 July 2023‎ Azoundria talk contribs‎ 52,040 bytes +4,402‎ Another 30 minutes complete. Integrated information about MrChaBuDuo. Tag: Visual edit

7 July 2023

• curprev 11:0811:08, 7 July 2023‎ Azoundria talk contribs‎ 47,638 bytes +3,094‎ Another 30 minutes complete. All open tabs integrated into the case. Prevention fully up to date. Tag: Visual edit

5 July 2023

• curprev 14:1114:11, 5 July 2023‎ Azoundria talk contribs‎ 44,544 bytes +4,350‎ Another 30 minutes complete. Tag: Visual edit

4 July 2023

• curprev 15:5615:56, 4 July 2023‎ Azoundria talk contribs‎ 40,194 bytes +4,864‎ Another 30 minutes complete. Tag: Visual edit

28 June 2023

• curprev 14:0314:03, 28 June 2023‎ Azoundria talk contribs‎ 35,330 bytes +10,061‎ Another 30 minutes complete. Tag: Visual edit

27 June 2023

• curprev 10:4010:40, 27 June 2023‎ Azoundria talk contribs‎ 25,269 bytes +4,512‎ Another 30 minutes complete. Tag: Visual edit

21 June 2023

• curprev 11:1511:15, 21 June 2023‎ Azoundria talk contribs‎ 20,757 bytes +4,109‎ Another 30 minutes complete. Tag: Visual edit

18 April 2023

• curprev 21:5221:52, 18 April 2023‎ Azoundria talk contribs‎ 16,648 bytes +2,649‎ Initial 30 minutes sent. Down to 4 sources left. Tag: Visual edit

12 April 2023

• curprev 10:1010:10, 12 April 2023‎ Azoundria talk contribs‎ 13,999 bytes +1,373‎ No edit summary

28 January 2023

• curprev 21:3421:34, 28 January 2023‎ Azoundria talk contribs‎ 12,626 bytes +12,626‎ Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/trezordatabreachphishing.php}} thumb|TrezorMultiple users of the Trezor hardware wallet had their email addresses compromised, and the phishing attacker sent out a realistic, typo-free, and well planned attack complete with an altered version of the application, which requested their seed phrase. While the total value of the loss hasn't been publicized, at least one user was fo..."