BitcoinTalk Database Breach: Revision history

Jump to navigation Jump to search

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

13 September 2024

15 May 2024

  • curprev 15:0315:03, 15 May 2024Azoundria talk contribs 18,711 bytes +3,159 COMPLETE 30 minutes. Full review and modification of the wiki article. Tons of sections have been filled in. Added information about earlier 2013 hack as a new case. Added detailed timeline information. Improved the immediate reactions and technical details with additional information. Tag: Visual edit

14 May 2024

  • curprev 16:3016:30, 14 May 2024Azoundria talk contribs 15,552 bytes +2,464 COMPLETE 30 minutes. Improving the summary introduction. Added a Prevention section with proposed prevention plan (may be improved later). Integrated information from a BitcoinTalk thread about the hack to help fill in the Ongoing Developments section. CCN news article with information from LeakedSource integrated. Added additional clarification to the amount lost and amount recovered sections. Completed a review of the changes to the CCN article with LeakedSource information. Added a couple sou Tag: Visual edit

2 April 2024

  • curprev 16:4016:40, 2 April 2024Azoundria talk contribs 13,088 bytes +2,607 Information in the about section spread out into other sections of the article. Added information from the articles by CCN and DataBreaches.net. DataBreaches.net replaced with archived version. Updated source titles of various sources. Tag: Visual edit

12 April 2023

15 February 2023

24 January 2023

  • curprev 14:4514:45, 24 January 2023Azoundria talk contribs 9,198 bytes +9,198 Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/bitcointalkdatabasebreach.php}} thumb|BitcoinTalkBitcoinTalk is one of the largest and oldest forums on the internet related to bitcoin. In May 2015, the server was compromised through a social engineering attack on the sites ISP (internet service provider). In the apparent 12 minutes that the attackers had access, they managed to pull the entire database of all 499,593 us..."