Moonhere "Fair Launch" Exit Scam

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!

Moonhere

Moonhere used the right buzzwords, claiming to be a fair launch, audited, and incapable of rugging. Despite the warnings from CertiK, many participants even still denied the concerns. Shortly thereafter, $110k of liquidity was pulled from the contract. The website and social media are gone.

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

About Moonhere

"The next generation BNB Yield Protocol." "Moonhere brings the newest and revolutionary mechanism to the Binance Smart Chain ecosystem. Earn $BNB just by holding $MORE token while Stake $BNB to earn more reward. 6,000+ Holders Right Now." "MoonHERE will be fairlaunch at 20/4 0700 AM UTC."

"Buy here (recommend 11.5%-13% slippage)." "[V]erified contract." "LP lock proof." "Burn 15% of total token." "This is the 5% txn tax and our lp token is automatically locked. We will not and CANNOT rug. If in doubt, please try to deploy liquidity and then swap back to test."

"For only 8 hours, we have already reached 7000+ holder. Thanks everyone! We have some maintenance chores to do and also updated some useful link, including Audit report. in docs. We will have more promotions incoming."

"WarOnRug claims this guy drained 300 BNB from reward pool. If you check on the transactions you can see this guy split his moonrat into several contract for selling them at the same time. He didn't claim any BNB from the reward pools. It is all his possessed moonrat dumping. We double checked the contract and everything is automated, no value can be modified through external. Your fund is SAFU!"

"Community alert published on https://certik.org about a project called Moonhere that is likely to exit scam once the pre-sale ends. Investigation indicates that the scam group behind may be identical to Cryptoption (alerted before). Please do not engage and stay vigilant."

"Lol, they have'nt a presale its pure community fairlaunch." "They are fairlaunch not presale lmao, what a joke again?" "There was no pre-sale it was fair launch? @certikorg please double or triple check again." "There was no pre-sale ... I don't understand what they're talking about! Well I think CERTIK no longer even knows what it checks ..." "Let's mass report certik" "Certik now not just a paid auditor, also paid fudder" "Unfollow done stupid certik!!!!"

"To avoid confusion, Moonhere is running a fair launch, but similar to the Cryptoption Exit Scam, users’ #BNB will be sent to the below unverified contract via its dApp. The evidence shows that Moonhere is associated with the same group behind Cryptoption."

"The screenshot shows that users funds collected through Moonhere’s fair launch will be sent to [an] unverified contract. Cryptoption Exit Scam, associated with Moonhere, also collected users’ funds through an unverified contract."

"Two hours after CertiK’s first alert, Moonhere has drained ~$110,000 worth of #BNB (192.74) from the fair-launch contract. CertiK will continue to monitor the situation."

"[M]e and my friend were scammed 5bnb. and a lot of people have been scammed tens of thousands of dollars."

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 - Moonhere "Fair Launch" Exit Scam

Date	Event	Description
April 20th, 2021 4:17:23 PM 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 $110,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

Having independent reviews required for a project to launch can easily prevent cases like this.

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.