How much was lost in the DxSale hack?

The DxSale hack resulted in $7.3M in losses on June 02, 2026.

What attack technique was used in the DxSale exploit?

The specific attack technique used in the DxSale hack has not been formally classified. Review available post-mortems and on-chain data for technical details.

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.

DxSale Hack

TOTAL LOST $7.3M

Medium Jun 02, 2026

Affected Chain 2026 Incident surface

Recovered - No recovery reported

All-Time Rank #367 By amount stolen

Auditors 1 Prior security audit

Incident Overview

SKALE (SKL) is a cryptocurrency launched in 2020and operates on the Ethereum platform. SKALE has a current supply of 6,342,291,667 with 6,192,144,337 in circulation. The last known price of SKALE is 0.00548144 USD and is down -3.09 over the last 24 hours.

It is currently trading on 253 active market(s) with $5,354,006.50 traded over the last 24 hours. More information can be found at https://skale.space/?utm_medium=website&utm_source=coinmarketcap&utm_campaign=skalepage.

This is classified as a Access Control Attacks . Compare similar hacks →

Incident Report

Protocol / Project DxSale

Date of Incident June 02, 2026

Primary Source View Post-Mortem

Protocol Information

Protocol Type Launchpad

Official Website skale.space/?utm_medium=website&utm_sou…

Protocol Twitter/X @SkaleNetwork

Market Context at Time of Hack

Token Categories

Platform Gaming Scaling Smart Contracts Staking Storage Arrington XRP Capital Portfolio BoostVC Portfolio

Protocol Links

GitHub Reddit

What Auditors Should Check

Audited by Audit Report 1 — still lost $7.3M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

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

Security Audit History

Audit Report 1 Report

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Access Control Attacks

Proof-of-Concept Exploits

1 PoC available

poc-exploits - dxsale

$ DxSale Ownership Override Attack

On-Chain Evidence & References

Reference https://crypto.news/dxsale-exploit-drains-7-3m-in-bnb-through-hi…
Twitter/X Alert https://x.com/Tahax1/status/1928169316736651568
Twitter/X Alert https://x.com/CoinsultAudits/status/1928203831996297670
Twitter/X Alert https://x.com/CertiKAlert/status/2006685174587605315

Sources & References

01
Source 1 https://rekt.news/dxsale-rekt

Threat Assessment

Severity Level

MEDIUM

Learn to Prevent the Next DxSale

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