Hacken Bridge Exploited for $250k in HAI Tokens Following Private Key Leak
ByAinvest
Monday, Jun 23, 2025 2:09 am ET1min read
BNB--
Blockchain security auditor Hacken has confirmed a significant exploit involving the unauthorized minting of HAI tokens on Ethereum and BNB Chain. A compromised private key allowed a malicious actor to mint 900 million HAI tokens, which were subsequently dumped on decentralized exchanges, resulting in estimated realized losses of $250,000. Hacken has revoked the affected minter account's access and paused bridge transactions, urging users to avoid interacting with the token until further notice [1].
The incident occurred during architectural changes to Hacken's blockchain bridge, which were intended to prevent such risks. The compromised private key was connected to an account with minting rights, leading to the unauthorized minting and dumping of HAI tokens. The value of HAI tokens plummeted by 99% from $0.015 to $0.000056, causing a substantial drop in the token's market cap [1].
Hacken's CEO, Dyma Budorin, acknowledged the incident and stated that all tokens bought after the hack will not be supported in the new tokenomics. The firm aims to transform HAI into a regulated financial tool that merges token utility with equity rights by merging HAI and Hacken's equity shareholders [1]. The core infrastructure of Hacken remains secure, and there is no evidence of any compromise beyond the private keys [1].
In response to the incident, Hacken has paused bridge transactions on Ethereum and BNB Chain until further notice and warned users about potential scams. The firm is working on transitioning HAI into a regulated security token and has advised users to track their legitimate balances and be cautious when interacting with the token [1].
This incident highlights the ongoing challenges faced by blockchain projects in maintaining security and protecting against unauthorized minting. It underscores the importance of robust security measures and the potential risks associated with human error and architectural changes in blockchain infrastructure.
References:
[1] https://cointelegraph.com/news/hacken-exploited-through-private-key-leak
[2] https://www.fxleaders.com/news/2025/06/23/cybersecurity-firm-hacken-suffers-98-token-crash-after-private-key-compromise/
DMAA--
ETH--
MIMI--
Hacken, a blockchain security auditor, has confirmed a major exploit involving the unauthorized minting of HAI tokens on Ethereum and BNB Chain. A compromised private key allowed a malicious actor to mint 900 million HAI tokens, which were subsequently dumped on decentralized exchanges, resulting in estimated realized losses of $250,000. Hacken has revoked the affected minter account's access and paused bridge transactions, urging users to avoid interacting with the token until further notice.
June 19, 2025Blockchain security auditor Hacken has confirmed a significant exploit involving the unauthorized minting of HAI tokens on Ethereum and BNB Chain. A compromised private key allowed a malicious actor to mint 900 million HAI tokens, which were subsequently dumped on decentralized exchanges, resulting in estimated realized losses of $250,000. Hacken has revoked the affected minter account's access and paused bridge transactions, urging users to avoid interacting with the token until further notice [1].
The incident occurred during architectural changes to Hacken's blockchain bridge, which were intended to prevent such risks. The compromised private key was connected to an account with minting rights, leading to the unauthorized minting and dumping of HAI tokens. The value of HAI tokens plummeted by 99% from $0.015 to $0.000056, causing a substantial drop in the token's market cap [1].
Hacken's CEO, Dyma Budorin, acknowledged the incident and stated that all tokens bought after the hack will not be supported in the new tokenomics. The firm aims to transform HAI into a regulated financial tool that merges token utility with equity rights by merging HAI and Hacken's equity shareholders [1]. The core infrastructure of Hacken remains secure, and there is no evidence of any compromise beyond the private keys [1].
In response to the incident, Hacken has paused bridge transactions on Ethereum and BNB Chain until further notice and warned users about potential scams. The firm is working on transitioning HAI into a regulated security token and has advised users to track their legitimate balances and be cautious when interacting with the token [1].
This incident highlights the ongoing challenges faced by blockchain projects in maintaining security and protecting against unauthorized minting. It underscores the importance of robust security measures and the potential risks associated with human error and architectural changes in blockchain infrastructure.
References:
[1] https://cointelegraph.com/news/hacken-exploited-through-private-key-leak
[2] https://www.fxleaders.com/news/2025/06/23/cybersecurity-firm-hacken-suffers-98-token-crash-after-private-key-compromise/

Stay ahead of the market.
Get curated U.S. market news, insights and key dates delivered to your inbox.
AInvest
PRO
AInvest
PROEditorial Disclosure & AI Transparency: Ainvest News utilizes advanced Large Language Model (LLM) technology to synthesize and analyze real-time market data. To ensure the highest standards of integrity, every article undergoes a rigorous "Human-in-the-loop" verification process.
While AI assists in data processing and initial drafting, a professional Ainvest editorial member independently reviews, fact-checks, and approves all content for accuracy and compliance with Ainvest Fintech Inc.’s editorial standards. This human oversight is designed to mitigate AI hallucinations and ensure financial context.
Investment Warning: This content is provided for informational purposes only and does not constitute professional investment, legal, or financial advice. Markets involve inherent risks. Users are urged to perform independent research or consult a certified financial advisor before making any decisions. Ainvest Fintech Inc. disclaims all liability for actions taken based on this information. Found an error?Report an Issue

Comments
No comments yet