Diamante ($DIAM)

What happened

The Diamante team discovered that the $DIAM contract on BSC was compromised. The attacker used stolen company access keys to take control of the contract and minted 161 million unauthorized DIAM tokens. Approximately 70% of the unauthorized tokens were subsequently frozen through cooperation with exchanges, the contract was secured under a new MPC wallet, and the team pledged to make all affected participants whole.

Details

Date

Oct 27, 2026

Kind

Hack or exploit

Method

Private Key Leakage

How in

Keys, accounts and infrastructure

Target

DeFi protocol or token (estimate: SlowMist chain category)

Chains

BNB Chain

What would have stopped it all controls for this way in

• What users load is locked down: build pipeline, dependencies, CDN, DNS and third-party scripts.
  Check: Who can change the code served to users, listed; dependencies pinned; DNS registrar locked; third-party scripts reviewed.
• Freeze contacts are arranged before they are needed: stablecoin issuers, the large exchanges, SEAL 911.
  Check: A contact sheet with named people, confirmed this quarter; one drill sending a freeze request.

General guidance for this kind of attack, not a finding about this incident.

After the theft

Frozen

yes, amount not stated
“Approximately 70% of the unauthorized tokens were subsequently frozen through cooperation with exchanges, the contract was secured under a new MPC wallet, and the team pledged to make all affected participants whole.” (SlowMist Hacked)

How sure: 0 of 4 checks what the checks mean

• Witnessesone source so far
• Same storyneeds a second source
• Blockchain receiptno public attack transaction checked
• Official wordno official statement linked

Who says what

• SlowMist Hacked ↗no figure

Related incidents