Etbox Wallet Hacked: Difference between revisions

From Quadriga Initiative Cryptocurrency Hacks, Scams, and Frauds Repository
Jump to navigation Jump to search
(Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/etboxwallethacked.php}} thumb|ETBoxETBox appears to have been a centralized exchange platform which existed and had their wallet hacked in 2019. There is limited record of the hack and the exchange does not appear to exist at present. This exchange or platform is based in Seychelles, or the incident targeted people primarily in Seychelles. == About ETBox == "ETBOX is a global...")
 
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/etboxwallethacked.php}}
{{Imported Case Study 2|source=https://www.quadrigainitiative.com/casestudy/etboxwallethacked.php}}
{{Unattributed Sources}}


[[File:Etbox.jpg|thumb|ETBox]]ETBox appears to have been a centralized exchange platform which existed and had their wallet hacked in 2019.
[[File:Etbox.jpg|thumb|ETBox]]ETBox appears to have been a centralized exchange platform which existed and had their wallet hacked in 2019.
Line 5: Line 6:
There is limited record of the hack and the exchange does not appear to exist at present.
There is limited record of the hack and the exchange does not appear to exist at present.


This exchange or platform is based in Seychelles, or the incident targeted people primarily in Seychelles.
This exchange or platform is based in Seychelles, or the incident targeted people primarily in Seychelles.<ref name="slowmisthacked-1160" /><ref name="blocking-2261" /><ref name="coincarp-2273" /><ref name="bixiaobao-2274" /><ref name="bibiqing-2275" /><ref name="cryptoxdirectory-2276" /><ref name="etboxarchive-2277" />


== About ETBox ==
== About ETBox ==
Line 31: Line 32:


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 52: Line 52:
!Description
!Description
|-
|-
|March 24th, 2019 12:00:00 AM
|March 24th, 2019
|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 60:
|
|
|}
|}
== 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 ==
The total amount lost is unknown.
The total amount lost has been estimated at $132,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 77: Line 76:


== 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 82:
== 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 ==
There is limited details, but in general, having assets in cold storage, with the signing authority shared between multiple people, and visibility to ensure customer assets are backed would prevent almost all known cases.
== Individual Prevention Policies ==
{{Prevention:Individuals:Placeholder}}
{{Prevention:Individuals:End}}
== Platform Prevention Policies ==
{{Prevention:Platforms:Placeholder}}
{{Prevention:Platforms:End}}


== Prevention Policies ==
== Regulatory Prevention Policies ==
There is limited details, but in general, having assets in cold storage, with the signing authority shared between multiple people, and visibility to ensure customer assets are backed would prevent almost all known cases.
{{Prevention:Regulators:Placeholder}}
 
{{Prevention:Regulators:End}}


