On June 12, 2026, the Beldex team identified unauthorized minting of BDX-BSC tokens resulting from an issue within the Beldex bridge infrastructure that supports BDX on BSC Chain.
Immediately upon discovery, our incident response procedures were activated. The affected bridge infrastructure, BDX-BSC contract, and related services, including trade, deposits, and withdrawals on exchanges where the BDX-BSC token was listed, were paused to prevent further activity while our team began a comprehensive investigation.
First and foremost, we want to reassure the community that this incident was isolated to the BDX-BSC environment and its associated bridge infrastructure. The Beldex native blockchain was not affected. The native chain remained secure, fully operational, and continued processing transactions normally throughout the incident.
What Happened?
Our investigation determined that unauthorized BDX-BSC tokens were minted through the bridge infrastructure without the corresponding movement of native BDX that would normally back those assets.
Preliminary analysis identified approximately 38.2 million unauthorized BDX-BSC tokens minted and distributed across multiple addresses controlled by the malicious actor.
Following the minting event, the attacker moved the unauthorized BDX-BSC tokens across several platforms. A portion of these tokens was bridged into native BDX and subsequently sold on centralized exchanges, while other funds (BDX-BSC tokens) were deposited directly into supported exchanges.
The incident activity was first traced to transactions occurring after June 10, 2026, at approximately 23:36 UTC. The attacker subsequently began selling the tokens on the market on June 11, 2026, at around 23:10 UTC. The bridge infrastructure was paused early on June 12, 2026, preventing any further activity through the affected pathway.
Immediate Response
Upon identifying the issue, the Beldex team took immediate action to contain the incident and protect users.
These measures included:
- Suspending bridge operations to prevent further unauthorized activity.
- Pausing the affected BDX-BSC contract environment, including deposits, withdrawals, and trades on exchanges where BDX-BSC is listed.
- Conducting a comprehensive investigation into fund movements.
- Tracing transactions associated with the unauthorized minting event.
- Coordinating with exchanges, wallets, infrastructure providers, and other ecosystem partners.
- Sharing transaction records and wallet information with relevant parties to support investigations and asset monitoring efforts.
The affected bridge infrastructure has since been secured, and no additional movement through the affected bridge pathway is possible.
Impact Assessment
While the incident affected BDX on the BSC chain, the impact was limited to the bridge environment and did not affect the Beldex native blockchain’s infra.
The following remained unaffected throughout the incident:
- The Beldex native blockchain.
- Native BDX balances and transactions.
- Masternode operations.
- Network consensus.
- Core protocol security.
- BChat, BelNet, and Beldex Browser Infra.
Users holding native BDX on the Beldex blockchain were not impacted by this event.
Maintaining Market Stability
Security incidents can create uncertainty, especially when they involve bridged assets like BDX-BSC operating across multiple blockchain ecosystems.
As part of our immediate response, the Beldex team worked closely with ecosystem partners and implemented measures to stabilize market conditions and reduce disruption to legitimate users through strategic buybacks.
We would like to thank our exchange partners, custodial and non-custodial wallet partners, as well as other infrastructure service providers and community members who assisted throughout the process.
Why We Are Replacing the Existing BDX-BSC Contract
As our investigation progressed, it became clear that continuing with the existing BDX-BSC contract would not provide the level of assurance and clarity required for long-term ecosystem stability.
For this reason, Beldex will retire the existing BDX-BSC contract (0x6ad12E761b438beA3EA09F6C6266556Bb24C2181) and deploy a new BDX-BSC contract that will continue to maintain a 1:1 relationship with native BDX.
The new contract will become the canonical representation of BDX on the BSC Chain moving forward.
New contract address :
0x9d10a1ec41Fe7878429BB457e31F9b050D38c633
Protecting Legitimate Holders
A key priority throughout this process has been ensuring that legitimate users are not negatively affected by the incident.
To accomplish this, the Beldex team is working closely with exchanges and ecosystem partners to establish a comprehensive balance reconciliation process.
Exchange partners have been requested to provide balance snapshots and transaction records covering the affected period. This information will allow us to distinguish legitimate user holdings from funds associated with the unauthorized minting event.
Non-custodial wallet holders (holders of BDX-BSC tokens on wallets like MetaMask and Trust Wallet) will also be compensated on a 1:1 ratio. Users do not need to take any action to receive funds. The new BDX-BSC tokens will be credited to them automatically based on snapshots taken at 23:36 UTC, June 10, 2026 (that is, before the attack).
All eligible holders will receive replacement BDX-BSC tokens under the new contract on a 1:1 basis. Our goal is simple: to protect legitimate holders and they should retain their economic position despite the incident.
What Users Need To Do
At this stage, users are not required to take any action.
We strongly advise the community to rely only on official Beldex communication channels for updates regarding:
- Contract migration details.
- Eligibility criteria.
- Snapshot procedures.
- Exchange support.
- Token distribution timelines.
Any migration instructions will be communicated directly by the Beldex team once finalized.
Next Steps
The Beldex team is currently focused on the following priorities:
- Completing the ongoing investigation and independent review process along with leading blockchain auditing firms in the industry.
- Finalizing the deployment of the new BDX-BSC contract.
- Coordinating with exchanges and infrastructure partners.
- Reconciling legitimate user balances.
- Distributing replacement tokens on a 1:1 basis to eligible holders.
- Restoring full BDX functionality on the BSC Chain through a secure and sustainable framework.
Moving Forward
While incidents such as these are challenging for us, they also show the importance of transparent communication, rapid response, and strong ecosystem partnerships.
Throughout the remediation process, our commitment has remained unchanged. It is to protect users, maintain transparency, and restore normal operations as quickly and responsibly as possible.
We appreciate the patience, support, and trust shown by our community, partners, exchanges, and ecosystem participants.
Additional updates will be shared as new information becomes available.
— The Beldex Team
Listen
back to blog