Payy Network Suffers $1.8 Million Loss Due to Bridge Logic Flaw
Payy Network experienced a significant security incident resulting in a loss of $1,828,589.38. The incident was attributed to a flaw in the bridge logic.
Our full investigation: Payy hack: the 682 ETH went into Tornado Cash, but 90,202 USDC is still on the exploiter’s wallet
The Payy Network was targeted in a security incident that led to a loss of $1,828,589.38. The incident was caused by a flaw in the bridge logic, which allowed for exploitation. This type of vulnerability can enable attackers to manipulate transactions or bypass security measures designed to protect assets during transfers between different blockchain networks.
The incident occurred on the Ethereum blockchain, which is known for its smart contract functionality. This means that the transactions related to the incident can be traced on the Ethereum network. The on-chain record will provide details of the transactions involved, including any addresses that were implicated in the exploit.
The loss represents a significant financial impact on the Payy Network, highlighting the potential risks associated with bridge mechanisms in blockchain technology. The incident serves as a reminder of the importance of thorough security audits and testing for vulnerabilities in smart contracts and bridging solutions.
Addresses in this incident
| Address | Chain | Role | Check |
|---|---|---|---|
| 0xaa4985dbdabfaca344237d40f7e06c4a0bb57e70 | ETH | mentioned in coverage | Check live |
| 0xb483b1742aad0a60a9fc91bb36c5a42dbe3f3d38 | ETH | mentioned in coverage | Check live |
| 0xe8d566e2f914dbd8309625e1792ed21fd0431956 | ETH | mentioned in coverage | Check live |
| 0x888a21c48cf442e312bddd7c24b678f0c7132a2a | ETH | mentioned in coverage | Check live |
| 0x3d092740936da4c5693dae3633c7207a37f40104 | ETH | mentioned in coverage | Check live |
| 0xf46e1e8ca9a032f1c84b1451890ad0aedb5e0bed | ETH | mentioned in coverage | Check live |
| 0x2072f325f0bb7e06c1d7c933a10886f794d4cc99 | ETH | mentioned in coverage | Check live |
| 0x21d4a32a357c77e72dce79810d54c7fcf5a19969 | ETH | mentioned in coverage | Check live |
Roles are attributed to the source that stated them. Addresses without an attributed role are listed because coverage mentioned them, not because we assign them a part in the incident.
