<?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=Renzo_Protocol_Discord_Account_Compromise</id>
	<title>Renzo Protocol Discord Account Compromise - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=Renzo_Protocol_Discord_Account_Compromise"/>
	<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Renzo_Protocol_Discord_Account_Compromise&amp;action=history"/>
	<updated>2026-05-30T06:44:10Z</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=Renzo_Protocol_Discord_Account_Compromise&amp;diff=6273&amp;oldid=prev</id>
		<title>Azoundria: Created page with &quot;{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/renzoprotocoldiscordaccountcompromise.php}} {{Unattributed Sources}}  Renzo Protocol Logo/HomepageRenzo Protocol is designed to assist users who with to restake their assets. Restaking allows for a passive return on the restaked funds. Renzo promises to make the process very easy for users, removing much of the complexity that would typically be involved....&quot;</title>
		<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Renzo_Protocol_Discord_Account_Compromise&amp;diff=6273&amp;oldid=prev"/>
		<updated>2024-10-25T19:57:49Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/renzoprotocoldiscordaccountcompromise.php}} {{Unattributed Sources}}  &lt;a href=&quot;/cryptocurrencyhackscamfraudwiki/index.php?title=File:Renzoprotocol.jpg&quot; title=&quot;File:Renzoprotocol.jpg&quot;&gt;thumb|Renzo Protocol Logo/Homepage&lt;/a&gt;Renzo Protocol is designed to assist users who with to restake their assets. Restaking allows for a passive return on the restaked funds. Renzo promises to make the process very easy for users, removing much of the complexity that would typically be involved....&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 With About|source=https://www.quadrigainitiative.com/casestudy/renzoprotocoldiscordaccountcompromise.php}}&lt;br /&gt;
{{Unattributed Sources}}&lt;br /&gt;
&lt;br /&gt;
[[File:Renzoprotocol.jpg|thumb|Renzo Protocol Logo/Homepage]]Renzo Protocol is designed to assist users who with to restake their assets. Restaking allows for a passive return on the restaked funds. Renzo promises to make the process very easy for users, removing much of the complexity that would typically be involved. On July 22nd, a few days after posting a tweet highlighting a focus on security, the Renzo Protocol announced that their Discord account had been hacked. There doesn't appear to have been any follow up tweets to notify that the Discord has been restored or provide any plans to compensate users who may have been affected.&amp;lt;ref name=&amp;quot;slowmisthackedarchive-14997&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;renzoprotocoltwitter-14998&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;renzoprotocoltwitter-14999&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;renzoprotocol-15000&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;renzoprotocoldocs-15001&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;renzoprotocntwitter-15002&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;thecryptonexustwitter-15003&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;bitcoinzhang1twitter-15004&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;cryptotimesiotwitter-15005&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;cryptoomotwitter-15006&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;cyclepiratetwitter-15007&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;leviathannewstwitter-15008&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;btchamsterstwitter-15009&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;nftchainstwitter-15010&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;coinnessgltwitter-15011&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;renzoprotocntwitter-15012&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;globalcnnewstwitter-15013&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;cryptototemtwitter-15014&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;henxdefitwitter-15015&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;lecryptodailytwitter-15016&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;gncryptonewstwitter-15017&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;cryptomageyttwitter-15018&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;thegivemebittwitter-15019&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;asmari71127twitter-15020&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== About Renzo Protocol ==&lt;br /&gt;
&amp;quot;Liquid Restaking made ezpz&amp;quot; &amp;quot;Experience the power of Renzo by exploring the wide range of integrated chains and dApps. Discover new possibilities and unlock the potential of decentralized applications with Renzo.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Renzo is a strategy manager and liquid restaking token provider for both EigenLayer and Symbiotic. Renzo's $ezETH and $pzETH serve as the interface to the EigenLayer and Symbiotic ecosystems, respectively. The mission of $ezETH and $pzETH is to secure Actively Validated Services and generate both staking and restaking rewards.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Restake from your favorite Ethereum Rollup&amp;quot; &amp;quot;Renzo's decentralized portfolio manager rebalances for the optimal risk-reward strategies&amp;quot; &amp;quot;Get liquid with Renzo across your favorite DeFi projects&amp;quot; &amp;quot;Passively capture staking and restaking rewards&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Trust Renzo's robust security framework made of institutional grade node operators and the top tier security partners&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Renzo always prioritizes security first!&lt;br /&gt;
&lt;br /&gt;
This culture extends into Renzo's core mission in being the safest and most reliable restaking protocol!&amp;quot;&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;
&amp;quot;The liquidity restaking protocol Renzo tweeted that the Renzo Discord server has been compromised by malicious attackers. Please do not click on any links posted in the server.&amp;quot;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Key Event Timeline - Renzo Protocol Discord Account Compromise&lt;br /&gt;
!Date&lt;br /&gt;
!Event&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
|July 19th, 2024 12:48:00 AM MDT&lt;br /&gt;
|Security First Post&lt;br /&gt;
|The Renzo Protocol team tweets about how they always prioritize security first to be &amp;quot;the safest and most reliable restaking protocol&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|July 22nd, 2024 4:55:00 AM MDT&lt;br /&gt;
|Crypto_omo Tweet&lt;br /&gt;
|Community member Crypto_omo notes that the Discord has been breached. Apparently this insight came from zachxbt, although the original communication cannot be located in a tweet.&lt;br /&gt;
|-&lt;br /&gt;
|July 22nd, 2024 5:00:00 AM MDT&lt;br /&gt;
|Renzo Protocol Tweet&lt;br /&gt;
|The Renzo Protocol tweets to warn the community about their Discord channel being breached by malicious actors, and that all communication from server admins should be considered to be potentialyl dangerous.&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;
&amp;quot;Our Renzo Discord server has been compromised by malicious actors. Please refrain from clicking any links posted in the server.&lt;br /&gt;
&lt;br /&gt;
At this time, treat all messages and links from server admins as potentially dangerous. Consider all communication within the server potentially harmful until further notice. We appreciate your patience as we work to secure the platform.&amp;quot;&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;slowmisthackedarchive-14997&amp;quot;&amp;gt;[https://web.archive.org/web/20240819162123/https://hacked.slowmist.io/?c=&amp;amp;page=2 SlowMist Hacked - SlowMist Zone] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;renzoprotocoltwitter-14998&amp;quot;&amp;gt;[https://twitter.com/renzoprotocol/status/1815341217414357311 @renzoprotocol Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;renzoprotocoltwitter-14999&amp;quot;&amp;gt;[https://twitter.com/RenzoProtocol/status/1814190519779557480 @RenzoProtocol Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;renzoprotocol-15000&amp;quot;&amp;gt;[https://www.renzoprotocol.com/ Renzo Protocol - Liquid Restaking] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;renzoprotocoldocs-15001&amp;quot;&amp;gt;[https://docs.renzoprotocol.com/docs Overview | Renzo Protocol] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;renzoprotocntwitter-15002&amp;quot;&amp;gt;[https://twitter.com/RenzoProto_CN/status/1815343036991160464 @RenzoProto_CN Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;thecryptonexustwitter-15003&amp;quot;&amp;gt;[https://twitter.com/TheCryptoNexus/status/1815353137110147479 @TheCryptoNexus Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;bitcoinzhang1twitter-15004&amp;quot;&amp;gt;[https://twitter.com/bitcoinzhang1/status/1815342813753561457 @bitcoinzhang1 Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;cryptotimesiotwitter-15005&amp;quot;&amp;gt;[https://twitter.com/CryptoTimes_io/status/1815349388304060774 @CryptoTimes_io Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;cryptoomotwitter-15006&amp;quot;&amp;gt;[https://twitter.com/Crypto_omo/status/1815339889660998118 @Crypto_omo Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;cyclepiratetwitter-15007&amp;quot;&amp;gt;[https://twitter.com/CyclePirate/status/1815390765524152362 @CyclePirate Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;leviathannewstwitter-15008&amp;quot;&amp;gt;[https://twitter.com/leviathan_news/status/1815541157293896163 @leviathan_news Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;btchamsterstwitter-15009&amp;quot;&amp;gt;[https://twitter.com/btc_hamsters/status/1815348091320701180 @btc_hamsters Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;nftchainstwitter-15010&amp;quot;&amp;gt;[https://twitter.com/nftchains/status/1815341100132905295 @nftchains Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;coinnessgltwitter-15011&amp;quot;&amp;gt;[https://twitter.com/CoinnessGL/status/1815348202570486251 @CoinnessGL Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;renzoprotocntwitter-15012&amp;quot;&amp;gt;[https://twitter.com/RenzoProto_CN/status/1815618190270947465 @RenzoProto_CN Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;globalcnnewstwitter-15013&amp;quot;&amp;gt;[https://twitter.com/GlobalCNNews/status/1815418385628377433 @GlobalCNNews Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;cryptototemtwitter-15014&amp;quot;&amp;gt;[https://twitter.com/CryptoTotem/status/1815368338568093862 @CryptoTotem Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;henxdefitwitter-15015&amp;quot;&amp;gt;[https://twitter.com/henx_DeFi/status/1815339800456548573 @henx_DeFi Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;lecryptodailytwitter-15016&amp;quot;&amp;gt;[https://twitter.com/LeCryptoDaily/status/1815346733452587302 @LeCryptoDaily Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;gncryptonewstwitter-15017&amp;quot;&amp;gt;[https://twitter.com/GNcrypto_news/status/1815374678967353460 @GNcrypto_news Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;cryptomageyttwitter-15018&amp;quot;&amp;gt;[https://twitter.com/CryptoMage_YT/status/1815336308815876421 @CryptoMage_YT Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;thegivemebittwitter-15019&amp;quot;&amp;gt;[https://twitter.com/theGiveMeBit/status/1815472462806802586 @theGiveMeBit Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;asmari71127twitter-15020&amp;quot;&amp;gt;[https://twitter.com/asmari71127/status/1815097687647179169 @asmari71127 Twitter] (Accessed Aug 19, 2024)&amp;lt;/ref&amp;gt;&amp;lt;/references&amp;gt;&lt;/div&gt;</summary>
		<author><name>Azoundria</name></author>
	</entry>
</feed>