PancakeHunny Liquidity Pool Drained

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!

PancakeHunny

The PancakeHunny smart contract had an exploit in the rewards mechanism, which allowed the attacker to mint additional Hunny which was not intended.

This is a global/international case not involving a specific country.

About PancakeHunny

"PancakeHunny aims to provide users the easiest way to join the bandwagon of the DeFi world, built on top of PancakeSwap, giving you the tastiest CAKEs topped with HUNNY. We support the underlying DeFi technology and ecosystem to compound user yields through the Binance Smart Chain (BSC). We have seen a huge surge in DeFi activity in 2020 since the rise of Yield Aggregator projects on different blockchain networks with existing protocols such as MakerDAO, Aave, Compound, and etc. As a Yield Aggregator with a vital role in the yield farming economy, we are leveraging different DeFi protocols and strategies to maximize user profits."

"On 3rd June 2021, at 1:46 UTC. A smart contract was created to exploit the Hunny Minter Smart Contract. The Contract was subsequently executed 91 times." "According to official sources, PancakeHunny on BSC was attacked by hackers, and the hackers made 43 ETH (a total of more than 100,000 US dollars). PancakeHunny forked from PancakeBunny, and the attack suffered this time was similar to PancakeBunny. Hackers obtained a large amount of HUNNY tokens and threw them to the market, causing the price of HUNNY tokens to plummet." "A lot of Hunny tokens [were] minted out and dumped, the hacker has taken out 38.9 ETH."

"Attacker deployed a contract and added 0.5 BNB from an external wallet address: 0x6be5a267b04e9f24cdc1824fd38d63c436be91ab" "This is the sequence of events: (1) wBNB Swap CAKE from PancakeSwap. (2) Sent CAKE to HUNNY Minter Smart Contract. (3) Added CAKE-BNB Liquidity from PancakeSwap. (4) Deposited CAKE-BNB LP tokens to CAKE-BNB Hive. (5) Redeemed HUNNY Rewards. (6) Swap Cake Balance to HUNNY-BNB, increase CAKE Balance as per #2. (7) Exploited and increased 2,281,142.448 HUNNY supply." "Attacker converted all remaining wBNB into ETH and was sent to an external wallet address: 0x2E5Ea63d69b2ed33C869eED58433f0F799E1F7AA"

"Exploiter’s wallet address: 0x0ef50be29c82ecf2158ec1886dc6692a2b0db411" "Total exploited transactions: 100" "Total BNB gained by the attacker: 216 BNB"

"We have stopped the minting process. Hives are all SAFU." "Since the minter was switched off, we were unable to allocate HUNNY profits to the respective Hives."

"None of the Bunny and Bunny fork attacks is a Flash Loan attack. They are Performance Fee Minting Attacks. They just often get amplified/made easier with Flash Loans. These attacks are made possible by one or more logic bugs in the Performance Fee Minting process."

"The core issue is: it’s taking all the wallet balance to create the LP tokens which will later be used for profit calculation and minting. Same old bug as the two of the previous hacks."

"We have taken immediate action to protect our users from any further potential issues that could arise. All Hives are unaffected. Funds are SAFU. The exploit only affects the Prices of Hunny/BNB." "We have since changed the logic behind the HUNNY Minter, whereby it will only mint HUNNY based on the profits received from vaults."

"Due to the nature of the attack, users who have staked in our HUNNY Hive should observe an increase in the profit as well as an increase in the unlocked HUNNY amount. This is because our Minter also distributed more profits to the HUNNY Hive. In short, other than a price dip, our users are actually benefitting from the higher profits (wBNB) gained from Hunny Hive." "We’ve [also] taken the chance to restructure our internal processes. This has made us stronger and more resilient than ever before."

"We'd like to express our gratitude to our partner @WatchPug_ for keeping a lookout for us since our launch. We will continue to strengthen the security of our smart contracts as we have always endeavored."

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.

Key Event Timeline - PancakeHunny Liquidity Pool Drained

Date	Event	Description
June 2nd, 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 $100,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 do not appear to have been any assets lost here. The only impact was that the price of the Hunny token dropped.

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.