Decentralized finance insurance project Cover protocol briefly suffered losses when an unknown attacker minted over 40 quintillion Cover tokens. However, after successfully cashing out tokens worth about $5 million, the attacker unexpectedly returned ether tokens valued at about $3.2 million before leaving a message for the Cover team.
Exploit No Longer Possible
Immediately after the attack, the value of the insurance protocolâ€™s token plummeted by over 94% to $34 at the time of writing. After the incident, the Cover team immediately acknowledged the attack and went on to warn investors against buying the token while investigations were underway. The team also urged the attackers to return the rest of the stolen funds.
However, in their statement on December 28, the team tries to reassure investors that the vulnerabilities exploited by attackers had been fixed. The team says:
Furthermore, the Cover team also announced a compensation plan based on the snapshot that â€œwill be taken at block 11541218, one block before the first major exploited mint.â€ Nevertheless, the compensation plan appears to have sparked controversy for the project with some token holders now accusing the Cover team of being dishonest.
For instance, in a response to Coverâ€™s compensation plan, one Twitter user known as Phil argues:
Another user Kyouraku Shunsui asks â€œwhy the investors are blamed for being late for the team.â€ The user asks for a change to â€œthe snapshot time.â€ However, despite the complaints, the Cover team appears to be proceeding as planned.
What are your thoughts on the attack on Cover? Tell us what you think in the comments section below.
Disclaimer: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. Bitcoin.com does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.