How much was lost in the DGLD hack?

The DGLD hack resulted in — in losses on February 23, 2026.

What attack technique was used in the DGLD exploit?

The DGLD exploit utilized Infinite Mint and Dump. 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.

DGLD Hack

TOTAL LOST —

Feb 23, 2026 Infinite Mint and Dump base

Affected Chain base Incident surface

Recovered - No recovery reported

All-Time Rank #2033 By amount stolen

Year 2026 Incident year

Incident Report

Protocol / Project DGLD

Date of Incident February 23, 2026

Affected Chain(s) base

Attack Technique Infinite Mint and Dump

Classification Protocol Logic

Primary Source View Post-Mortem

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 infinite mint and dump and Solidity and EVM internals

Capital Required Seed capital to cover gas and initial position setup

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

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

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? Likely — with a thorough Infinite Mint and Dump audit checklist and test coverage

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

Verify all logic paths related to Infinite Mint and Dump 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://x.com/DGLD_Official/status/2025996938869694927

Threat Assessment

Severity Level

UNKNOWN

Attack Vector Infinite Mint and Dump
Root Cause Protocol Logic
Year 2026

Learn to Prevent the Next DGLD

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

Incident Report

What the Attacker Needed to Succeed

What Auditors Should Check

Sources & References

Related Hacks - Infinite Mint and Dump

Learn to Prevent the Next DGLD