How much was lost in the NewDex hack?

The NewDex hack resulted in $58K in losses on September 14, 2018.

What attack technique was used in the NewDex exploit?

The NewDex exploit utilized Infinite Mint. 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.

NewDex Hack

TOTAL LOST $58K

Low Sep 14, 2018 Infinite Mint eos

Affected Chain eos Incident surface

Recovered - No recovery reported

All-Time Rank #2066 By amount stolen

Year 2018 Incident year

Incident Report

Protocol / Project NewDex

Date of Incident September 14, 2018

Affected Chain(s) eos

Attack Technique Infinite Mint

Classification Token & Share Accounting

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

Capital Required Seed capital to cover gas and initial position setup

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

Protocol Analysis Identification of the exploitable vulnerability in NewDex's contract logic - root cause: token & share accounting

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 audit checklist and test coverage

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

Verify all logic paths related to Infinite Mint 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

Threat Assessment

Severity Level

LOW

Attack Vector Infinite Mint
Root Cause Token & Share Accounting
Year 2018

Learn to Prevent the Next NewDex

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

Related Hacks - Infinite Mint

Learn to Prevent the Next NewDex