Monkey Kingdom Additional Minting Hack

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!

Monkey Kingdom

The Monkey Kingdom NFT project reported that there was a "hack" which happened during their presale, allowing some users to mint more than 1 Baepe. They proceeded to relaunch a new collection, and promised to reimburse all participants in the original collection. The Tweet was later deleted and the outcome is unclear.

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

About Monkey Kingdom

"Monkey Kingdom is one of the known “Bluechip” projects in Solana NFT space, currently sitting at 45 SOL FP, but reaching the floor price up to 100 SOL (~$18,000)."

"Monkey Kingdom's first collection (Gen 1) - 2,222 uniquely generated 32x32 pixels NFTs on the Solana Blockchain. Daily $PEACH token airdrop, staking, breeding, metaverse development and real world exclusive meet-ups and merch collabs. Gen 2 - Diamond Baepes (on Solana) Gen 3 - Monkey Legends (on Ethereum)"

"There was a scheduled party with Steve Aoki to celebrate the new minting collection."

"After investigation, we have confirmed a hack happened during our presale minting session causing some people being able to mint more than 1 Baepe. We'll follow up the situation with the procedures below:"

"1) ALL Minted Baepes will be refunded, when it is sent back to us." "2) The entirety of the current set will be cancelled, we will launch a new identical collection of Baepes." "3) ALL whitelisted wallets will be airdropped one Baepe from the new collection (1301 wallets in total)." "4) The rest will follow the procedure as usual (i.e. 3-to-1 Aurdrops, Main Sale)." "5) 1 mint per wallet in the Main Sale will be removed." "The old collection will not be verified and will not be tradeable / viewable on any marketplaces."

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 - Monkey Kingdom Additional Minting Hack

Date	Event	Description
December 21st, 2021 8:58:00 AM MST	Monkey Kingdom Tweet	Monkey Kingdom reports the hack in a tweet.

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 is unknown.

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

The total amount recovered is unknown.

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.