Renzo Protocol Discord Account Compromise

Notice: This page is a freshly imported case study from an original repository. While the original content had a similar format, some sections may not have been fully completed. Please help fill in any empty sections or any missing information 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!

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.

About Renzo Protocol

"Liquid Restaking made ezpz" "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."

"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."

"Restake from your favorite Ethereum Rollup" "Renzo's decentralized portfolio manager rebalances for the optimal risk-reward strategies" "Get liquid with Renzo across your favorite DeFi projects" "Passively capture staking and restaking rewards"

"Trust Renzo's robust security framework made of institutional grade node operators and the top tier security partners"

"Renzo always prioritizes security first!

This culture extends into Renzo's core mission in being the safest and most reliable restaking protocol!"

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 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."

Key Event Timeline - Renzo Protocol Discord Account Compromise

Date	Event	Description
July 19th, 2024 12:48:00 AM MDT	Security First Post	The Renzo Protocol team tweets about how they always prioritize security first to be "the safest and most reliable restaking protocol".
July 22nd, 2024 4:55:00 AM MDT	Crypto_omo Tweet	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.
July 22nd, 2024 5:00:00 AM MDT	Renzo Protocol Tweet	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.

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

"Our Renzo Discord server has been compromised by malicious actors. Please refrain from clicking any links posted in the server.

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."

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

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.