Odaily Planet Daily reports: White-hat hacker f4lc0n posted on X that he discovered a critical vulnerability on the Injective chain via the Immunefi platform, allowing any user to directly steal funds from any on-chain account without special privileges, putting over $500 million in on-chain assets at risk. The hacker stated that the Injective team submitted a fix for governance voting the day after the report was filed, but received no follow-up or technical discussion for the next three months. Ultimately, Injective offered a $50,000 bounty, despite the project’s maximum bounty for critical vulnerabilities being $5 million. The hacker said he raised an objection but received no response, and the $50,000 bounty has still not been paid.
White Hat Hacker Claims Injective’s Critical Vulnerability Exposed Over $500 Million in Assets, Only $50,000 Bounty Offered
KuCoinFlashShare
Summary
A white hat hacker named f4lc0n disclosed a critical vulnerability on the Injective blockchain via the Immunefi platform. The flaw could enable attackers to steal funds from any on-chain account, exposing over $500 million in assets. The Injective team deployed a fix for governance following the report, but communication stalled for three months. They eventually offered a $50,000 bounty, despite a stated maximum policy of $500,000. The hacker stated the bounty remains unpaid and expressed dissatisfaction.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.