BitWhisk Relaunched Fraud Site: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/bitwhiskrelaunchedfraudsite.php}} | {{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/bitwhiskrelaunchedfraudsite.php}} | ||
{{Unattributed | {{Unattributed Sources}} | ||
[[File:Bitwhisk.jpg|thumb|BitWhisk]]BitWhisk was a bitcoin mixing service launched around March 2018. Users could give bitcoin to receive mixed bitcoin. The service went offline around November 2018 after mixing just 3 BTC. Since that time, a fraudster set up a fake mixing service on the same domain. A small amount of funds have been sent to the fraudulent mixer service. | [[File:Bitwhisk.jpg|thumb|BitWhisk]]BitWhisk was a bitcoin mixing service launched around March 2018. Users could give bitcoin to receive mixed bitcoin. The service went offline around November 2018 after mixing just 3 BTC. Since that time, a fraudster set up a fake mixing service on the same domain. A small amount of funds have been sent to the fraudulent mixer service. | ||
This is a global/international case not involving a specific country. | This is a global/international case not involving a specific country.<ref name="bitcointalk-5614" /><ref name="archive-5615" /><ref name="bitwhisktwitter-5616" /><ref name="bitcointalk-5617" /><ref name="bitwhiskarchive-5618" /><ref name="bitwhiskarchive-5619" /> | ||
<ref name="bitcointalk-5614" /><ref name="archive-5615" /><ref name="bitwhisktwitter-5616" /><ref name="bitcointalk-5617" /><ref name="bitwhiskarchive-5618" /><ref name="bitwhiskarchive-5619" /> | |||
== About BitWhisk == | == About BitWhisk == | ||
| Line 59: | Line 58: | ||
!Description | !Description | ||
|- | |- | ||
|August 23rd, 2019 6:34:28 AM | |August 23rd, 2019 6:34:28 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 67: | Line 66: | ||
| | | | ||
|} | |} | ||
== 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 86: | Line 88: | ||
== 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:Regulators:End}} | |||
== References == | == References == | ||
Latest revision as of 13:23, 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' section to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.
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!
BitWhisk was a bitcoin mixing service launched around March 2018. Users could give bitcoin to receive mixed bitcoin. The service went offline around November 2018 after mixing just 3 BTC. Since that time, a fraudster set up a fake mixing service on the same domain. A small amount of funds have been sent to the fraudulent mixer service.
This is a global/international case not involving a specific country.[1][2][3][4][5][6]
About BitWhisk
"Bitcoin mixing, also referred to as Bitcoin tumbling or Bitcoin laundering, is the process of using a service like ours to break the connection between a Bitcoin sending and receiving address." "In the near future it may be simple for anyone- including friends, relatives, employers, and law enforcement, to track every Bitcoin transaction you’ve ever made and see exactly where it ended up. Breaking the connection between your addresses and the coins’ destination by mixing them is certainly a precaution that all Bitcoin users should take. You NEED to use a Bitcoin mixer to protect your privacy and safety."
"Virtual currency is part of the here and now, but with it comes the need to “guard your wallet.” BitWhisk’s high volume bitcoin mixer keeps your identity safe by offering premium mixing service with the ability to handle even the largest bitcoin transactions." "Cleans the coins instantly, you can set the time. After the intial transaction you send to BitWhisk has 1 confirmations, the coins will be cleaned and sent back to you with 1 transaction immediately. The process can take up to 48 hours."
"The mixer had been operating for less than a year before it was closed. Bitwhisk mixed only 3 BTC in that period of time with a much lower mixing reserve." "Closing after 5th November. If you want us to stay you may donate, we need around 0.05BTC to pay server's costs for the next 3 months."
"Bitwhisk.io closed business in 2018 but the website is online again with different design and intention. Probably a scammer bought the domain." "All of a sudden Bitwhisk.io is online again with domain information indicating that the domain was registered last July."
"Thanks to @o_e_l_e_o's sharp alertness. He discovered that the so called Bitcoin Tumble was forward the same address to different users which translates to pure scam."
"So I have just accessed this website from 3 different devices in 3 different browsers and on 3 different IPs, and entered a different addresses to "receive" my mixed coins to each time. On every single instance, it told me to send coins to the same address, and they would be mixed and sent back to the address I had entered."
"If anyone else would like to verify they are also shown the address above, then it pretty much confirms that this is a scam. A scam so poorly set up they couldn't even be bothered to generate a new address for each victim."
"The address has already started receiving money from victims."
This is a global/international case not involving a specific country.
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.
Include:
- Known history of when and how the service was started.
- What problems does the company or service claim to solve?
- What marketing materials were used by the firm or business?
- Audits performed, and excerpts that may have been included.
- Business registration documents shown (fake or legitimate).
- How were people recruited to participate?
- Public warnings and announcements prior to the event.
Don't Include:
- Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
- Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.
The Reality
This sections is included if a case involved deception or information that was unknown at the time. Examples include:
- When the service was actually started (if different than the "official story").
- Who actually ran a service and their own personal history.
- How the service was structured behind the scenes. (For example, there was no "trading bot".)
- Details of what audits reported and how vulnerabilities were missed during auditing.
What Happened
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
| Date | Event | Description |
|---|---|---|
| August 23rd, 2019 6:34:28 AM MDT | 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 $2,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?
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
- ↑ Bitwhisk.io 2.0 - Don't send you coins there. A scammer is behind the comeback. (Jan 11, 2022)
- ↑ https://archive.fo/qwb63 (Jan 13, 2022)
- ↑ @BitWhisk Twitter (Jan 13, 2022)
- ↑ Bitwhisk.io is online again. Is it a scam attempt by someone else or a comeback? (Jan 13, 2022)
- ↑ CoinMixer | Bitcoin Mixer | BestMixer | BitWhisk.io (Jan 13, 2022)
- ↑ WHY - Bitcoin Mixer | BitWhisk.io (Jan 13, 2022)