AutoShark Finance Swap Mining Vulnerability: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
[[File:Autoshark.jpg|thumb|AutoShark Finance]]A user was incentivized to make a large trade on the AutoShark platform based on the rebate program, which contributed heavily to the market volatility. It's unclear if there was an overall loss of any investor funds. | [[File:Autoshark.jpg|thumb|AutoShark Finance]]A user was incentivized to make a large trade on the AutoShark platform based on the rebate program, which contributed heavily to the market volatility. It's unclear if there was an overall loss of any investor funds. | ||
This is a global/international case not involving a specific country. | This is a global/international case not involving a specific country.<ref name="autosharkdocsarchive-1287" /><ref name="openblocksecgithub-2342" /><ref name="autosharkdocs-4179" /><ref name="peckshieldtwitter-4180" /><ref name="bscscan-4181" /><ref name="autosharkfintwitter-4182" /><ref name="slowmisthacked-3823" /><ref name="autosharkfintwitter-4538" /> | ||
<ref name="autosharkdocsarchive-1287" /><ref name="openblocksecgithub-2342" /><ref name="autosharkdocs-4179" /><ref name="peckshieldtwitter-4180" /><ref name="bscscan-4181" /><ref name="autosharkfintwitter-4182" /><ref name="slowmisthacked-3823" /><ref name="autosharkfintwitter-4538" /> | |||
== About AutoShark Finance == | == About AutoShark Finance == | ||
| Line 69: | Line 68: | ||
!Description | !Description | ||
|- | |- | ||
|October 1st, 2021 | |October 1st, 2021 | ||
|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 77: | Line 76: | ||
| | | | ||
|} | |} | ||
== 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 96: | Line 98: | ||
== 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 19:49, 3 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!
A user was incentivized to make a large trade on the AutoShark platform based on the rebate program, which contributed heavily to the market volatility. It's unclear if there was an overall loss of any investor funds.
This is a global/international case not involving a specific country.[1][2][3][4][5][6][7][8]
About AutoShark Finance
"AutoShark [started as] a yield optimizer for Automatic Liquidity Acquisition Farms & AMMs on the Binance Smart Chain. It is forked from PancakeBunny, and offers unparalleled access to farming opportunities through the use of superior yield strategies and auto-compounding vaults." "Autoshark was nearly [a] 1:1 fork of PancakeBunny."
"Amidst the numerous rug pulls that have happened over the past month, it will be inevitable that some investors will fall for the scams even if they have a favorite yield optimizer platform to be on. At AutoShark, we make sure to work only with the most established projects so yield farmers can have peace of mind when their assets are with us."
"AutoShark Finance is the 1st Hybrid AMM and Yield Optimizer, offering unparalleled access to farming opportunities through the use of superior yield strategies, auto-compounding vaults, and NFT-powered farming." "The goal of AutoShark is to build the number 1 most sustainable AMM + DEX and Yield Optimizer on the Binance Smart Chain." "To do so, we seek to capture interest through our aggregation of decentralized exchange swap systems and yield optimizing strategies."
"AutoShark has grown from being a yield optimizer to a project that focuses on building an entire ecosystem of sustainable DEFI products to help you get the safest and best possible yields on your cryptocurrency portfolio. We welcome cryptocurrency advocates from all walks of life, and present the following features for every different profile."
"The swap mining feature was exploited in a flurry of txs to gain the reward of 3.18M FINS tokens, which are then immediately swapped to 1,388 BNB (with roughly $581K)."
"The hack is made possible due to the relatively low pool liquidity so that the hacker can use flashloans to occupy the majority of pool share (to recover swap loss/fee) while still enjoy the sizable "swap fee reward” (increased from each huge swap)."
"To illustrate, we use one example hack tx with 100+ swaps back-and-forth to get 15K FINS rewards, which are then swapped to get 121 BNB as profit. Note the swap fee is still largely obtained by the hacker due to the owned majority pool share." "he hacker repeats the above steps seven times and gains in total 1,388 BNBs (with ~$580K). The initial hack funds are transferred from @TyphoonCrypto and the final gains are transferred out to Ethereum via @AnyswapNetwork."
"Interesting, it seems the @AutoSharkFin platform charges 0.3% swap fees with a portion being sent to holders of #FINS as dividends. The hacker sold native tokens for ~$581k, while the platform gained ~$920k for buyback and fees redistribution."
"In short, the user basically did a huge trade on our platform, paying us huge amount of fees & minting equivalent amount of $FINS. As part of our tokenomics, the fees collected are used to form LP that will be deposited into the FINS dividend pool for users as rewards."
"We have also used $FINS from our own dev treasury to form FINS LP that is being sent to the $FINS dividend pool. Therefore, our $FINS holders will gain more than $920,000 in rewards!"
"Moving forward, we will be placing a hard cap of trading fee rebates based on the total daily trading volume on our platform. So users can't do huge trades that will create volatility in our system (like what we have just seen)."
For example, "our trading volume is averaging $9-10mil volume now and upon hitting a cap at around $20mil total trading volume, we will pause the trading rebates and resume the following day."
"Our APY for $FINS dividend pool has increased significantly from the increase in rewards that is attributed to the large volume of trading fees!"
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 |
|---|---|---|
| October 1st, 2021 | 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 $581,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
- ↑ What is AutoShark.Finance? - AutoShark (Jun 13, 2021)
- ↑ blocksec-incidents/2021.md at main · openblocksec/blocksec-incidents · GitHub (Aug 11, 2021)
- ↑ AutoShark Intro - AutoShark (Dec 5, 2021)
- ↑ @peckshield Twitter (Dec 5, 2021)
- ↑ https://bscscan.com/tx/0x640ce34ce69ff5a034edc6df6e43fd80cc08d02a36d262e131d37ead990fff29 (Dec 5, 2021)
- ↑ @AutoSharkFin Twitter (Dec 5, 2021)
- ↑ SlowMist Hacked - SlowMist Zone (Nov 6, 2021)
- ↑ @AutoSharkFin Twitter (Dec 17, 2021)