How much was lost in the SudoRare hack?

The SudoRare hack resulted in $883K in losses on August 23, 2022.

What attack technique was used in the SudoRare exploit?

The SudoRare exploit utilized Drained Contracts / Rugpull. Understanding this attack vector is critical for smart contract auditors and developers building secure DeFi protocols.

How can developers prevent similar smart contract attacks?

Preventing smart contract hacks requires a combination of secure coding practices, thorough security audits, and understanding common attack vectors like reentrancy, oracle manipulation, and access control flaws. Smart Contract Hacking (SCH) provides hands-on training to help developers and auditors identify and prevent vulnerabilities before deployment.

SudoRare Hack

TOTAL LOST $883K

Low Aug 23, 2022 Drained Contracts / Rugpull ethereum

Affected Chain ethereum Incident surface

Recovered - No recovery reported

All-Time Rank #863 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

Quick Summary

The owner of SudoRare contracts used privileges and transferred all deposited assets from SudoRare Pools. The contracts contained security issues as minting and privileges to freely transfer any types of assets from the pools contract were accessible by the owner.

Details of the Exploit

SudoRare was a NFT platform with staking features using $XMON, $LOOKS and $ETH assets. After reaching certain amount of assets, the owner of the SudoRareGenesisPool contract used his privileges to withdraw funds including 6 $XMON (125.4 $ETH), 1,115,216 $LOOKS (192 $ETH) and 200 $wETH. After the withdrawal, all assets were sold on UniSwap for $wETH. The total of the ill-gotten funds amounted to 517,4 wETH, which were transferred to three newly added addresses.

Subsequently, a huge amount of $SR tokens (87.7 % of total supply) was transferred to another address. Official site sudorare.xyz has been downed and social accounts have been deleted.

Block Data Reference

Affected contract address: https://etherscan.io/address/0x8c4e4633…F6e905

Address of scammer: https://etherscan.io/address/0xbb42f789…389d8A

Public addresses of three current holders of rugged wETH:

https://etherscan.io/address/0x0498d16a…b68074

https://etherscan.io/address/0xbFb7840e…777EAa

https://etherscan.io/address/0x75c3b271…Bc3981

Transaction (Project deployer withdrawing funds)

https://etherscan.io/tx/0x78d9a54c…7a819b

Source code:

https://etherscan.io/address/0x8703ff2b…f159d4#code

Incident Report

Protocol / Project SudoRare

Date of Incident August 23, 2022

Affected Chain(s) ethereum

Attack Technique Drained Contracts / Rugpull

Classification Rugpull / NFT

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token SudoRare

Smart Contract Language Solidity

Team Anonymous

Source Code Verified On-Chain

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of drained contracts / rugpull and Solidity and EVM internals

Capital Required Seed capital to cover gas and initial position setup

On-Chain Access Ability to interact with ethereum smart contracts and deploy a custom exploit contract

Protocol Analysis Identification of the exploitable vulnerability in SudoRare's contract logic - root cause: rugpull / nft

Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block

Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Hard to catch — private key / OpSec failures are outside smart contract audit scope

If you're auditing a protocol with similar architecture to SudoRare, these are the critical security checks that could have prevented this incident (August 2022).

Verify all logic paths related to Drained Contracts / Rugpull are guarded by proper access controls and input validation
Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Sources & References

01
Source 1 https://www.theblock.co/post/164970/nft-exchange-sudorare-suffer…
02
Reference https://www.business2community.com/crypto-news/nft-sudorare-rug-…
03
Reference https://forkast.news/headlines/sudorare-vanishes-with-519-ethereum/
04
Reference https://cryptobriefing.com/sudorare-pulled-the-rug-for-820000-ho…

Threat Assessment

Severity Level

LOW

Attack Vector Drained Contracts / Rugpull
Root Cause Rugpull / NFT
Year 2022

Learn to Prevent the Next SudoRare

The SudoRare hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Start Free Trial Browse Attack Library