Bitomat Exchange Wallet.dat File Deleted - Revision history

Azoundria at 21:30, 13 September 2024

2024-09-13T21:30:43Z

Azoundria at 16:13, 12 April 2023

2023-04-12T16:13:33Z

← Older revision		Revision as of 10:13, 12 April 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/bitomatexchangewalletdatfiledeleted.php}}		{{Imported Case Study 2\|source=https://www.quadrigainitiative.com/casestudy/bitomatexchangewalletdatfiledeleted.php}}
	{{Unattributed ~~Citations~~}}		{{Unattributed Sources}}

	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.		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.		This exchange or platform is based in Poland, or the incident targeted people primarily in Poland.<ref name="bitcoinmagazine-6" /><ref name="bitcointalklistold-19" /><ref name="kylegibson-86" /><ref name="bitcointalklist-87" /><ref name="bitcoinexchangeguide-218" />
	<ref name="bitcoinmagazine-6" /><ref name="bitcointalklistold-19" /><ref name="kylegibson-86" /><ref name="bitcointalklist-87" /><ref name="bitcoinexchangeguide-218" />

	== About Bitomat ==		== About Bitomat ==
Line 45:		Line 44:
	!Description		!Description
	\|-		\|-
	\|July 1st, 2011 12:00:03 AM		\|July 1st, 2011 12:00:03 AM MDT
	\|Main Event		\|Main Event
	\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
Line 72:		Line 71:
	== Ongoing Developments ==		== Ongoing Developments ==
	What parts of this case are still remaining to be concluded?		What parts of this case are still remaining to be concluded?
			== General 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.
			== Individual Prevention Policies ==
			{{Prevention:Individuals:Placeholder}}

			{{Prevention:Individuals:End}}

	== Prevention Policies ==		== Platform 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.~~		{{Prevention:Platforms:Placeholder}}

			{{Prevention:Platforms:End}}

			== Regulatory Prevention Policies ==
			{{Prevention:Regulators:Placeholder}}

			{{Prevention:Regulators:End}}

	== References ==		== References ==
	<references><ref name="bitcoinmagazine-6">[https://bitcoinmagazine.com/articles/infographic-overview-compromised-bitcoin-exchange-events Infographic: An Overview of Compromised Bitcoin Exchange Events] (Jan 29, 2020)</ref>		<references><ref name="bitcoinmagazine-6">[https://bitcoinmagazine.com/articles/infographic-overview-compromised-bitcoin-exchange-events Infographic: An Overview of Compromised Bitcoin Exchange Events] (Jan 30, 2020)</ref>

	<ref name="bitcointalklistold-19">[https://bitcointalk.org/index.php?topic=83794.msg923918#msg923918 <nowiki>List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses [Old]</nowiki>] (Jan 28, 2020)</ref>		<ref name="bitcointalklistold-19">[https://bitcointalk.org/index.php?topic=83794.msg923918#msg923918 <nowiki>List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses [Old]</nowiki>] (Jan 28, 2020)</ref>

Azoundria at 23:54, 18 February 2023

2023-02-18T23:54:06Z

← Older revision		Revision as of 17:54, 18 February 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/bitomatexchangewalletdatfiledeleted.php}}		{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/bitomatexchangewalletdatfiledeleted.php}}
			{{Unattributed Citations}}

	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.		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.		This exchange or platform is based in Poland, or the incident targeted people primarily in Poland.
			<ref name="bitcoinmagazine-6" /><ref name="bitcointalklistold-19" /><ref name="kylegibson-86" /><ref name="bitcointalklist-87" /><ref name="bitcoinexchangeguide-218" />

	== About Bitomat ==		== About Bitomat ==
Line 75:		Line 77:

	== References ==		== References ==
	[https://bitcoinmagazine.com/articles/infographic-overview-compromised-bitcoin-exchange-events Infographic: An Overview of Compromised Bitcoin Exchange Events] (Jan 29)		<references><ref name="bitcoinmagazine-6">[https://bitcoinmagazine.com/articles/infographic-overview-compromised-bitcoin-exchange-events Infographic: An Overview of Compromised Bitcoin Exchange Events] (Jan 29, 2020)</ref>

	[https://bitcointalk.org/index.php?topic=83794.msg923918#msg923918 <nowiki>List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses [Old]</nowiki>] (Jan 27)		<ref name="bitcointalklistold-19">[https://bitcointalk.org/index.php?topic=83794.msg923918#msg923918 <nowiki>List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses [Old]</nowiki>] (Jan 28, 2020)</ref>

	[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)		<ref name="kylegibson-86">[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 25, 2020)</ref>

	[https://bitcointalk.org/index.php?topic=576337 List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses] (Feb 14)		<ref name="bitcointalklist-87">[https://bitcointalk.org/index.php?topic=576337 List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses] (Feb 15, 2020)</ref>

	[https://bitcoinexchangeguide.com/bitcoin/scams-hacks/ Bitcoin Scams and Cryptocurrency Hacks List - BitcoinExchangeGuide.com] (Mar 4)		<ref name="bitcoinexchangeguide-218">[https://bitcoinexchangeguide.com/bitcoin/scams-hacks/ Bitcoin Scams and Cryptocurrency Hacks List - BitcoinExchangeGuide.com] (Mar 5, 2020)</ref></references>

Azoundria at 17:01, 29 January 2023

2023-01-29T17:01:00Z

← Older revision		Revision as of 11:01, 29 January 2023
Line 23:		Line 23:

	Don't Include:		Don't Include:

	* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.		* 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.		* Anything that wasn't reasonably knowable at the time of the event.
Line 45:		Line 44:
	\|-		\|-
	\|July 1st, 2011 12:00:03 AM		\|July 1st, 2011 12:00:03 AM
	\|~~First~~ Event		\|Main Event
	\|~~This is an expanded~~ description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
	\|-
	\|
	\|
	\|
	\|-		\|-
	\|		\|
Line 58:		Line 53:

	== Total Amount Lost ==		== Total Amount Lost ==
	$220 000 USD		The total amount lost has been estimated at $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 68:		Line 64:

	== Total Amount Recovered ==		== Total Amount Recovered ==
	~~$0 USD~~		There do not appear to have been any funds recovered in this case.

	What funds were recovered? What funds were reimbursed for those affected users?		What funds were recovered? What funds were reimbursed for those affected users?

Azoundria at 19:13, 20 January 2023

2023-01-20T19:13:16Z

← Older revision		Revision as of 13:13, 20 January 2023
Line 1:		Line 1:
	~~New cases added need~~ to ~~comply~~ with the ~~[[Criteria for Case Inclusion]]~~. ~~A high level overview of all~~ the ~~most relevant facts~~ and ~~information~~ in the ~~case would be included here~~. ~~Case studies would then generally comprise of the following primary sections:~~		{{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.

	~~== About [Service] ==~~
	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 - ~~[Case Name]~~		\|+Key Event Timeline - Bitomat Exchange Wallet.dat File Deleted
	!Date		!Date
	!Event		!Event
	!Description		!Description
	\|-		\|-
	\|~~January 14th~~, ~~2023 8~~:16 AM		\|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 ==
	~~Which policies could~~ have ~~prevented this event from happening?~~		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 ~~section with the references where information came from~~.		[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)

Azoundria at 19:52, 17 January 2023

2023-01-17T19:52:50Z

← Older revision		Revision as of 13:52, 17 January 2023
Line 1:		Line 1:
	.		New cases added need to comply with the [[Criteria for Case Inclusion]]. A high level overview of all the most relevant facts and information in the case would be included here. Case studies would then generally comprise of the following primary sections:

			== About [Service] ==
			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.
			{\| class="wikitable"
			\|+Key Event Timeline - [Case Name]
			!Date
			!Event
			!Description
			\|-
			\|January 14th, 2023 8:16 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 ==
			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 ==
			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 ==
			Which policies could have prevented this event from happening?

			== References ==
			A section with the references where information came from.

Azoundria: Created page with "."

2023-01-17T19:52:31Z

Created page with "."

New page