News linked to both this project and an event.
Odaily Planet Daily reported that the algorithmic stablecoin Balance Coin dropped from $0.9954 to $0.001358, a decline of over 99%. The stablecoin is the native algorithmic stablecoin of the Balance Protocol, designed to maintain a peg to the US dollar. Blockchain security firm PeckShield stated that the depegging occurred following an exploit of the decentralized autonomous organization 42DAO, which governs the Balance Protocol and its BLC token, resulting in a $915,000 loss. TenArmor reported detecting suspicious attacks involving GemJoin and 42DAO on the BNB Chain.
the Midnight Foundation has provided an update on the handling of the cross-chain bridge attack event involving Wanchain Cardano and BNB. Multiple exchanges including KuCoin, Kraken, Binance, Bybit, OKX, Gate, and MEXC have coordinated risk control actions, temporarily freezing the involved accounts and associated addresses, adding the hacker wallet to a blacklist, and pausing NIGHT token deposits and withdrawals as needed to curb the transfer and cashing out of stolen assets.The Foundation specifically noted that this security incident is an isolated incident related to a third-party cross-chain bridge, and the Midnight mainnet and native NIGHT assets have not been affected. The project team continues to collaborate with major exchanges and ecosystem partners to advance traceability investigations, reminding the community to rely on official disclosures for information and to be cautious of misinformation.
Robinhood Chain launchpad Pons has officially responded to earlier reports about a token authorization vulnerability in its front end, stating that the Pons launchpad trading page does not have any Multicall3 functionality. The Multicall3 feature mentioned in the tweet originated from the previous Debank Chain old version bridge and was released before the Pons launchpad, thus it does not affect launchpad users. It is currently confirmed that only 0.60 NOXA tokens, valued at approximately $0.66, are affected.As a security precaution, Pons recommends that users who previously used the old version bridge revoke token authorizations via revoke.cash. The team is currently working with audit firms to investigate potential risks and has stated that Pons' front-end services will be restored after confirming the absence of any actual vulnerabilities.
Michael, Chief Business Officer of Token Pocket, stated on platform X that Robinhood founder's seed phrase was leaked during a live stream. After gaining control of the address, the hacker used it and associated addresses to heavily purchase the Meme token $1, prompting thousands of investors to follow suit. In a short time, the token's market cap quickly surged from approximately $500,000 to $14 million.Subsequently, the price of the $1 token dropped sharply, with two-hour trading volume reaching around $20 million. After the address was frozen, the hacker quickly moved to the BNB Chain, using the address and its associated addresses to issue a new token. They created trading activity through tactics like wash trading, ultimately dumping the tokens for profit.Currently, Robinhood's RPC has frozen the address, and the node does not allow transactions originating from this address to be packaged, making transfers, purchases, or sales impossible.
According to official sources, TAC issued a statement regarding the significant price drop in the past 24 hours, stating that the protocol was not attacked, on-chain assets are secure, and the system is operating normally; the team and early investors did not participate in the sell-off, relevant tokens remain in the lock-up and vesting period, and there is no possibility of unlocking at this stage.
According to The Block, BNB Chain is building a new Layer 1 blockchain designed specifically for agent trading, targeting transaction pre-confirmation in under 50 milliseconds, and suppressing MEV behaviors such as sandwich attacks by eliminating the public mempool (adopting the TxStream mechanism). The new chain will also reserve block space for oracles, liquidations, and cross-chain bridges via PriorityLane, with a designed throughput target exceeding 100,000 TPS, and supporting sub-second block finality. This chain will become the fourth chain in the BNB Chain ecosystem, connected to BNB Smart Chain via a native bridge, with BSC serving as the settlement hub. The testnet is planned to launch at the end of 2026, and the mainnet is expected to deploy in early 2027.
BNB Chain is developing a new Layer 1 blockchain designed for Agentic Trading, releasing the first detailed architectural information after months of research and development. According to BNB Chain's disclosed technical roadmap for the second half of 2026, the new chain will run in parallel with the existing BNB Chain ecosystem, targeting transaction preconfirmation times of less than 50 milliseconds. The goal is to deliver an execution experience close to that of centralized exchanges (CEX) while retaining the advantages of on-chain self-custody and transparency.In terms of technical architecture, the new chain will remove the traditional public mempool and introduce a transaction transmission mechanism called "TxStream," which directly sends transactions to block producers to reduce latency and minimize MEV extraction behaviors such as sandwich attacks. (The Block)
: Cardano wallet service provider SecondFi has released an update on the security incident recovery progress, stating that EMURGO has established an asset recovery fund to return assets to users affected by the attack.SecondFi stated that emergency measures have been taken to protect and restore access to some assets. The team is currently discussing appropriate custody mechanisms with Intersect to ensure the safe return of assets to users.Furthermore, SecondFi is collaborating with a Cardano community-led working group to advance the on-chain recovery plan. Due to the recovery plan being more complex than initially expected, the overall recovery time may exceed the previously estimated two weeks.
Base has officially released an analysis report on the block production outage, disclosing that the Base mainnet experienced two block production interruptions on June 25 and 26, lasting 116 minutes and 20 minutes respectively. On-chain asset security was unaffected, and funds remained safe at all times. The root cause was a vulnerability in the sequencer's block construction logic: after a transaction execution failure, the old journal state was not properly cleared, causing subsequent legitimate transactions to encounter gas calculation errors during execution, thereby generating invalid state transition blocks and halting block production on the entire L2 chain.Base stated that the issue has been resolved through a patch, and will strengthen the protocol's fuzz testing and stress testing framework to identify potential malicious transaction paths, while optimizing monitoring and operational processes. Additionally, plans are in place to introduce a recovery mechanism to enhance rapid recovery capabilities in future similar events.
Cybersecurity firm Novee, in its latest research, revealed a CI/CD supply chain vulnerability pattern dubbed “Cordyceps,” primarily involving command injection, authentication logic flaws, artifact poisoning, and privilege escalation within GitHub Actions workflows. According to the report, unauthenticated users can exploit these vulnerabilities under specific conditions to hijack workflows, steal credentials, or gain control of code repositories.
HashKey Chain will host the “HashKey Chain Horizon” hackathon in Japan from June 18 to July 14. Built upon the foundation of building a compliant and secure Web3 ecosystem, this hackathon is open to developers, innovators, and Web3 enthusiasts worldwide. It features two challenge tracks focused on key areas within the HashKey Chain ecosystem.
Taiko stated on its X platform that it has confirmed its chain state verification mechanism has been compromised, and the security assumptions of all cross-chain bridges deployed on Taiko are no longer reliable.Taiko said it is coordinating with its security committee and ecosystem partners to control the situation, suspending affected systems, and taking technical and legal actions. Taiko strongly advises all users to immediately withdraw funds from cross-chain bridges deployed on Taiko.Additionally, Taiko has made an urgent request for all centralized exchanges to suspend TAIKO token deposit services until further official notice. Previously, Taiko's ERC20 Vault was attacked, resulting in losses exceeding $1 million.
Odaily news, Slow Mist founder Cosine published an analysis stating that the approximately $1.1 million loss incident in the OLPC / LABUBU liquidity pool on BNB Chain is suspicious. The loss occurred due to a severe imbalance in the OLPC/LABUBU trading pair, caused by a "vulnerability" in OLPC being exploited. Under certain conditions in _update, it is possible to burn OLPC tokens amounting to value * decimalsValue. Normally, decimalsValue is 1, but approximately 46 days before the attack, it was changed by the owner to an extremely large value of 7,326,680,472,586,200,649. A few days later, the OLPC owner renounced ownership, setting it to the zero address.Today, the attacker exploited this extremely large decimalsValue to trigger the Pair reserve burn, allowing a small amount of OLPC to extract a large amount of LABUBU. The attacker ultimately swapped 1.115 million USDT at a low cost. The suspicious point lies in the setting of decimalsValue—why did the OLPC owner set such an abnormally large value?
PancakeSwap has issued a notice regarding abnormal activity in the BNB Chain OLPC/LABUBU liquidity pool, stating that the team has acknowledged community reports and initiated a preliminary investigation.PancakeSwap indicated that initial findings confirm no issues at the smart contract level, and the relevant incident is still under further review. The team will continue to monitor the situation and provide updates as more information becomes available.The platform reminds users to rely on information released through PancakeSwap's official channels and to be cautious of unverified rumors.
according to PeckShield monitoring, the OLPC/LABUBU liquidity pool on BNB Chain's PancakeSwap was attacked. The attacker stole approximately $1.1 million worth of assets. After the incident, the attacker cross-chain transferred the stolen funds to Ethereum and subsequently deposited 633.4 ETH into the mixing protocol Tornado Cash. Additionally, the attacker sent 0.0221 BNB and 0.0411 ETH to a deprecated address. Relevant attack details and fund flows are still under continuous tracking.
According to on-chain analyst PeckShield (@PeckShieldAlert), the Humanity attacker’s address has bridged 130 ETH (approximately $220,600) from Ethereum to BNB Chain (381 BNB).
SlowMist announced that over 140 Mastra-related npm packages were compromised via a supply-chain attack. Affected versions introduce the malicious dependency `[email protected]`, which triggers attacker-controlled code execution during installation.
Humanity has announced the $H incident recovery plan: The legacy version of H on Ethereum, BNB Smart Chain, and Humanity Mainnet has been deprecated. A new Ethereum ERC-20 version of H will be airdropped 1:1 to eligible holders based on a pre-attack snapshot. Attackers and associated addresses have been excluded.
According to on-chain security platform Blockaid (@blockaid_), the MILC Platform cross-chain bridge suffered a private key leak on both the BNB Chain and Ethereum networks. The attacker exploited a historical bridge administrator wallet to grant the DEFAULT_ADMIN_ROLE and MANAGER_ROLE permissions to the attacker’s address. Subsequently, assets were withdrawn from the bridge contract, and administrative control was transferred to the attacker’s wallet. Confirmed losses currently stand at approximately $97,003 USDT (on BNB Chain) and approximately 39.21 ETH (on Ethereum, transferred out via Rhino.fi), totaling roughly $161,000.
Humanity released a post-mortem report on the H token security incident that occurred between June 8 and 9, stating that the incident was not caused by a smart contract vulnerability, but rather by a malware intrusion into a developer's device, which led to the leakage of private keys. Humanity stated that the attacker still holds the ProxyAdmin permissions for the ETH bridge and the BNB Chain token. Preliminary investigations confirmed that a colleague's device was infected with malware, which the attacker used to obtain the hot wallet private key of the administrator and the private keys for signing on 6 Gnosis Safe wallets. The team has hired an external security agency to conduct a forensic investigation and stated that they are formulating a recovery plan for affected users.