Wild Credit Minting Exploit
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!
An exploit in the smart contract allowed anyone to take over the contract.
A malicious actor attempted to exploit, however another front-running bot saw the transaction and ran it with a higher fee to bypass them. The front-runner returned the funds to the contract developers, where they were distributed back to affected users.
This is a global/international case not involving a specific country.[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16]
About Wild Credit
"Wild.credit is an upcoming lending protocol with isolated lending pairs." "Wild is a permissionless lending protocol featuring isolated lending pairs. Lenders supply assets into any of the lending pairs to earn interest. Borrowers pay interest to borrow while collateralizing their loans. The protocol earns an interest rate spread."
"Using isolated lending pairs, lenders can decide which pairs they are comfortable with and provide liquidity only to those. Just like on Uniswap, users of Wild Credit are also free to create lending pairs for any asset permissionlessly."
"The DeFi protocol Wild Credit on Ethereum suffered a white hat attack."
"A potential irregularity on the BNT-ETH pair" "We've discovered a potential irregularity on the BNT-ETH pair. All deposits have been disabled while the investigation is in progress. As a precaution, please withdraw your funds."
"[A]nyone can call the `initialize` function to become the owner of the LP token contract. The owner can freely mint and burn LP tokens. The hacker took ownership of the contract, minted a bunch of tokens to themselves, and then used those fake tokens to withdraw real funds."
"Preliminary results show that BNT-ETH was the only exploited pool. Total amount is 125,585 BNT (~ $637k)."
"The "attacker" who returned the funds was actually an operator of a generalized front-running bot. The real attacker attempted to execute their exploit here and was front-run." "[T]he attacker has returned a total of $650,000."
"We've finished reconstructing the deposit balances. Please review it to see if your deposit amount looks correct. To make sure we haven't missed anyone, we'll wait 24 hours before sending the balances."
"All funds have been returned now. Please check your wallet. If you made a deposit with ETH, you should have WETH balance now instead. WETH is a token representation of ETH which can be unwrapped 1:1 back to ETH on Uniswap."
"NEW BUG BOUNTY: @WildCredit is live now with their Immunefi Bug Bounty program! Wild Credit: decentralized lending protocol with isolated lending pairs. Go wild on your bug bounty hunting and earn $20,000:"
"$10k has been awarded to @Mudit__Gupta for finding a bug in the RewardDistribution contract involving snapshotAccount function which would lead to the loss of all stored rewards. The bounty remains open for all other qualified bugs."
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 |
|---|---|---|
| May 27th, 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 $637,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
While there are lots of additional precautions that smart contracts can take including security audits, bug bounties, and careful design practices, it is impossible to prove that a complex smart contract is secure. The safest storage of funds is an offline multi-signature wallet held by known people.
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
- ↑ SlowMist Hacked - SlowMist Zone (May 18, 2021)
- ↑ Introduction - Wild Credit (Jul 14, 2021)
- ↑ Announcing Wild Credit Borrow Or Lend Any Token (Jul 14, 2021)
- ↑ @WildCredit Twitter (Jul 14, 2021)
- ↑ @WildCredit Twitter (Jul 14, 2021)
- ↑ @WildCredit Twitter (Jul 14, 2021)
- ↑ @WildCredit Twitter (Jul 14, 2021)
- ↑ @WildCredit Twitter (Jul 14, 2021)
- ↑ Ethereum Transaction Hash (Txhash) Details | Etherscan (Jul 14, 2021)
- ↑ Ethereum Transaction Hash (Txhash) Details | Etherscan (Jul 14, 2021)
- ↑ @WildCredit Twitter (Jul 14, 2021)
- ↑ @WildCredit Twitter (Jul 14, 2021)
- ↑ @Mudit__Gupta Twitter (Jul 14, 2021)
- ↑ No Title (Jul 24, 2021)
- ↑ blocksec-incidents/2021.md at main · openblocksec/blocksec-incidents · GitHub (Aug 11, 2021)
- ↑ @_anishagnihotri Twitter (Aug 11, 2021)