CryptoRush Hack - Revision history

Azoundria: Another 30 minutes. Filling in more information tracing the original hacks and events happening around BlackCoin. Found and added video. Found and attempted to access technical analysis article. Promotion on Twitter.

2024-03-13T18:58:30Z

Another 30 minutes. Filling in more information tracing the original hacks and events happening around BlackCoin. Found and added video. Found and attempted to access technical analysis article. Promotion on Twitter.

← Older revision		Revision as of 12:58, 13 March 2024
Line 17:		Line 17:
	=== DogeyMcDoge ===		=== DogeyMcDoge ===
	One member of the CryptoRush support team goes by the nickname DogeyMcDoge<ref name=":4">[https://web.archive.org/web/20190624173646/https://pastebin.com/eLkPxLWi DogeyMcDoge Pastebin Archive June 24th, 2019 11:36:46 AM MDT] (Accessed Mar 7, 2024)</ref>. They started to work for CryptoRush in late February of 2014<ref name=":4">[https://web.archive.org/web/20190624173646/https://pastebin.com/eLkPxLWi DogeyMcDoge Pastebin Archive June 24th, 2019 11:36:46 AM MDT] (Accessed Mar 7, 2024)</ref>.		One member of the CryptoRush support team goes by the nickname DogeyMcDoge<ref name=":4">[https://web.archive.org/web/20190624173646/https://pastebin.com/eLkPxLWi DogeyMcDoge Pastebin Archive June 24th, 2019 11:36:46 AM MDT] (Accessed Mar 7, 2024)</ref>. They started to work for CryptoRush in late February of 2014<ref name=":4">[https://web.archive.org/web/20190624173646/https://pastebin.com/eLkPxLWi DogeyMcDoge Pastebin Archive June 24th, 2019 11:36:46 AM MDT] (Accessed Mar 7, 2024)</ref>.

			BitcoinTalk:<ref>https://bitcointalk.org/index.php?action=profile;u=224348</ref><ref>https://bitcointalk.org/index.php?action=profile;u=180394</ref>

	== The Reality ==		== The Reality ==
	Using any third party platform involves a high degree of risk. ~~Signs~~ of limited experience were visible from the FAQ page of CryptoRush.in itself<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>.		Using any third party platform involves a high degree of risk. In this case, there was a critical vulnerability in the BlackCoin client where each user was given a daemon account and the balance was calculated incorrectly<ref name=":8" />. Additional signs of limited experience were visible from the FAQ page of CryptoRush.in itself<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>.

	=== Negative Balance Concern ===		=== Negative Balance Concern ===
Line 31:		Line 33:

	=== Each Coin Adds Attack Surface ===		=== Each Coin Adds Attack Surface ===
	Every coin supported increases the attack surface against a platform, since an issue in one coin could inflate the user's balance and allow them to trade against other coins.		A big part of CryptoRush was the support for a wide range of coins<ref name=":1" />. Every coin supported increases the attack surface against a platform, since an issue in one coin could inflate the user's balance and allow them to trade against other coins.

	== What Happened ==		== What Happened ==
Line 52:		Line 54:
	\|Emergency Call		\|Emergency Call
	\|DogeyMcDoge reportedly calls Devianttwo on the emergency phone number and is told that he wasn't going to be able to fix the problems at the moment<ref name=":4" />.		\|DogeyMcDoge reportedly calls Devianttwo on the emergency phone number and is told that he wasn't going to be able to fix the problems at the moment<ref name=":4" />.
			\|-
			\|March 25th, 2014 3:58:02 AM MDT
			\|Chat Log Uploaded To PasteBin
			\|A chat log of the discussion with BlackCoin developer rat4 is shared to PasteBin<ref name=":8" />.
			\|-
			\|March 25th, 2014 11:21:03 PM MDT
			\|Information Leak To PasteBin
			\|The information leak is uploaded to PasteBin<ref name=":4" />.
	\|-		\|-
	\|March 26th, 2014 5:02:01 AM MDT		\|March 26th, 2014 5:02:01 AM MDT
Line 59:		Line 69:
	\|April 1st, 2014 10:17:48 AM MDT		\|April 1st, 2014 10:17:48 AM MDT
	\|Death Thread On BitcoinTalk		\|Death Thread On BitcoinTalk
	\|BitcoinTalk forum discussion about the "death" of ~~cryptorush~~<ref>[https://bitcointalk.org/index.php?topic=553041.0 Death Of Cryptorush.in - BitcoinTalk] (Accessed Mar 12, 2024)</ref>.		\|BitcoinTalk forum discussion about the "death" of the CryptoRush platform<ref>[https://bitcointalk.org/index.php?topic=553041.0 Death Of Cryptorush.in - BitcoinTalk] (Accessed Mar 12, 2024)</ref>.
			\|-
			\|October 16th, 2014 4:59:44 PM MDT
			\|YouTube Video On Relaunch
			\|Adrian Crenshaw posts a video about relaunching CryptoRush with many details of the attack included<ref>[https://www.youtube.com/watch?v=0K9xK5t9ckc v04 CryptoRush a Rising from the Ashes King Dragon - YouTube] (Accessed Mar 13, 2024)</ref>.
	\|-		\|-
	\|November 11th, 2020 8:32:40 PM MST		\|November 11th, 2020 8:32:40 PM MST
Line 75:		Line 89:

	== Technical Details ==		== Technical Details ==
			The primary issue involved the implementation of the BlackCoin client on the platform<ref name=":8">[https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL PasteBin Chat Log Archive June 24th, 2019 11:35:14 AM MDT] (Accessed Feb 27, 2024)</ref>.

			[https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN]

	~~<ref>[https~~:~~//web~~.~~archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL PasteBin Chat Log Archive June 24th, 2019 11:35:14 AM MDT] (Accessed Feb 27, 2024)</ref>~~		Timezones: Linkandzelda 8 AM = Devianttwo 4 AM = Server 3 AM.

	[https://~~www~~.~~ccn~~.~~com~~/~~cryptorush~~-~~support~~-~~worker~~-~~leaks~~-~~inside~~-~~info~~ CryptoRush ~~support worker leaks inside info~~ - ~~CCN]~~		BitComSec shared a technical analysis tracing the flow of the funds, however this was never captured by ther Internet Archive due to dynamic JavaScript on the website<ref>[https://web.archive.org/web/20141024095104/https://bitcomsec.true.io/bitcomsec/tracking-a-bitcoin-thief-cryptorush-hack/ Tracking A Bitcoin Theft CryptoRush Hack Archive October 24th, 2014 3:51:04 AM MDT] (Accessed Mar 13, 2024)</ref> and their website is presently offline<ref>[https://bitcomsec.true.io/ BitComSec Homepage] (Accessed Mar 13, 2024)</ref>. <ref>https://bitcointalk.org/index.php?topic=2588973.0 </ref><ref>https://twitter.com/bitcomsec</ref><ref>https://www.reddit.com/r/Bitcoin/comments/2k1t3w/bitcomsec_tracking_a_bitcoin_thief_pt_i_the/</ref><ref>https://www.facebook.com/ElPasoDevelopers</ref><ref>https://yro.slashdot.org/story/14/10/23/2216201/tracking-a-bitcoin-thief</ref>

	== Total Amount Lost ==		== Total Amount Lost ==
Line 96:		Line 112:

	=== Inclusion/Recognition On Lists ===		=== Inclusion/Recognition On Lists ===
	The issue was featured on several lists including Kyle Gibson<ref name="kylegibson-86" />, and the Idex Blog<ref name="idexblog-7454" />.		The issue was featured on several lists including Kyle Gibson<ref name="kylegibson-86" />, CryptoXDirectory<ref>[https://cryptoxdirectory.com/cryptorush CryptoRush - CryptoXDirectory] (Accessed Mar 13, 2024)</ref>, and the Idex Blog<ref name="idexblog-7454" />.

	== Total Amount Recovered ==		== Total Amount Recovered ==

Azoundria: Another 30 minutes. Completed prevention section. Integrating information from the chat log and BitcoinTalk discussion threads. Minor tweaks to the article wording to improve readability.

2024-03-12T16:57:24Z

Another 30 minutes. Completed prevention section. Integrating information from the chat log and BitcoinTalk discussion threads. Minor tweaks to the article wording to improve readability.

← Older revision		Revision as of 10:57, 12 March 2024
Line 1:		Line 1:
	{{Case Study Under Construction}}{{Unattributed Sources}}[[File:Cryptorush.jpg\|thumb\|CryptoRush Logo/Homepage]]		{{Case Study Under Construction}}{{Unattributed Sources}}[[File:Cryptorush.jpg\|thumb\|CryptoRush Logo/Homepage]]

	The primary issue here appears to be numerous exploits in the various alt coin withdrawal processes which CryptoRush handled through hot wallets. This seems to be based on the service being ~~quickly~~ coded in a few ~~short~~ months.		The primary issue here appears to be numerous exploits in the various alt coin withdrawal processes which CryptoRush handled through hot wallets. This seems to be based on the service being coded in a "rush", with development of only a few months.

	This exchange or platform is based in United States, or the incident targeted people primarily in United States.<ref name="kylegibson-86" /><ref name="bitcointalklist-87" /><ref name="bitcoinexchangeguide-218" /><ref name="idexblog-7454" /><ref name="cointelegraph-7455" />		This exchange or platform is based in United States, or the incident targeted people primarily in United States.<ref name="kylegibson-86" /><ref name="bitcointalklist-87" /><ref name="bitcoinexchangeguide-218" /><ref name="idexblog-7454" /><ref name="cointelegraph-7455" />

	== About CryptoRush ==		== About CryptoRush ==
	While CryptoRush used a .in extension<ref name=":1">[https://web.archive.org/web/20140317110538/https://www.cryptorush.in/ CryptoRush Homepage Archive March 17th, 2014 5:05:38 AM MDT] (Accessed Mar 1, 2024)</ref> which is the country code of India, the exchange was actually based in the United States. CryptoRush appears to favour small alternate currencies, and was aiming to be a top cryptocurrency exchange<ref name=":2">[https://web.archive.org/web/20140302065608/https://cryptorush.in/index.php?p=about About CryptoRush Archive March 1st, 2014 11:56:08 PM MST] (Accessed Mar 1, 2024)</ref>. ~~The founder was reportedly named~~ Kristian, while the other team members were reportedly named Matt and Chris, and they reportedly joined after beta<ref name=":2">[https://web.archive.org/web/20140302065608/https://cryptorush.in/index.php?p=about About CryptoRush Archive March 1st, 2014 11:56:08 PM MST] (Accessed Mar 1, 2024)</ref>.<blockquote>Crypto Rush strives to help give all coins a chance. We aim to be at the top of the crypto currency exchanges as we grow, we offer low fees compared to other exchanges. We also want to give new coins a chance and have a low cost system to help get coins in. When a coin goes down, users will be automatically alerted via twitter and e-mail and the markets suspended to secure your coins! Thank you for using Crypto Rush!		While CryptoRush used a .in extension<ref name=":1">[https://web.archive.org/web/20140317110538/https://www.cryptorush.in/ CryptoRush Homepage Archive March 17th, 2014 5:05:38 AM MDT] (Accessed Mar 1, 2024)</ref> which is the country code of India, the exchange was actually based in the United States. CryptoRush appears to favour small alternate currencies, and was aiming to be a top cryptocurrency exchange<ref name=":2">[https://web.archive.org/web/20140302065608/https://cryptorush.in/index.php?p=about About CryptoRush Archive March 1st, 2014 11:56:08 PM MST] (Accessed Mar 1, 2024)</ref>. Kristian (Devianttwo) founded the platform, while the other team members were reportedly named Matt and Chris, and they reportedly joined after beta<ref name=":2">[https://web.archive.org/web/20140302065608/https://cryptorush.in/index.php?p=about About CryptoRush Archive March 1st, 2014 11:56:08 PM MST] (Accessed Mar 1, 2024)</ref>.<blockquote>Crypto Rush strives to help give all coins a chance. We aim to be at the top of the crypto currency exchanges as we grow, we offer low fees compared to other exchanges. We also want to give new coins a chance and have a low cost system to help get coins in. When a coin goes down, users will be automatically alerted via twitter and e-mail and the markets suspended to secure your coins! Thank you for using Crypto Rush!

	Crypto Rush started by the owner Kristian in 2014 was originally to be just one market. But soon evolved into more, and even more. Matt joined the team fairly soon into development as co-owner, within a fortnight the basis was written from the ground up with security in mind.		Crypto Rush started by the owner Kristian in 2014 was originally to be just one market. But soon evolved into more, and even more. Matt joined the team fairly soon into development as co-owner, within a fortnight the basis was written from the ground up with security in mind.
Line 40:		Line 40:
	!Event		!Event
	!Description		!Description
			\|-
			\|February 26th, 2014 6:22:00 PM MST
			\|BlackCoin Trading Pairs Added
			\|The BlackCoin trading pairs are added to the CryptoRush website<ref name=":6">[https://twitter.com/TheCryptoRush/status/438846475460550656 CryptoRush - "@CoinBlack added, BC/BTC BC/LTC BC/POT BC/TEA #blackcoin" - Twitter] (Accessed Mar 12, 2024)</ref>. It can be traded against bitcoin, litecoin, potcoin, and teacoin<ref name=":6">[https://twitter.com/TheCryptoRush/status/438846475460550656 CryptoRush - "@CoinBlack added, BC/BTC BC/LTC BC/POT BC/TEA #blackcoin" - Twitter] (Accessed Mar 12, 2024)</ref>.
	\|-		\|-
	\|March 11th, 2014		\|March 11th, 2014
	\|Date Widely Cited		\|Date Widely Cited
	\|~~The date of the incident as reported by sources including Kyle Gibson<ref name="kylegibson-86" />.~~ According to DogeyMcDoge, this is the date when he was notified by Devianttwo that "something bad" had happened and brought into a Skype call where the hack was revealed<ref name=":4" />.		\|According to DogeyMcDoge, this is the date when he was notified by Devianttwo that "something bad" had happened and brought into a Skype call where the hack was revealed<ref name=":4" />. This date is widely cited as the date of the incident by sources including Kyle Gibson<ref name="kylegibson-86" />.
	\|-		\|-
	\|March 24th, 2014 8:30 AM MDT		\|March 24th, 2014 8:30 AM MDT
	\|Emergency Call		\|Emergency Call
	\|DogeyMcDoge calls Devianttwo on the emergency phone number and is told that he wasn't going to be able to fix the problems at the moment<ref name=":4" />.		\|DogeyMcDoge reportedly calls Devianttwo on the emergency phone number and is told that he wasn't going to be able to fix the problems at the moment<ref name=":4" />.
	\|-		\|-
	\|March 26th, 2014 5:02:01 AM MDT		\|March 26th, 2014 5:02:01 AM MDT
	\|Insider Information Leak		\|Insider Information Leak
	\|A CCN article sheds visibility into the lack of funds in the CryptoRush exchange platform<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>. A support worker at CryptoRush, named DogeyMcDoge, has leaked inside information regarding the exchange's troubles. This leak sheds light on the challenges faced by CryptoRush in the past month, including two hacking incidents and unorthodox methods to recover losses. Despite attempts to reassure users with solutions like CryptoRushShares, transparency issues persisted, leading to insolvency. DogeyMcDoge's confession has been confirmed by CryptoRush's administrators, who announced an official statement forthcoming. Meanwhile, CryptoRush has appointed a new CEO and promised to reimburse stolen funds. However, doubts linger about the exchange's ability to address its issues effectively<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>.		\|A CCN article sheds visibility into the lack of funds in the CryptoRush exchange platform<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>. A support worker at CryptoRush, named DogeyMcDoge, has leaked inside information regarding the exchange's troubles. This leak sheds light on the challenges faced by CryptoRush in the past month, including two hacking incidents and unorthodox methods to recover losses. Despite attempts to reassure users with solutions like CryptoRushShares, transparency issues persisted, leading to insolvency. DogeyMcDoge's confession has been confirmed by CryptoRush's administrators, who announced an official statement forthcoming. Meanwhile, CryptoRush has appointed a new CEO and promised to reimburse stolen funds. However, doubts linger about the exchange's ability to address its issues effectively<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>.
			\|-
			\|April 1st, 2014 10:17:48 AM MDT
			\|Death Thread On BitcoinTalk
			\|BitcoinTalk forum discussion about the "death" of cryptorush<ref>[https://bitcointalk.org/index.php?topic=553041.0 Death Of Cryptorush.in - BitcoinTalk] (Accessed Mar 12, 2024)</ref>.
	\|-		\|-
	\|November 11th, 2020 8:32:40 PM MST		\|November 11th, 2020 8:32:40 PM MST
Line 67:		Line 75:

	== Technical Details ==		== Technical Details ==
	<ref>https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL (Accessed Feb 27, 2024)</ref>

			<ref>[https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL PasteBin Chat Log Archive June 24th, 2019 11:35:14 AM MDT] (Accessed Feb 27, 2024)</ref>

	[https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN]		[https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN]
Line 83:		Line 93:

	=== Article/PasteBin Removal ===		=== Article/PasteBin Removal ===
	Both the CCN article<ref>[https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN] (Accessed Mar 8, 2024)</ref>, and the PasteBin<ref name=":5" /> were removed from the internet.		Both the CCN article<ref name=":7">[https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN] (Accessed Mar 8, 2024)</ref>, and the PasteBin<ref name=":5" /> were removed from the internet.

	=== Inclusion/Recognition On Lists ===		=== Inclusion/Recognition On Lists ===
Line 94:		Line 104:

	== Ongoing Developments ==		== Ongoing Developments ==
	It appears that there is an ongoing effort to suppress the information on what happened prior to the collapse of the CryptoRush platform.		It appears that there is an ongoing effort to suppress the information on what happened prior to the collapse of the CryptoRush platform<ref name=":5" /><ref name=":7" />.
	== Individual Prevention Policies ==		== Individual Prevention Policies ==
	{{Prevention:Individuals:~~Placeholder~~}}		{{Prevention:Individuals:Avoid Third Party Custodians}}

			{{Prevention:Individuals:Store Funds Offline}}

	{{Prevention:Individuals:End}}		{{Prevention:Individuals:End}}

	== Platform Prevention Policies ==		== Platform Prevention Policies ==
	{{Prevention:Platforms:~~Placeholder~~}}		{{Prevention:Platforms:Regular Audit Procedures}}

			{{Prevention:Platforms:Implement Multi-Signature}}

			{{Prevention:Platforms:Establish Industry Insurance Fund}}

	{{Prevention:Platforms:End}}		{{Prevention:Platforms:End}}

	== Regulatory Prevention Policies ==		== Regulatory Prevention Policies ==
	{{Prevention:Regulators:~~Placeholder~~}}		{{Prevention:Regulators:Platform Security Assessments}}

			{{Prevention:Regulators:Establish Industry Insurance Fund}}

	{{Prevention:Regulators:End}}		{{Prevention:Regulators:End}}

Azoundria: Another 30 minutes. Integrated more history on the CCN article. Review of CCN article. Filling in some sections without information. Improved summary description.

2024-03-08T23:58:25Z

Another 30 minutes. Integrated more history on the CCN article. Review of CCN article. Filling in some sections without information. Improved summary description.

← Older revision		Revision as of 17:58, 8 March 2024
Line 19:		Line 19:

	== The Reality ==		== The Reality ==
	Signs of limited experience were visible from the FAQ page of CryptoRush.in itself<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>. The FAQ page for Crypto Rush offers valuable information for users encountering various issues while using the platform<ref name=":3" />. It includes common login and activation problems, advising users to use their email address for authentication. For discrepancies in order fulfillment, users are encouraged to contact support for investigation and can review their transaction history for clarity<ref name=":3" />. Regarding deposit recognition delays, the FAQ explains the process and encourages users to verify deposits on the blockchain while providing a manual update option<ref name=":3" />. Lastly, it explains the trading engine's limitations, such as the trade rate matching and order fulfillment process, while offering guidance on resolving balance discrepancies caused by sync issues<ref name=":3" />.		Using any third party platform involves a high degree of risk. Signs of limited experience were visible from the FAQ page of CryptoRush.in itself<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>.

	* The FAQ covers issues related to negative balances after placing orders, attributing them to rounding errors and assuring users that they usually resolve automatically within 30 minutes<ref name=":3" />. Negative balances suggest weakness in the platform, which had not been corrected, suggesting the possibility of a vulnerability that could be more serious if repeatedly exploited<ref name=":3" />.		=== Negative Balance Concern ===
	* A FAQ entry mentioned that using email addresses was more secure than using usernames. It is not clear how this is the case, since many exploits can start from the user's email address being compromised, and one of the steps in exploiting to recover an account is often obtaining access to recovery points such as the email address. There is likely to be a similar number of breaches of username/password combinations in comparison to email/password combinations for users who reuse passwords. The only case where this could be useful is if the username is publicly visible on the platform itself, ~~and it~~'s ~~not clear whether or not this is~~ the ~~case~~<ref name=":3">~~[https://web~~.~~archive.org/web/20140302062552/https://cryptorush.in/index.php?p~~=~~faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>.~~		For discrepancies in order fulfillment, users are encouraged to contact support for investigation and can review their transaction history for clarity<ref name=":3" />. The FAQ covers issues related to negative balances after placing orders, attributing them to rounding errors and assuring users that they usually resolve automatically within 30 minutes<ref name=":3" />. Negative balances suggest weakness in the platform, which had not been corrected, suggesting the possibility of a vulnerability that could be more serious if repeatedly exploited<ref name=":3" />.

			=== Email Address Security Theater ===
			A FAQ entry mentioned that using email addresses was more secure than using usernames<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>. It is not clear how this is the case, since many exploits can start from the user's email address being compromised, and one of the steps in exploiting to recover an account is often obtaining access to recovery points such as the email address. There is likely to be a similar number of breaches of username/password combinations in comparison to email/password combinations for users who reuse passwords. The only case where this could be useful is if the username is publicly visible on the platform itself, giving an attacker knowledge of which username to use, however most exchange platforms do not identify the counterparties to a trade.

			=== Trade Engine Limitations ===
			The FAQ page explains the trading engine's limitations, such as the trade rate matching and order fulfillment process, while offering guidance on resolving balance discrepancies caused by sync issues<ref name=":3" />.

			=== Each Coin Adds Attack Surface ===
	Every coin supported increases the attack surface against a platform, since an issue in one coin could inflate the user's balance and allow them to trade against other coins.		Every coin supported increases the attack surface against a platform, since an issue in one coin could inflate the user's balance and allow them to trade against other coins.

Line 44:		Line 52:
	\|Insider Information Leak		\|Insider Information Leak
	\|A CCN article sheds visibility into the lack of funds in the CryptoRush exchange platform<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>. A support worker at CryptoRush, named DogeyMcDoge, has leaked inside information regarding the exchange's troubles. This leak sheds light on the challenges faced by CryptoRush in the past month, including two hacking incidents and unorthodox methods to recover losses. Despite attempts to reassure users with solutions like CryptoRushShares, transparency issues persisted, leading to insolvency. DogeyMcDoge's confession has been confirmed by CryptoRush's administrators, who announced an official statement forthcoming. Meanwhile, CryptoRush has appointed a new CEO and promised to reimburse stolen funds. However, doubts linger about the exchange's ability to address its issues effectively<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>.		\|A CCN article sheds visibility into the lack of funds in the CryptoRush exchange platform<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>. A support worker at CryptoRush, named DogeyMcDoge, has leaked inside information regarding the exchange's troubles. This leak sheds light on the challenges faced by CryptoRush in the past month, including two hacking incidents and unorthodox methods to recover losses. Despite attempts to reassure users with solutions like CryptoRushShares, transparency issues persisted, leading to insolvency. DogeyMcDoge's confession has been confirmed by CryptoRush's administrators, who announced an official statement forthcoming. Meanwhile, CryptoRush has appointed a new CEO and promised to reimburse stolen funds. However, doubts linger about the exchange's ability to address its issues effectively<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>.
			\|-
			\|November 11th, 2020 8:32:40 PM MST
			\|CCN Article Redirects
			\|In future captures, the CCN article appears to automatically redirect users to an article about the "PS5 Skeleton Leaks to Peek Inside Sony’s Next-Gen Console"<ref>https://web.archive.org/web/20210308011115/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info (Accessed Mar 8, 2024)</ref><ref>[https://web.archive.org/web/20201112033240/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN Archive November 11th, 2020 8:32:40 PM MST] (Accessed Mar 8, 2024)</ref>. The article was still online in 2019<ref>[https://web.archive.org/web/20190628080310/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN Archive June 28th, 2019 2:03:10 AM MDT] (Accessed Mar 8, 2024)</ref>.
	\|-		\|-
	\|May 9th, 2021 11:22:00 AM MDT		\|May 9th, 2021 11:22:00 AM MDT
	\|PasteBin Information Censored		\|PasteBin Information Censored
	\|The information about this case is removed from the PasteBin site for the content being "potentially harmful"<ref>[https://pastebin.com/eLkPxLWi DogeyMcDoge Pastebin] (Accessed Mar 1, 2024)</ref>.		\|The information about this case is removed from the PasteBin site for the content being "potentially harmful"<ref name=":5">[https://pastebin.com/eLkPxLWi DogeyMcDoge Pastebin] (Accessed Mar 1, 2024)</ref>.
			\|-
			\|October 26th, 2022 9:28:15 AM MDT
			\|Further Censorship Redirect Removed
			\|The CCN article no longer redirects, but instead displays a 404 error that the article does not exist<ref>[https://web.archive.org/web/20221026152815/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN Archive October 26th, 2022 9:28:15 AM MDT] (Accessed Mar 8, 2024)</ref>.
	\|}		\|}

Line 53:		Line 69:
	<ref>https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL (Accessed Feb 27, 2024)</ref>		<ref>https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL (Accessed Feb 27, 2024)</ref>

	https://www.ccn.com/cryptorush-support-worker-leaks-inside-info		[https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN]

	== Total Amount Lost ==		== Total Amount Lost ==
Line 64:		Line 80:

	== Ultimate Outcome ==		== Ultimate Outcome ==
	~~What was~~ the ~~end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?~~		The CryptoRush platform theft and collapse were widely reported. Around 2020, content about the incident started disappearing from the internet.



			=== Article/PasteBin Removal ===
			Both the CCN article<ref>[https://www.ccn.com/cryptorush-support-worker-leaks-inside-info CryptoRush support worker leaks inside info - CCN] (Accessed Mar 8, 2024)</ref>, and the PasteBin<ref name=":5" /> were removed from the internet.

			=== Inclusion/Recognition On Lists ===
	The issue was featured on several lists including Kyle Gibson<ref name="kylegibson-86" />, and the Idex Blog<ref name="idexblog-7454" />.		The issue was featured on several lists including Kyle Gibson<ref name="kylegibson-86" />, and the Idex Blog<ref name="idexblog-7454" />.

Line 77:		Line 94:

	== Ongoing Developments ==		== Ongoing Developments ==
	~~What parts~~ of ~~this case are still remaining to be concluded?~~		It appears that there is an ongoing effort to suppress the information on what happened prior to the collapse of the CryptoRush platform.
	~~== General Prevention Policies ==~~
	~~Coming soon~~.
	== Individual Prevention Policies ==		== Individual Prevention Policies ==
	{{Prevention:Individuals:Placeholder}}		{{Prevention:Individuals:Placeholder}}

Azoundria: Another 30 minutes complete. More comprehensive review and integration of Pastebin source, and added proper reference. Rewrote sections of the wiki for greater readability.

2024-03-07T20:43:43Z

Another 30 minutes complete. More comprehensive review and integration of Pastebin source, and added proper reference. Rewrote sections of the wiki for greater readability.

Show changes

Azoundria: Another 30 minutes complete. About section split apart. Added a screenshot and logo from the website. Integrated information from the about and FAQ sections of the site. Started review/integration of Pastebin source.

2024-03-01T18:46:02Z

Another 30 minutes complete. About section split apart. Added a screenshot and logo from the website. Integrated information from the about and FAQ sections of the site. Started review/integration of Pastebin source.

← Older revision		Revision as of 12:46, 1 March 2024
Line 6:		Line 6:

	== About CryptoRush ==		== About CryptoRush ==
	While CryptoRush used a .in extension<ref name=":1">[https://web.archive.org/web/20140317110538/https://www.cryptorush.in/ CryptoRush Homepage Archive March 17th, 2014 5:05:38 AM MDT] (Accessed Mar 1, 2024)</ref> which is the country code of India, the exchange was actually based in the United States. CryptoRush appears to favour small alternate currencies, and was aiming to be a top cryptocurrency exchange<ref name=":1">[https://web.archive.org/web/~~20140317110538~~/https://~~www.~~cryptorush.in/ CryptoRush ~~Homepage~~ Archive March ~~17th~~, 2014 5:05:~~38 AM MDT~~] (Accessed Mar 1, 2024)</ref>. The founder was reportedly named Kristian, while the other team members were reportedly named Matt and Chris, who joined after beta<ref name=":1">[https://web.archive.org/web/~~20140317110538~~/https://~~www.~~cryptorush.in/ CryptoRush ~~Homepage~~ Archive March ~~17th~~, 2014 5:05:~~38 AM MDT~~] (Accessed Mar 1, 2024)</ref>.<blockquote>Crypto Rush strives to help give all coins a chance. We aim to be at the top of the crypto currency exchanges as we grow, we offer low fees compared to other exchanges. We also want to give new coins a chance and have a low cost system to help get coins in. When a coin goes down, users will be automatically alerted via twitter and e-mail and the markets suspended to secure your coins! Thank you for using Crypto Rush!		While CryptoRush used a .in extension<ref name=":1">[https://web.archive.org/web/20140317110538/https://www.cryptorush.in/ CryptoRush Homepage Archive March 17th, 2014 5:05:38 AM MDT] (Accessed Mar 1, 2024)</ref> which is the country code of India, the exchange was actually based in the United States. CryptoRush appears to favour small alternate currencies, and was aiming to be a top cryptocurrency exchange<ref name=":2">[https://web.archive.org/web/20140302065608/https://cryptorush.in/index.php?p=about About CryptoRush Archive March 1st, 2014 11:56:08 PM MST] (Accessed Mar 1, 2024)</ref>. The founder was reportedly named Kristian, while the other team members were reportedly named Matt and Chris, who joined after beta<ref name=":2">[https://web.archive.org/web/20140302065608/https://cryptorush.in/index.php?p=about About CryptoRush Archive March 1st, 2014 11:56:08 PM MST] (Accessed Mar 1, 2024)</ref>.<blockquote>Crypto Rush strives to help give all coins a chance. We aim to be at the top of the crypto currency exchanges as we grow, we offer low fees compared to other exchanges. We also want to give new coins a chance and have a low cost system to help get coins in. When a coin goes down, users will be automatically alerted via twitter and e-mail and the markets suspended to secure your coins! Thank you for using Crypto Rush!

	Crypto Rush started by the owner Kristian in 2014 was originally to be just one market. But soon evolved into more, and even more. Matt joined the team fairly soon into development as co-owner, within a fortnight the basis was written from the ground up with security in mind.		Crypto Rush started by the owner Kristian in 2014 was originally to be just one market. But soon evolved into more, and even more. Matt joined the team fairly soon into development as co-owner, within a fortnight the basis was written from the ground up with security in mind.

	When beta launched, Chris joined the team and helped increase productivity with his skillset</blockquote>		When beta launched, Chris joined the team and helped increase productivity with his skillset</blockquote>The Frequently Asked Questions (FAQ) page for Crypto Rush offers valuable information for users encountering various issues while using the platform. It addresses common login and activation problems, advises users to use their email address for authentication, and offers manual activation assistance if necessary. The FAQ also covers issues related to negative balances after placing orders, attributing them to rounding errors and assuring users that they usually resolve automatically within 30 minutes. For discrepancies in order fulfillment, users are encouraged to contact support for investigation and can review their transaction history for clarity. Regarding deposit recognition delays, the FAQ explains the process and encourages users to verify deposits on the blockchain while providing a manual update option. It also assures users of the platform's security measures and offers assistance for any redirection issues.<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>

			Furthermore, the FAQ lists supported coins on the platform, providing users with comprehensive information about the available cryptocurrencies for trading. It clarifies the fees charged by Crypto Rush, including buying and selling fees, withdrawal fees, and fees for accepting new coins, aiming to offer competitive rates and superior service. Additionally, the FAQ explains the varying withdrawal fees for different coins, attributing them to both platform fees and network transaction fees. It also addresses users' inquiries about purchasing coins directly from Crypto Rush, emphasizing that while plans exist, this feature is not currently available. Moreover, the FAQ reassures users about the safety of their coins, detailing the platform's security measures and separate storage for wallets. Lastly, it explains the trading engine's limitations, such as the trade rate matching and order fulfillment process, while offering guidance on resolving balance discrepancies caused by sync issues.<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>

	== The Reality ==		== The Reality ==
	~~This sections is included if~~ a ~~case involved deception or information that was unknown at~~ the ~~time~~. ~~Examples include:~~		Every coin supported increases the attack surface against a platform, since an issue in one coin could inflate the user's balance and allow them to trade against other coins.

	* When the service was actually started (if different than the "~~official story~~").		Signs of limited experience were visible from the FAQ page of CryptoRush.in itself<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>.
	* ~~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~~".)		* A FAQ entry reported on an outstanding issue with negative balances, which had not been corrected, and suggested the possibility that users might have even larger negative balances. Negative balances suggest a vulnerability in the platform, which could be exploited for further loss<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>.
	* Details of what audits reported and how vulnerabilities were missed during auditing.		* A FAQ entry mentioned that using email addresses was more secure than using usernames. It is not clear how this is the case, since many exploits can start from the user's email address being compromised, and one of the steps in exploiting to recover an account is often obtaining access to recovery points such as the email address. There is likely to be a similar number of breaches of username/password combinations in comparison to email/password combinations for users who reuse passwords. The only case where this could be useful is if the username is publicly visible on the platform itself, and it's not clear whether or not this is the case<ref name=":3">[https://web.archive.org/web/20140302062552/https://cryptorush.in/index.php?p=faq CryptoRush FAQ Page Archive March 1st, 2014 11:25:52 PM MST] (Accessed Mar 1, 2024)</ref>.

	== What Happened ==		== 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~~.		The CryptoRush platform was exploited, with the attacker managing to withdraw 950 BTC and 2500 LTC.
	{\| class="wikitable"		{\| class="wikitable"
	\|+Key Event Timeline - CryptoRush Hack		\|+Key Event Timeline - CryptoRush Hack
Line 35:		Line 37:
	\|Insider Information Leak		\|Insider Information Leak
	\|A CCN article sheds visibility into the lack of funds in the CryptoRush exchange platform<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>. A support worker at CryptoRush, named DogeyMcDoge, has leaked inside information regarding the exchange's troubles. This leak sheds light on the challenges faced by CryptoRush in the past month, including two hacking incidents and unorthodox methods to recover losses. Despite attempts to reassure users with solutions like CryptoRushShares, transparency issues persisted, leading to insolvency. DogeyMcDoge's confession has been confirmed by CryptoRush's administrators, who announced an official statement forthcoming. Meanwhile, CryptoRush has appointed a new CEO and promised to reimburse stolen funds. However, doubts linger about the exchange's ability to address its issues effectively<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>.		\|A CCN article sheds visibility into the lack of funds in the CryptoRush exchange platform<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>. A support worker at CryptoRush, named DogeyMcDoge, has leaked inside information regarding the exchange's troubles. This leak sheds light on the challenges faced by CryptoRush in the past month, including two hacking incidents and unorthodox methods to recover losses. Despite attempts to reassure users with solutions like CryptoRushShares, transparency issues persisted, leading to insolvency. DogeyMcDoge's confession has been confirmed by CryptoRush's administrators, who announced an official statement forthcoming. Meanwhile, CryptoRush has appointed a new CEO and promised to reimburse stolen funds. However, doubts linger about the exchange's ability to address its issues effectively<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>.
			\|-
			\|May 9th, 2021 11:22:00 AM MDT
			\|PasteBin Information Censored
			\|The PasteBin information about this case is removed from the site<ref>[https://pastebin.com/eLkPxLWi DogeyMcDoge Pastebin] (Accessed Mar 1, 2024)</ref>.
	\|}		\|}
	~~Technical Details~~

			== Technical Details ==
	<ref>https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL (Accessed Feb 27, 2024)</ref>		<ref>https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL (Accessed Feb 27, 2024)</ref>

Azoundria at 18:16, 1 March 2024

2024-03-01T18:16:46Z

← Older revision		Revision as of 12:16, 1 March 2024
Line 1:		Line 1:
	{{Case Study Under Construction}}{{Unattributed Sources}}		{{Case Study Under Construction}}{{Unattributed Sources}}[[File:Cryptorush.jpg\|thumb\|CryptoRush Logo/Homepage]]

	The primary issue here appears to be numerous exploits in the various alt coin withdrawal processes which CryptoRush handled through hot wallets. This seems to be based on the service being quickly coded in a few short months.		The primary issue here appears to be numerous exploits in the various alt coin withdrawal processes which CryptoRush handled through hot wallets. This seems to be based on the service being quickly coded in a few short months.

Azoundria at 18:16, 1 March 2024

2024-03-01T18:16:08Z

@@ Line 6: / Line 6: @@
 == About CryptoRush ==
-This exchange or platform is based in United States, or the incident targeted people primarily in United States.
+When beta launched, Chris joined the team and helped increase productivity with his skillset</blockquote>
 == The Reality ==

Azoundria at 00:00, 1 March 2024

2024-03-01T00:00:56Z

← Older revision		Revision as of 18:00, 29 February 2024
Line 43:		Line 43:
	!Description		!Description
	\|-		\|-
	\|March ~~1st~~, 2014 ~~12:00:30 AM MST~~		\|March 11th, 2014
	\|~~Main Event~~		\|Date Widely Cited
	\|~~Expand this into a brief description~~ of ~~what happened and~~ the ~~impact. If multiple lines are necessary, add them here~~.		\|The date of the incident as reported by sources including Kyle Gibson<ref name="kylegibson-86" />.
	\|-		\|-
	\|March 26th, 2014 5:02:01 AM MDT		\|March 26th, 2014 5:02:01 AM MDT
Line 54:		Line 54:

	<ref>https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL (Accessed Feb 27, 2024)</ref>		<ref>https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL (Accessed Feb 27, 2024)</ref>

			https://www.ccn.com/cryptorush-support-worker-leaks-inside-info

	== Total Amount Lost ==		== Total Amount Lost ==
	Losses were reportedly up to 950 BTC and 2500 LTC<ref name="idexblog-7454" />.		Losses were reportedly up to 950 BTC<ref name="kylegibson-86" /> and 2500 LTC<ref name="idexblog-7454" />.

	~~The total amount lost has been estimated at $800,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?~~		The total amount lost has been estimated at $800,000 USD<ref name="kylegibson-86" />.

	== Immediate Reactions ==		== Immediate Reactions ==
Line 67:		Line 67:
	== Ultimate Outcome ==		== Ultimate Outcome ==
	What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?		What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?



	"The guilt was starting to build up inside of me. I answered very few tickets the week of the 16th. I was conflicted, but I worked at my full time job >40 hours that week, so it kept my mind off of things a little. The issues continued. I kept suggesting ways we could maybe get some BTC back, arbitrage, etc. We didn’t even have enough funds for that. I wanted so bad for the exchange to stay afloat, thinking “Maybe tomorrow will bring us back our volume!” But alas, the problems with Zeit, and BTC withdrawals killed our volume. There was no coming back."		"The guilt was starting to build up inside of me. I answered very few tickets the week of the 16th. I was conflicted, but I worked at my full time job >40 hours that week, so it kept my mind off of things a little. The issues continued. I kept suggesting ways we could maybe get some BTC back, arbitrage, etc. We didn’t even have enough funds for that. I wanted so bad for the exchange to stay afloat, thinking “Maybe tomorrow will bring us back our volume!” But alas, the problems with Zeit, and BTC withdrawals killed our volume. There was no coming back."


	The issue was featured on several lists including Kyle Gibson<ref name="kylegibson-86" />, and the Idex Blog<ref name="idexblog-7454" />.		The issue was featured on several lists including Kyle Gibson<ref name="kylegibson-86" />, and the Idex Blog<ref name="idexblog-7454" />.

Azoundria: COMPLETE Another 30 minutes. About section spread around. Reviewing different lists as sources. Integrating information into article. Found and integrated news article. Reviewed chat with Blackcoin developers.

2024-02-27T23:27:13Z

COMPLETE Another 30 minutes. About section spread around. Reviewing different lists as sources. Integrating information into article. Found and integrated news article. Reviewed chat with Blackcoin developers.

← Older revision		Revision as of 17:27, 27 February 2024
Line 1:		Line 1:
	{{~~Imported~~ Case Study ~~2\|source=https://www.quadrigainitiative.com/casestudy/cryptorushhack.php~~}}		{{Case Study Under Construction}}{{Unattributed Sources}}
	{{Unattributed Sources}}

	The primary issue here appears to be numerous exploits in the various alt coin withdrawal processes which CryptoRush handled through hot wallets. This seems to be based on the service being quickly coded in a few short months.		The primary issue here appears to be numerous exploits in the various alt coin withdrawal processes which CryptoRush handled through hot wallets. This seems to be based on the service being quickly coded in a few short months.
Line 7:		Line 6:

	== About CryptoRush ==		== About CryptoRush ==
	"The guilt was starting to build up inside of me. I answered very few tickets the week of the 16th. I was conflicted, but I worked at my full time job >40 hours that week, so it kept my mind off of things a little. The issues continued. I kept suggesting ways we could maybe get some BTC back, arbitrage, etc. We didn’t even have enough funds for that. I wanted so bad for the exchange to stay afloat, thinking “Maybe tomorrow will bring us back our volume!” But alas, the problems with Zeit, and BTC withdrawals killed our volume. There was no coming back."

	This exchange or platform is based in United States, or the incident targeted people primarily in United States.		This exchange or platform is based in United States, or the incident targeted people primarily in United States.
Line 48:		Line 47:
	\|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.
	\|-		\|-
	\|		\|March 26th, 2014 5:02:01 AM MDT
	\|		\|Insider Information Leak
	\|		\|A CCN article sheds visibility into the lack of funds in the CryptoRush exchange platform<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>. A support worker at CryptoRush, named DogeyMcDoge, has leaked inside information regarding the exchange's troubles. This leak sheds light on the challenges faced by CryptoRush in the past month, including two hacking incidents and unorthodox methods to recover losses. Despite attempts to reassure users with solutions like CryptoRushShares, transparency issues persisted, leading to insolvency. DogeyMcDoge's confession has been confirmed by CryptoRush's administrators, who announced an official statement forthcoming. Meanwhile, CryptoRush has appointed a new CEO and promised to reimburse stolen funds. However, doubts linger about the exchange's ability to address its issues effectively<ref name=":0">[https://web.archive.org/web/20190624073719/https://www.ccn.com/cryptorush-support-worker-leaks-inside-info/ CryptoRush support worker leaks inside info - CCN Archive June 24th, 2019 1:37:19 AM MDT] (Accessed Feb 27, 2024)</ref>.
	\|}		\|}
			Technical Details

			<ref>https://web.archive.org/web/20190624173514/https://pastebin.com/qW3xRmcL (Accessed Feb 27, 2024)</ref>

	== Total Amount Lost ==		== Total Amount Lost ==
			Losses were reportedly up to 950 BTC and 2500 LTC<ref name="idexblog-7454" />.

	The total amount lost has been estimated at $800,000 USD.		The total amount lost has been estimated at $800,000 USD.

Line 63:		Line 67:
	== Ultimate Outcome ==		== Ultimate Outcome ==
	What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?		What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?


			"The guilt was starting to build up inside of me. I answered very few tickets the week of the 16th. I was conflicted, but I worked at my full time job >40 hours that week, so it kept my mind off of things a little. The issues continued. I kept suggesting ways we could maybe get some BTC back, arbitrage, etc. We didn’t even have enough funds for that. I wanted so bad for the exchange to stay afloat, thinking “Maybe tomorrow will bring us back our volume!” But alas, the problems with Zeit, and BTC withdrawals killed our volume. There was no coming back."


			The issue was featured on several lists including Kyle Gibson<ref name="kylegibson-86" />, and the Idex Blog<ref name="idexblog-7454" />.

	== Total Amount Recovered ==		== Total Amount Recovered ==
	There do not appear to have been any funds recovered in this case.		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?~~		The exchange issued a “Debt Management Plan” which outlined plans and potential refunds for victims<ref name="idexblog-7454" />.

	== Ongoing Developments ==		== Ongoing Developments ==
Line 89:		Line 99:

	== References ==		== References ==
	<references><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>		<references>
			<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 - Kyle Gibson] (Jan 25, 2020)</ref>
	<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>		<ref name="bitcointalklist-87">[https://bitcointalk.org/index.php?topic=576337 List of Major Bitcoin Heists, Thefts, Hacks, Scams, and Losses - BitcoinTalk] (Feb 15, 2020)</ref>

	<ref name="bitcoinexchangeguide-218">[https://bitcoinexchangeguide.com/bitcoin/scams-hacks/ Bitcoin Scams and Cryptocurrency Hacks List - BitcoinExchangeGuide.com] (Mar 5, 2020)</ref>		<ref name="bitcoinexchangeguide-218">[https://bitcoinexchangeguide.com/bitcoin/scams-hacks/ Bitcoin Scams and Cryptocurrency Hacks List - BitcoinExchangeGuide.com] (Mar 5, 2020)</ref>
			<ref name="idexblog-7454">[https://blog.idex.io/all-posts/a-complete-list-of-cryptocurrency-exchange-hacks-updated/#2014 <nowiki>A Complete List of Cryptocurrency Exchange Hacks [Updated] - Idex Blog Archive February 15th, 2021 4:34:24 AM MST</nowiki>] (Accessed Mar 26, 2022)</ref>
	<ref name="idexblog-7454">[https://blog.idex.io/all-posts/a-complete-list-of-cryptocurrency-exchange-hacks-updated/#2014 ~~https://blog.idex.io/all-posts/a-complete-list-~~of-~~cryptocurrency-exchange-hacks-updated~~/~~#2014~~] (Mar 26, 2022)</ref>		<ref name="cointelegraph-7455">[https://cointelegraph.com/news/bitcoins-correction-could-well-have-shaken-out-potentially-damaging-investors Bitcoin’s Correction Could Well Have Shaken Out Potentially Damaging Investors - CoinTelegraph] (Mar 26, 2022)</ref>
			</references>
	<ref name="cointelegraph-7455">[https://cointelegraph.com/news/bitcoins-correction-could-well-have-shaken-out-potentially-damaging-investors Bitcoin’s Correction Could Well Have Shaken Out Potentially Damaging Investors] (Mar 26, 2022)</ref></references>

Azoundria at 23:56, 12 April 2023

2023-04-12T23:56:25Z

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

	The primary issue here appears to be numerous exploits in the various alt coin withdrawal processes which CryptoRush handled through hot wallets. This seems to be based on the service being quickly coded in a few short months.		The primary issue here appears to be numerous exploits in the various alt coin withdrawal processes which CryptoRush handled through hot wallets. This seems to be based on the service being quickly coded in a few short months.

	This exchange or platform is based in United States, or the incident targeted people primarily in United States.		This exchange or platform is based in United States, or the incident targeted people primarily in United States.<ref name="kylegibson-86" /><ref name="bitcointalklist-87" /><ref name="bitcoinexchangeguide-218" /><ref name="idexblog-7454" /><ref name="cointelegraph-7455" />
	<ref name="kylegibson-86" /><ref name="bitcointalklist-87" /><ref name="bitcoinexchangeguide-218" /><ref name="idexblog-7454" /><ref name="cointelegraph-7455" />

	== About CryptoRush ==		== About CryptoRush ==
Line 45:		Line 44:
	!Description		!Description
	\|-		\|-
	\|March 1st, 2014 12:00:30 AM		\|March 1st, 2014 12:00:30 AM MST
	\|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 ==
			Coming soon.
			== Individual Prevention Policies ==
			{{Prevention:Individuals:Placeholder}}

			{{Prevention:Individuals:End}}

	== Prevention Policies ==		== Platform Prevention Policies ==
	~~Coming soon.~~		{{Prevention:Platforms:Placeholder}}

			{{Prevention:Platforms:End}}

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

			{{Prevention:Regulators:End}}

	== References ==		== References ==