当“安全铸造”不再安全:“HypeBears”安全事件的经验教训

当“安全铸造”不再安全:“HypeBears”安全事件的经验教训

2月3日上午(+8时区),我们的系统报告了一笔针对 HypeBears NFT合约的攻击交易 0xfa97c3476aa8aeac662dae0cc3f0d3da48472ff4e7c55d0e305901ec37a2f704。经过调查,我们发现这是由ERC721的_safeMint函数引起的一次重入攻击。

根本原因

该项目对一个账户可以铸造的NFT数量有限制。基本上,它有一个addressMinted映射,用于记录一个账户是否已经铸造了NFT。

在铸造NFT时,代码使用了OZ参考实现的_safeMint函数。这个函数是“安全”的,因为它会检查接收方是否能够接收ERC721代币。这可以防止NFT被铸造到无法处理ERC721代币的合约中。根据文档:

如果to指向一个智能合约,它必须实现IERC721Receiver.onERC721Received,该函数在安全转账时会被调用。以下代码显示了OZ实现_safeMint函数的代码。

然而,这个外部函数调用会产生一个安全漏洞。具体来说,攻击者可以在onERC721Received回调函数中执行重入调用。例如,在易受攻击的HypeBears合约中,攻击者可以在onERC721Received回调函数中再次调用mintNFT函数(因为addressMinted尚未更新)。

攻击

下图显示了攻击交易

教训

安全研究人员已经讨论过SafeMint带来的风险链接1 链接2。然而,我们仍然可以看到易受攻击的代码和现实中的攻击。正如在QBridge安全事件中的safeTransfer所示,使用一个**安全的函数并不保证一个安全**的合约 😃。

Sign up for the latest updates
Weekly Web3 Security Incident Roundup | Feb 9 – Feb 15, 2026

Weekly Web3 Security Incident Roundup | Feb 9 – Feb 15, 2026

During the week of February 9 to February 15, 2026, three blockchain security incidents were reported with total losses of ~$657K. All incidents occurred on the BNB Smart Chain and involved flawed business logic in DeFi token contracts. The primary causes included an unchecked balance withdrawal from an intermediary contract that allowed donation-based inflation of a liquidity addition targeted by a sandwich attack, a post-swap deflationary clawback that returned sold tokens to the caller while draining pool reserves to create a repeatable price-manipulation primitive, and a token transfer override that burned tokens directly from a Uniswap V2 pair's balance and force-synced reserves within the same transaction to artificially inflate the token price.

Top 10 "Awesome" Security Incidents in 2025

Top 10 "Awesome" Security Incidents in 2025

To help the community learn from what happened, BlockSec selected ten incidents that stood out most this year. These cases were chosen not only for the scale of loss, but also for the distinct techniques involved, the unexpected twists in execution, and the new or underexplored attack surfaces they revealed.

#10 Panoptic Incident: XOR Linearity Breaks the Position Fingerprint Scheme

#10 Panoptic Incident: XOR Linearity Breaks the Position Fingerprint Scheme

On August 29, 2025, Panoptic disclosed a Cantina bounty finding and confirmed that, with support from Cantina and Seal911, it executed a rescue operation on August 25 to secure roughly $400K in funds. The issue stemmed from a flaw in Panoptic’s position fingerprint calculation algorithm, which could have enabled incorrect position identification and downstream fund risk.