We’re aware of the exploit affecting b14g, a restaking and yield protocol on Core and Babylon, and we’re working closely with their team.
The Core network is secure. Core’s consensus, validators and staking contracts operated normally throughout, and CORE staked directly with validators or through other protocols is unaffected.
We’re supporting b14g and exchange partners to trace and freeze the funds. Most of the stolen CORE remains on Core, and exchanges are freezing deposits linked to the attacker.
We’ll share updates as we have them.
The Core network is secure. Core’s consensus, validators and staking contracts operated normally throughout, and CORE staked directly with validators or through other protocols is unaffected.
We’re supporting b14g and exchange partners to trace and freeze the funds. Most of the stolen CORE remains on Core, and exchanges are freezing deposits linked to the attacker.
We’ll share updates as we have them.
b14g Security UpdateView quoted post on X
At 09:29 UTC today, approximately 97M CORE staked through b14g was withdrawn without authorization and transferred to attacker-controlled addresses.
Upon discovery, we immediately paused the affected contracts. We are working closely with the Core team, security partners and exchanges to investigate the incident, trace the funds and coordinate freezing and recovery efforts.
Based on tracing so far, approximately 68M CORE remains on Core. Exchange partners have frozen approximately 9M CORE linked to the attacker.
The affected assets are CORE staked through b14g. BTC staked through b14g remains time-locked on Bitcoin and was not affected.
Our immediate priority is protecting users and recovering the affected funds.
Attacker addresses:
0xc556ed208285406d71705927f92d4f4eaea579f1
0x27758c30f8e424fbd8ca605bf31e9496c26ce92c
We will publish a detailed post-mortem covering the technical cause and impact, along with next steps for affected users. Further updates will follow as information is verified.
