🔍 Fetch.ai and NuNet: what a compromised signing key actually breaks
Fetch.ai has published a preliminary on-chain analysis of the exploit of its token conversion contract. The team says the attack traces from a compromised signing key to the attacker's cash-out wallets, that the affected wallets and contract have been deactivated together with SingularityNET, and that the investigation is ongoing. Reporting puts the combined loss across Fetch.ai and NuNet at roughly $2 million, with the same attacker behind both.
Three things about the mechanism:
1️⃣ A token migration temporarily gives a token an issuer again. Tokens get released or minted on one side because an off-chain signer attests that something happened on the other. For the length of that migration, supply integrity rests on key custody, not on consensus.
2️⃣ A signature is not a proof. A contract can verify that a message was signed. It cannot verify that the event the message describes ever happened.
3️⃣ Being able to deactivate the contract quickly and being exposed this way come from the same place: privileged control. That is a trade-off worth naming, not a bug.
Open question: both projects being drained by the same attacker raises whether this was one shared trust boundary rather than two separate failures.
Not financial advice. Do your own research.
#CryptoNews #Security
Fetch.ai has published a preliminary on-chain analysis of the exploit of its token conversion contract. The team says the attack traces from a compromised signing key to the attacker's cash-out wallets, that the affected wallets and contract have been deactivated together with SingularityNET, and that the investigation is ongoing. Reporting puts the combined loss across Fetch.ai and NuNet at roughly $2 million, with the same attacker behind both.
Three things about the mechanism:
1️⃣ A token migration temporarily gives a token an issuer again. Tokens get released or minted on one side because an off-chain signer attests that something happened on the other. For the length of that migration, supply integrity rests on key custody, not on consensus.
2️⃣ A signature is not a proof. A contract can verify that a message was signed. It cannot verify that the event the message describes ever happened.
3️⃣ Being able to deactivate the contract quickly and being exposed this way come from the same place: privileged control. That is a trade-off worth naming, not a bug.
Open question: both projects being drained by the same attacker raises whether this was one shared trust boundary rather than two separate failures.
Not financial advice. Do your own research.
#CryptoNews #Security