Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/hapesocialdiscordhacked.php}} {{Unattributed Sources}} HAPE WebsiteHAPE was reportedly among those projects affected by a breach on their Discord servers. These typically promised an enticing mint in order to convince followers to provide full wallet authorization. Once the wallet was authorized, it would be emptied. This is a global/international case not involving a s..."

2023-10-16T17:31:49Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/hapesocialdiscordhacked.php}} {{Unattributed Sources}} thumb|HAPE WebsiteHAPE was reportedly among those projects affected by a breach on their Discord servers. These typically promised an enticing mint in order to convince followers to provide full wallet authorization. Once the wallet was authorized, it would be emptied. This is a global/international case not involving a s..."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/hapesocialdiscordhacked.php}}
{{Unattributed Sources}}

[[File:Hapenft.jpg|thumb|HAPE Website]]HAPE was reportedly among those projects affected by a breach on their Discord servers. These typically promised an enticing mint in order to convince followers to provide full wallet authorization. Once the wallet was authorized, it would be emptied.

This is a global/international case not involving a specific country.<ref name="interlockweb3twitter-9762" /><ref name="eggb0mbtwitter-9745" /><ref name="chox3twitter-9746" /><ref name="trickynftstwitter-9731" /><ref name="ryukdevtwitter-11906" /><ref name="lukenamoptwitter-9733" /><ref name="nftherdertwitter-9748" /><ref name="hape-11907" /><ref name="opensea-11908" /><ref name="yugalabstwitter-11892" /><ref name="hapebeastsnft-11909" />

== About HAPE Social ==
"HIGH-FASHION HAPES" "FULLY 3D AND READY TO REDEFINE DIGITAL FASHION" "DISCOVER 8192 UNIQUE BEAUTIFUL HAPES"

"Street fashion, your style" "Switch up your HAPE's clothing with digital drops, rank up on the Fashion Index and build your look for the metaverse." "RUN THE HAPEWALK Take to the runway and show off your collection. Become a HAPEFLUENCER and reap the real-world rewards."

"We've released our 2ND variant of our Hape which includes extra holder benefits. What to look our for: Daily community sneak-peeks for new utility. Free merch drops. Special HODL'er Discord chat. This mint is exclusive to our Discord community, and we have many-many more things awaiting all of you! For Hapes, by Hapes. Mint: FREE Supply: 1000 Mint here: https://hapebeastsnft.org/"

"Once you interact with these fake bots they will snag your discord token, giving them instant access to your account without 2FA or your password."

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.
{| class="wikitable"
|+Key Event Timeline - HAPE Social Discord Hacked
!Date
!Event
!Description
|-
|May 18th, 2022 12:25:00 AM MDT
|Twitter Post
|Unknown Twitter post.
|}

== 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 ==
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 ==
{{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><ref name="interlockweb3twitter-9762">[https://twitter.com/interlockweb3/status/1526893044095664128 @interlockweb3 Twitter] (Nov 24, 2022)</ref>

<ref name="eggb0mbtwitter-9745">[https://twitter.com/eggb0mb_/status/1513443469406183425 @eggb0mb_ Twitter] (Nov 24, 2022)</ref>

<ref name="chox3twitter-9746">[https://twitter.com/CHOX3__/status/1519240898437328898 @CHOX3__ Twitter] (Nov 24, 2022)</ref>

<ref name="trickynftstwitter-9731">[https://twitter.com/Tricky_NFTs/status/1526849651546144769 @Tricky_NFTs Twitter] (Nov 24, 2022)</ref>

<ref name="ryukdevtwitter-11906">[https://twitter.com/ryuk_dev/status/1526811117787287553 @ryuk_dev Twitter] (Nov 24, 2022)</ref>

<ref name="lukenamoptwitter-9733">[https://twitter.com/lukenamop/status/1526855835527303171 @lukenamop Twitter] (Nov 24, 2022)</ref>

<ref name="nftherdertwitter-9748">[https://twitter.com/NFTherder/status/1531307520366632964 @NFTherder Twitter] (Nov 24, 2022)</ref>

<ref name="hape-11907">[https://www.hape.io/ HAPE PRIME] (Sep 19, 2023)</ref>

<ref name="opensea-11908">[https://opensea.io/collection/hapeprime https://opensea.io/collection/hapeprime] (Sep 19, 2023)</ref>

<ref name="yugalabstwitter-11892">[https://twitter.com/yugalabs/status/1549157338665336839 @yugalabs Twitter] (Sep 20, 2023)</ref>

<ref name="hapebeastsnft-11909">[https://hapebeastsnft.org/ https://hapebeastsnft.org/] (Sep 20, 2023)</ref></references>

HAPE Social Discord Hacked - Revision history