== References ==
== References ==
[https://hacked.slowmist.io/en/?c=Exchange SlowMist Hacked - SlowMist Zone] (Jun 25)
<references><ref name="slowmisthacked-1160">[https://hacked.slowmist.io/en/?c=Exchange SlowMist Hacked - SlowMist Zone] (Jun 26, 2021)</ref>


[https://blocking.net/464/how-hard-is-it-to-lose-money-on-the-exchange-and-how-to-recover-bitcoin-digital-assets/ How hard is it to lose money on the exchange and how to recover bitcoin digital assets? Blockchain Network] (Aug 6)
<ref name="blocking-2261">[https://blocking.net/464/how-hard-is-it-to-lose-money-on-the-exchange-and-how-to-recover-bitcoin-digital-assets/ How hard is it to lose money on the exchange and how to recover bitcoin digital assets? Blockchain Network] (Aug 7, 2021)</ref>


[https://www.coincarp.com/exchange/etbox/ ETBOX Exchange Live Markets, trade volume ,Guides, and Info | CoinCarp] (Aug 6)
<ref name="coincarp-2273">[https://www.coincarp.com/exchange/etbox/ ETBOX Exchange Live Markets, trade volume ,Guides, and Info | CoinCarp] (Aug 7, 2021)</ref>


[https://www.bixiaobao.com/en/exchange/etbox etbox Trade Volume, Ranking and etbox Listing Pairs | Bixiaobao] (Aug 7)
<ref name="bixiaobao-2274">[https://www.bixiaobao.com/en/exchange/etbox etbox Trade Volume, Ranking and etbox Listing Pairs | Bixiaobao] (Aug 8, 2021)</ref>


[https://www.bibiqing.com/exchange/etbox ETBOX交易所_ETBOX交易平台_ETBOX交易行情-币币情] (Aug 7)
<ref name="bibiqing-2275">[https://www.bibiqing.com/exchange/etbox ETBOX交易所_ETBOX交易平台_ETBOX交易行情-币币情] (Aug 8, 2021)</ref>


[https://cryptoxdirectory.com/hacked_2019 The 23 exchange hacks of 2019] (Aug 7)
<ref name="cryptoxdirectory-2276">[https://cryptoxdirectory.com/hacked_2019 The 23 exchange hacks of 2019] (Aug 8, 2021)</ref>


[https://web.archive.org/web/20180808104635/http://etbox.com/ Wayback Machine] (Aug 7)
<ref name="etboxarchive-2277">[https://web.archive.org/web/20180808104635/http://etbox.com/ Wayback Machine] (Aug 8, 2021)</ref></references>

Latest revision as of 13:00, 1 May 2023

Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' and 'General Prevention' sections to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.

Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!

ETBox

ETBox appears to have been a centralized exchange platform which existed and had their wallet hacked in 2019.

There is limited record of the hack and the exchange does not appear to exist at present.

This exchange or platform is based in Seychelles, or the incident targeted people primarily in Seychelles.[1][2][3][4][5][6][7]

About ETBox

"ETBOX is a global professional digital currency trading platform that combines the high performance of a centralized exchange with the high reliability of a decentralized public chain. Committed to discovering high-quality innovative digital asset investment opportunities, it currently provides trading and investment services for more than ten mainstream digital products. The core team of ETBOX is from the professional technology and operation teams of IBM, ApplePay, Goldman Sachs, the former Liquid Digital Currency Exchange, and the Digital Money Alliance of James Simmons. It has rich experience in technology research and development and global operations in the digital currency field."

"With a self-developed core transaction matching system and a fast and smooth user experience, ETbox.com is committed to creating the safest, most stable and efficient digital currency trading platform for users around the world. ETBOX intelligent ant quantification robot (abbreviation: ET robot), former IBM, ApplePay, Goldman Sachs, former Liquid Digital Currency Exchange, James Simmons' digital currency alliance and other professional technical and operational teams to develop the highest efficiency ETBOX intelligent ant quantification robot ( Abbreviation: ET robot), real-time tracking to capture big data and efficient market analysis of major trading platforms, the robot will identify the difference and transaction volume of digital assets in each trading platform, decide whether to execute the arbitrage task, and start the arbitrage transaction at the right time. The robot can also capture the spread of each digital asset in each trading platform in real time, decide whether to conduct trading, contract trading and other arbitrage methods, which can make our entrusted digital assets completely free from price fluctuations, and solve the problem of manual arbitrage. The shortcomings and risks, intelligent arbitrage transactions in real time."

"On the day of the hacker attack on Dragon.com, the exchange was also blocked by Etbox." "The Etbox platform wallet was hacked, causing the platform’s digital assets to be stolen."

"Three days later, Etbox issued a statement saying that the attack caused the platform to lose assets of $132,000."

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

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.

Key Event Timeline - Etbox Wallet Hacked
Date Event Description
March 24th, 2019 Main Event Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.

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

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

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

Immediate Reactions

How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

Ultimate Outcome

What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

Total Amount Recovered

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?

Ongoing Developments

What parts of this case are still remaining to be concluded?

General Prevention Policies

There is limited details, but in general, having assets in cold storage, with the signing authority shared between multiple people, and visibility to ensure customer assets are backed would prevent almost all known cases.

Individual Prevention Policies

No specific policies for individual prevention have yet been identified in this case.

For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.

Platform Prevention Policies

Policies for platforms to take to prevent this situation have not yet been selected in this case.

For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.

Regulatory Prevention Policies

No specific regulatory policies have yet been identified in this case.

For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.

References