How much was lost in the GigaDAO hack?

The GigaDAO hack resulted in $108K in losses on November 23, 2023.

What attack technique was used in the GigaDAO exploit?

The GigaDAO exploit utilized 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.

GigaDAO Hack

TOTAL LOST $108K

Low Nov 23, 2023 Rugpull

Affected Chain 2023 Incident surface

Recovered - No recovery reported

All-Time Rank #1505 By amount stolen

Protocol Type Reserve Currency Target category

Incident Overview

Quick Summary

GIGS token was rugpulled by deployer, removing liquidity worth 240,270 USD from PancakeSwap pool, causing a total loss of 107,819 USD.

Details of the Exploit

GIGS is a BEP20 token trading on PancakeSwap. On Nov 23, 2023, the deployer removed liquidity from the LP pool in an exit scam. The attacker added 456.12 WBNB as liquidity to the pool and then removed it, equating to a loss of 107,819 USD.

The stolen funds were transferred to another EOA address and subsequently distributed among multiple addresses.

Block Data Reference

Deployer Address:

https://bscscan.com/address/0x1C1208b4…BfAFF6

Liquidity Adding Transaction:

https://bscscan.com/tx/0xc50665cb…a7a992

Liquidity Removal Transaction:

https://bscscan.com/tx/0x87398f1e…9d7223

Incident Report

Protocol / Project GigaDAO

Date of Incident November 23, 2023

Attack Technique Rugpull

Classification Token

Primary Source View Post-Mortem

Protocol Information

Protocol Type Reserve Currency

Affected Token GIGS

Official Website www.gizadao.com

Protocol Twitter/X @GizaDao

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 rugpull and Solidity and EVM internals

Capital Required Seed capital to cover gas and initial position setup

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

Protocol Analysis Identification of the exploitable vulnerability in GigaDAO's contract logic - root cause: token

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 GigaDAO, these are the critical security checks that could have prevented this incident (November 2023).

Verify all logic paths related to 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://twitter.com/PeckShieldAlert/status/1727901233762177025

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Token
Year 2023

Learn to Prevent the Next GigaDAO

The GigaDAO 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