Bitomat Exchange Wallet.dat File Deleted: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/bitomatexchangewalletdatfiledeleted.php}} | |||
In addition to protecting against unauthorized access, it’s important to build in redundancy. Using multi-sig with at least one additional spare signature means that any single loss of signature is unable to bring down the wallet. | |||
This exchange or platform is based in Poland, or the incident targeted people primarily in Poland. | |||
== About Bitomat == | |||
“During a server restart, the remote Amazon service that housed Bitomat.pl’s wallet was wiped. No backups were kept, and Mt. Gox later bailed out Bitomat.pl. Ultimately, neither the exchange’s customers nor the original owners suffered any loss from the incident.” | |||
This exchange or platform is based in Poland, or the incident targeted people primarily in Poland. | |||
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events. | The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events. | ||
| Line 31: | Line 39: | ||
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it. | The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it. | ||
{| class="wikitable" | {| class="wikitable" | ||
|+Key Event Timeline - | |+Key Event Timeline - Bitomat Exchange Wallet.dat File Deleted | ||
!Date | !Date | ||
!Event | !Event | ||
!Description | !Description | ||
|- | |- | ||
| | |July 1st, 2011 12:00:03 AM | ||
|First Event | |First Event | ||
|This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here. | |This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here. | ||
| Line 50: | Line 58: | ||
== Total Amount Lost == | == Total Amount Lost == | ||
$220 000 USD | |||
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie? | How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie? | ||
| Line 59: | Line 68: | ||
== Total Amount Recovered == | == Total Amount Recovered == | ||
$0 USD | |||
What funds were recovered? What funds were reimbursed for those affected users? | What funds were recovered? What funds were reimbursed for those affected users? | ||
| Line 65: | Line 75: | ||
== Prevention Policies == | == Prevention Policies == | ||
The use of multi-signature technology provides redundancy, and all operators should have training in how to safely store and manage private keys. | |||
== References == | == References == | ||
A | [https://bitcoinmagazine.com/articles/infographic-overview-compromised-bitcoin-exchange-events Infographic: An Overview of Compromised Bitcoin Exchange Events] (Jan 29) | ||
[https://bitcointalk.org/index.php?topic=83794.msg923918#msg923918 <nowiki>List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses [Old]</nowiki>] (Jan 27) | |||
[https://medium.com/@kylegibson/100-crypto-thefts-a-timeline-of-hacks-glitches-exit-scams-and-other-lost-cryptocurrency-873c87fd5522 100 Crypto Thefts: A Timeline of Hacks, Glitches, Exit Scams, and other Lost Cryptocurrency Incidents] (Jan 24) | |||
[https://bitcointalk.org/index.php?topic=576337 List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses] (Feb 14) | |||
[https://bitcoinexchangeguide.com/bitcoin/scams-hacks/ Bitcoin Scams and Cryptocurrency Hacks List - BitcoinExchangeGuide.com] (Mar 4) | |||
Revision as of 13:13, 20 January 2023
Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' section to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.
In addition to protecting against unauthorized access, it’s important to build in redundancy. Using multi-sig with at least one additional spare signature means that any single loss of signature is unable to bring down the wallet.
This exchange or platform is based in Poland, or the incident targeted people primarily in Poland.
About Bitomat
“During a server restart, the remote Amazon service that housed Bitomat.pl’s wallet was wiped. No backups were kept, and Mt. Gox later bailed out Bitomat.pl. Ultimately, neither the exchange’s customers nor the original owners suffered any loss from the incident.”
This exchange or platform is based in Poland, or the incident targeted people primarily in Poland.
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.
Include:
- Known history of when and how the service was started.
- What problems does the company or service claim to solve?
- What marketing materials were used by the firm or business?
- Audits performed, and excerpts that may have been included.
- Business registration documents shown (fake or legitimate).
- How were people recruited to participate?
- Public warnings and announcements prior to the event.
Don't Include:
- Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
- Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.
The Reality
This sections is included if a case involved deception or information that was unknown at the time. Examples include:
- When the service was actually started (if different than the "official story").
- Who actually ran a service and their own personal history.
- How the service was structured behind the scenes. (For example, there was no "trading bot".)
- Details of what audits reported and how vulnerabilities were missed during auditing.
What Happened
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
| Date | Event | Description |
|---|---|---|
| July 1st, 2011 12:00:03 AM | First Event | This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here. |
Total Amount Lost
$220 000 USD How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?
Immediate Reactions
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?
Ultimate Outcome
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?
Total Amount Recovered
$0 USD What funds were recovered? What funds were reimbursed for those affected users?
Ongoing Developments
What parts of this case are still remaining to be concluded?
Prevention Policies
The use of multi-signature technology provides redundancy, and all operators should have training in how to safely store and manage private keys.
References
Infographic: An Overview of Compromised Bitcoin Exchange Events (Jan 29)
List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses [Old] (Jan 27)
List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses (Feb 14)
Bitcoin Scams and Cryptocurrency Hacks List - BitcoinExchangeGuide.com (Mar 4)