BTC-e Data Leak - Revision history

Azoundria at 19:16, 14 March 2025

2025-03-14T19:16:37Z

← Older revision		Revision as of 13:16, 14 March 2025
Line 58:		Line 58:
	\|		\|
	\|}		\|}

			== Technical Details ==
			This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

	== Total Amount Lost ==		== Total Amount Lost ==
Line 93:		Line 96:

	== References ==		== References ==
	<references><ref name="youtube-6145">[https://www.youtube.com/watch?v=qd6kBbpQ22Y Ledger Hack: Who is Ledger? What Happened? Does the Ledger data breach affect everyone? - YouTube] (Jan 31, 2022)</ref>		<references><ref name="youtube-6145">[https://www.youtube.com/watch?v=qd6kBbpQ22Y Ledger Hack: Who is Ledger? What Happened? Does the Ledger data breach affect everyone? - YouTube] (Accessed Jan 31, 2022)</ref>

	<ref name="ccn-6817">[https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/ https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/] (Mar 4, 2022)</ref>		<ref name="ccn-6817">[https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/ https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/] (Accessed Mar 4, 2022)</ref>

	<ref name="databreaches-6818">[https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/ https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/] (Mar 4, 2022)</ref>		<ref name="databreaches-6818">[https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/ https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/] (Accessed Mar 4, 2022)</ref>

	<ref name="wikipedia-4420">[https://en.wikipedia.org/wiki/BTC-e BTC-e - Wikipedia] (Dec 12, 2021)</ref>		<ref name="wikipedia-4420">[https://en.wikipedia.org/wiki/BTC-e BTC-e - Wikipedia] (Accessed Dec 12, 2021)</ref>

	<ref name="btcearchive-6819">[https://web.archive.org/web/20160223095410/https://btc-e.com/ BTC-E \| Bitcoin Exchange, Namecoin Exchange, Litecoin Exchange, BTC Exchange] (Mar 4, 2022)</ref>		<ref name="btcearchive-6819">[https://web.archive.org/web/20160223095410/https://btc-e.com/ BTC-E \| Bitcoin Exchange, Namecoin Exchange, Litecoin Exchange, BTC Exchange] (Accessed Mar 4, 2022)</ref>

	<ref name="newsbtc-6820">[https://www.newsbtc.com/news/leakedsource-publishes-update-btc-e-bitcointalk-hacking-incidents/ Update on BTC-E and BitcoinTalk Hacking Incidents] (Mar 4, 2022)</ref>		<ref name="newsbtc-6820">[https://www.newsbtc.com/news/leakedsource-publishes-update-btc-e-bitcointalk-hacking-incidents/ Update on BTC-E and BitcoinTalk Hacking Incidents] (Accessed Mar 4, 2022)</ref>

	<ref name="leakedsourcearchive-6929">[https://web.archive.org/web/20161208010408/https://www.leakedsource.com/blog/bitcointalkbtce LeakedSource disclosure of Bitcointalk.org and Btc-e.com Hack] (Mar 8, 2022)</ref></references>		<ref name="leakedsourcearchive-6929">[https://web.archive.org/web/20161208010408/https://www.leakedsource.com/blog/bitcointalkbtce LeakedSource disclosure of Bitcointalk.org and Btc-e.com Hack] (Accessed Mar 8, 2022)</ref></references>

Azoundria at 23:57, 12 April 2023

2023-04-12T23:57:48Z

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

	[[File:Btce.jpg\|thumb\|BTC-e]]The BTC-e platform was breached in October 2014. Data on 568,355 users was breached, although since passwords were hashed efficiently, only usernames, email addresses, IP addresses, dates of registration, and language settings were captured.		[[File:Btce.jpg\|thumb\|BTC-e]]The BTC-e platform was breached in October 2014. Data on 568,355 users was breached, although since passwords were hashed efficiently, only usernames, email addresses, IP addresses, dates of registration, and language settings were captured.

	This exchange or platform is based in Russia, or the incident targeted people primarily in Russia.		This exchange or platform is based in Russia, or the incident targeted people primarily in Russia.<ref name="youtube-6145" /><ref name="ccn-6817" /><ref name="databreaches-6818" /><ref name="wikipedia-4420" /><ref name="btcearchive-6819" /><ref name="newsbtc-6820" /><ref name="leakedsourcearchive-6929" />
	<ref name="youtube-6145" /><ref name="ccn-6817" /><ref name="databreaches-6818" /><ref name="wikipedia-4420" /><ref name="btcearchive-6819" /><ref name="newsbtc-6820" /><ref name="leakedsourcearchive-6929" />

	== About BTC-e ==		== About BTC-e ==
Line 51:		Line 50:
	!Description		!Description
	\|-		\|-
	\|October 15th, 2014 ~~12:00:00 AM~~		\|October 15th, 2014
	\|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 78:		Line 77:
	== 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?
			== Individual Prevention Policies ==
			{{Prevention:Individuals:Placeholder}}

			{{Prevention:Individuals:End}}

			== Platform Prevention Policies ==
			{{Prevention:Platforms:Placeholder}}

			{{Prevention:Platforms:End}}

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

	== Prevention ~~Policies ==~~		{{Prevention:Regulators:End}}
	~~Which policies could have prevented this event from happening?~~

	== References ==		== References ==

Azoundria at 00:50, 16 February 2023

2023-02-16T00:50:38Z

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

	[[File:Btce.jpg\|thumb\|BTC-e]]The BTC-e platform was breached in October 2014. Data on 568,355 users was breached, although since passwords were hashed efficiently, only usernames, email addresses, IP addresses, dates of registration, and language settings were captured.		[[File:Btce.jpg\|thumb\|BTC-e]]The BTC-e platform was breached in October 2014. Data on 568,355 users was breached, although since passwords were hashed efficiently, only usernames, email addresses, IP addresses, dates of registration, and language settings were captured.

	This exchange or platform is based in Russia, or the incident targeted people primarily in Russia.		This exchange or platform is based in Russia, or the incident targeted people primarily in Russia.
			<ref name="youtube-6145" /><ref name="ccn-6817" /><ref name="databreaches-6818" /><ref name="wikipedia-4420" /><ref name="btcearchive-6819" /><ref name="newsbtc-6820" /><ref name="leakedsourcearchive-6929" />

	== About BTC-e ==		== About BTC-e ==
Line 29:		Line 31:

	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 51:		Line 52:
	\|-		\|-
	\|October 15th, 2014 12:00:00 AM		\|October 15th, 2014 12:00:00 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 64:		Line 61:

	== Total Amount Lost ==		== Total Amount Lost ==
	~~The total amount~~ lost ~~is unknown~~.		No funds were lost.

	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 75:		Line 72:

	== Total Amount Recovered ==		== Total Amount Recovered ==
	~~It is unknown how much was~~ recovered.		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?
Line 83:		Line 80:

	== Prevention Policies ==		== Prevention Policies ==
			Which policies could have prevented this event from happening?

	== References ==		== References ==
	[https://www.youtube.com/watch?v=qd6kBbpQ22Y Ledger Hack: Who is Ledger? What Happened? Does the Ledger data breach affect everyone? - YouTube] (Jan 31)		<references><ref name="youtube-6145">[https://www.youtube.com/watch?v=qd6kBbpQ22Y Ledger Hack: Who is Ledger? What Happened? Does the Ledger data breach affect everyone? - YouTube] (Jan 31, 2022)</ref>

	[https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/ https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/] (Mar 4)		<ref name="ccn-6817">[https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/ https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/] (Mar 4, 2022)</ref>

	[https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/ https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/] (Mar 4)		<ref name="databreaches-6818">[https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/ https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/] (Mar 4, 2022)</ref>

	[https://en.wikipedia.org/wiki/BTC-e BTC-e - Wikipedia] (Dec 12)		<ref name="wikipedia-4420">[https://en.wikipedia.org/wiki/BTC-e BTC-e - Wikipedia] (Dec 12, 2021)</ref>

	[https://web.archive.org/web/20160223095410/https://btc-e.com/ BTC-E \| Bitcoin Exchange, Namecoin Exchange, Litecoin Exchange, BTC Exchange] (Mar 4)		<ref name="btcearchive-6819">[https://web.archive.org/web/20160223095410/https://btc-e.com/ BTC-E \| Bitcoin Exchange, Namecoin Exchange, Litecoin Exchange, BTC Exchange] (Mar 4, 2022)</ref>

	[https://www.newsbtc.com/news/leakedsource-publishes-update-btc-e-bitcointalk-hacking-incidents/ Update on BTC-E and BitcoinTalk Hacking Incidents] (Mar 4)		<ref name="newsbtc-6820">[https://www.newsbtc.com/news/leakedsource-publishes-update-btc-e-bitcointalk-hacking-incidents/ Update on BTC-E and BitcoinTalk Hacking Incidents] (Mar 4, 2022)</ref>

	[https://web.archive.org/web/20161208010408/https://www.leakedsource.com/blog/bitcointalkbtce LeakedSource disclosure of Bitcointalk.org and Btc-e.com Hack] (Mar 8)		<ref name="leakedsourcearchive-6929">[https://web.archive.org/web/20161208010408/https://www.leakedsource.com/blog/bitcointalkbtce LeakedSource disclosure of Bitcointalk.org and Btc-e.com Hack] (Mar 8, 2022)</ref></references>

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/btcedataleak.php}} BTC-eThe BTC-e platform was breached in October 2014. Data on 568,355 users was breached, although since passwords were hashed efficiently, only usernames, email addresses, IP addresses, dates of registration, and language settings were captured. This exchange or platform is based in Russia, or the incident targeted people primarily in Russia. == About..."

2023-01-24T20:29:37Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/btcedataleak.php}} thumb|BTC-eThe BTC-e platform was breached in October 2014. Data on 568,355 users was breached, although since passwords were hashed efficiently, only usernames, email addresses, IP addresses, dates of registration, and language settings were captured. This exchange or platform is based in Russia, or the incident targeted people primarily in Russia. == About..."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/btcedataleak.php}}

[[File:Btce.jpg|thumb|BTC-e]]The BTC-e platform was breached in October 2014. Data on 568,355 users was breached, although since passwords were hashed efficiently, only usernames, email addresses, IP addresses, dates of registration, and language settings were captured.

This exchange or platform is based in Russia, or the incident targeted people primarily in Russia.

== About BTC-e ==
"BTC-e was a cryptocurrency trading platform founded in July 2011 by Alexander Vinnik and Aleksandr Bilyuchenko". "BTC-e was established in July 2011, handling a few coin pairs, including Bitcoin/U. S. dollar and I0Coin to Bitcoin. By October 2011, they supported many different currency pairs, including Litecoin to dollars, Bitcoin to rubles and RuCoin to rubles." "It was a component of the CoinDesk Bitcoin Price Index since the index's September 2013 formation."

"A stolen data set containing user information from BTC-E from October 2014 revealed a total of 568,355 users registered with the exchange."

"The breached data contained all manners of user details including usernames, email addresses, passwords, IP addresses, dates of registration, and the user’s preferred language. Somewhat alarmingly, some profile details even revealed the number of bitcoins owned by the user."

"However, BTC-E used a discreet and a unique password hashing method to secure user passwords, a method unknown even to LeakedSource. Currently, every single password of over half a million BTC-E users remains “completely uncrackable, although that may change”, according to LeakedSource."

This exchange or platform is based in Russia, or the incident targeted people primarily in Russia.

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 - BTC-e Data Leak
!Date
!Event
!Description
|-
|October 15th, 2014 12:00:00 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 ==
The total amount lost is unknown.

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 ==
It is unknown how much was 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 ==

== References ==
[https://www.youtube.com/watch?v=qd6kBbpQ22Y Ledger Hack: Who is Ledger? What Happened? Does the Ledger data breach affect everyone? - YouTube] (Jan 31)

[https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/ https://www.ccn.com/bitcoin-exchange-btc-e-bitcointalk-forum-breaches-details-revealed/] (Mar 4)

[https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/ https://www.databreaches.net/bitcoin-exchange-btc-e-and-bitcointalk-forum-breaches/] (Mar 4)

[https://en.wikipedia.org/wiki/BTC-e BTC-e - Wikipedia] (Dec 12)

[https://web.archive.org/web/20160223095410/https://btc-e.com/ BTC-E | Bitcoin Exchange, Namecoin Exchange, Litecoin Exchange, BTC Exchange] (Mar 4)

[https://www.newsbtc.com/news/leakedsource-publishes-update-btc-e-bitcointalk-hacking-incidents/ Update on BTC-E and BitcoinTalk Hacking Incidents] (Mar 4)

[https://web.archive.org/web/20161208010408/https://www.leakedsource.com/blog/bitcointalkbtce LeakedSource disclosure of Bitcointalk.org and Btc-e.com Hack] (Mar 8)