<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=Lazy_Lions_Discord_Hack</id>
	<title>Lazy Lions Discord Hack - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=Lazy_Lions_Discord_Hack"/>
	<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Lazy_Lions_Discord_Hack&amp;action=history"/>
	<updated>2026-06-01T20:21:28Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.1</generator>
	<entry>
		<id>https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Lazy_Lions_Discord_Hack&amp;diff=5113&amp;oldid=prev</id>
		<title>Azoundria: Created page with &quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/lazylionsdiscordhack.php}} {{Unattributed Sources}}  Lazy Lions WebsiteLazy Lions 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 in...&quot;</title>
		<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Lazy_Lions_Discord_Hack&amp;diff=5113&amp;oldid=prev"/>
		<updated>2023-10-16T17:38:30Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/lazylionsdiscordhack.php}} {{Unattributed Sources}}  &lt;a href=&quot;/cryptocurrencyhackscamfraudwiki/index.php?title=File:Lazylions.jpg&quot; title=&quot;File:Lazylions.jpg&quot;&gt;thumb|Lazy Lions Website&lt;/a&gt;Lazy Lions 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 in...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/lazylionsdiscordhack.php}}&lt;br /&gt;
{{Unattributed Sources}}&lt;br /&gt;
&lt;br /&gt;
[[File:Lazylions.jpg|thumb|Lazy Lions Website]]Lazy Lions 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.&lt;br /&gt;
&lt;br /&gt;
This is a global/international case not involving a specific country.&amp;lt;ref name=&amp;quot;interlockweb3twitter-9762&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;eggb0mbtwitter-9745&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;chox3twitter-9746&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;trickynftstwitter-9731&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;lukenamoptwitter-11916&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;nftherdertwitter-9748&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;lazylions-11926&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;lazylionsnfttwitter-11927&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;lazylions-11928&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;yugalabstwitter-11892&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== About Lazy Lions ==&lt;br /&gt;
&amp;quot;Welcome, fellow adventurers, to the world of Lazy Lions Lore, where we're crafting the next legendary universe together! Get ready to dive into a digital storytelling and world-building experience like no other.&lt;br /&gt;
Lazy Lions Lore, a cutting-edge platform powered by Legend Keeper, is here to redefine the way we tell stories. But here's the twist—it's not just the project doing the storytelling. We're inviting the incredible Lazy Lions community to join in, contribute, and shape the future of our universe. It's like an entire Lazy Lions encyclopedia, but way more interactive!&lt;br /&gt;
&lt;br /&gt;
embedded image&lt;br /&gt;
You, yes, YOU, get to co-write the next iconic story. Just think of the buzz when the character you helped create becomes as legendary as Harry Potter or Batman! We're not just building a digital wiki here. We're co-creating the next big thing, and it all starts with Lazy Lions Lore.&lt;br /&gt;
&lt;br /&gt;
Lazy Lions is all about us coming together, being the Kings and Queens of co-creation and digital ownership. But now, we're flipping the script on how entertainment works. No more of that 'chosen few' nonsense. We're giving every member the chance to shape our universe. From building landscapes to crafting epic backstories for your NFTs, Lazy Lions Lore hands you the keys.&lt;br /&gt;
&lt;br /&gt;
Our mission is to make our community the heart and soul of everything we do. We're not just telling stories; we're building a universe together. Imagine our tales becoming future TV shows, movies, or novels. It's not just exciting—it's revolutionary.&lt;br /&gt;
&lt;br /&gt;
Lazy Lions is all about collaboration and innovation and now, we're here to dominate the future of entertainment and digital ownership. So, if you've ever dreamed of leaving your mark on a sprawling universe, now's your chance. Jump into the Lazy Lions Lore and become part of something epic.&lt;br /&gt;
&lt;br /&gt;
To be part of the storytelling revolution, grab your Lazy Lions NFT on OpenSea and let's make history together. &amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;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.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This is a global/international case not involving a specific country.&lt;br /&gt;
&lt;br /&gt;
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.&lt;br /&gt;
&lt;br /&gt;
Include:&lt;br /&gt;
&lt;br /&gt;
* Known history of when and how the service was started.&lt;br /&gt;
* What problems does the company or service claim to solve?&lt;br /&gt;
* What marketing materials were used by the firm or business?&lt;br /&gt;
* Audits performed, and excerpts that may have been included.&lt;br /&gt;
* Business registration documents shown (fake or legitimate).&lt;br /&gt;
* How were people recruited to participate?&lt;br /&gt;
* Public warnings and announcements prior to the event.&lt;br /&gt;
&lt;br /&gt;
Don't Include:&lt;br /&gt;
* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.&lt;br /&gt;
* Anything that wasn't reasonably knowable at the time of the event.&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== The Reality ==&lt;br /&gt;
This sections is included if a case involved deception or information that was unknown at the time. Examples include:&lt;br /&gt;
&lt;br /&gt;
* When the service was actually started (if different than the &amp;quot;official story&amp;quot;).&lt;br /&gt;
* Who actually ran a service and their own personal history.&lt;br /&gt;
* How the service was structured behind the scenes. (For example, there was no &amp;quot;trading bot&amp;quot;.)&lt;br /&gt;
* Details of what audits reported and how vulnerabilities were missed during auditing.&lt;br /&gt;
&lt;br /&gt;
== What Happened ==&lt;br /&gt;
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.&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Key Event Timeline - Lazy Lions Discord Hack&lt;br /&gt;
!Date&lt;br /&gt;
!Event&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
|May 18th, 2022 3:22:00 AM MDT&lt;br /&gt;
|Twitter Post&lt;br /&gt;
|Unknown Twitter post.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Technical Details ==&lt;br /&gt;
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?&lt;br /&gt;
&lt;br /&gt;
== Total Amount Lost ==&lt;br /&gt;
The total amount lost is unknown.&lt;br /&gt;
&lt;br /&gt;
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?&lt;br /&gt;
&lt;br /&gt;
== Immediate Reactions ==&lt;br /&gt;
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?&lt;br /&gt;
&lt;br /&gt;
== Ultimate Outcome ==&lt;br /&gt;
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?&lt;br /&gt;
&lt;br /&gt;
== Total Amount Recovered ==&lt;br /&gt;
There do not appear to have been any funds recovered in this case.&lt;br /&gt;
&lt;br /&gt;
What funds were recovered? What funds were reimbursed for those affected users?&lt;br /&gt;
&lt;br /&gt;
== Ongoing Developments ==&lt;br /&gt;
What parts of this case are still remaining to be concluded?&lt;br /&gt;
== Individual Prevention Policies ==&lt;br /&gt;
{{Prevention:Individuals:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Individuals:End}}&lt;br /&gt;
&lt;br /&gt;
== Platform Prevention Policies ==&lt;br /&gt;
{{Prevention:Platforms:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Platforms:End}}&lt;br /&gt;
&lt;br /&gt;
== Regulatory Prevention Policies ==&lt;br /&gt;
{{Prevention:Regulators:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Regulators:End}}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references&amp;gt;&amp;lt;ref name=&amp;quot;interlockweb3twitter-9762&amp;quot;&amp;gt;[https://twitter.com/interlockweb3/status/1526893044095664128 @interlockweb3 Twitter] (Nov 24, 2022)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;eggb0mbtwitter-9745&amp;quot;&amp;gt;[https://twitter.com/eggb0mb_/status/1513443469406183425 @eggb0mb_ Twitter] (Nov 24, 2022)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;chox3twitter-9746&amp;quot;&amp;gt;[https://twitter.com/CHOX3__/status/1519240898437328898 @CHOX3__ Twitter] (Nov 24, 2022)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;trickynftstwitter-9731&amp;quot;&amp;gt;[https://twitter.com/Tricky_NFTs/status/1526849651546144769 @Tricky_NFTs Twitter] (Nov 24, 2022)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;lukenamoptwitter-11916&amp;quot;&amp;gt;[https://twitter.com/lukenamop/status/1526855836315918336 @lukenamop Twitter] (Nov 24, 2022)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;nftherdertwitter-9748&amp;quot;&amp;gt;[https://twitter.com/NFTherder/status/1531307520366632964 @NFTherder Twitter] (Nov 24, 2022)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;lazylions-11926&amp;quot;&amp;gt;[https://lazylions.ai/ Lazy Lions] (Sep 19, 2023)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;lazylionsnfttwitter-11927&amp;quot;&amp;gt;[https://twitter.com/LazyLionsNFT/ @LazyLionsNFT Twitter] (Sep 19, 2023)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;lazylions-11928&amp;quot;&amp;gt;[https://lazylions.ai/lore/ Lazy Lions - Lore] (Sep 19, 2023)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;yugalabstwitter-11892&amp;quot;&amp;gt;[https://twitter.com/yugalabs/status/1549157338665336839 @yugalabs Twitter] (Sep 20, 2023)&amp;lt;/ref&amp;gt;&amp;lt;/references&amp;gt;&lt;/div&gt;</summary>
		<author><name>Azoundria</name></author>
	</entry>
</feed>