Web3 security firm identifies activity similar to Kraken breach on OKX, BingX, Gate.io and Binance

Hexagate, a Web3 security firm, has identified on-chain activity similar to CertiK in Kraken’s case.
Security firm detected this across Base, BNBChain, Optimism, Arbitrum, Avalanche, LineaBuild and Polygon.
Hexagate states there is no evidence that exchanges have been impacted, shows on-chain proof, alerting users.

Security-focused ranking platform CertiK identified itself as the “white-hat” hacker behind the $3 million Kraken hack. The exchange is treating the case as a criminal exploit, and law enforcement is attempting to recover funds.

While the security firm defended its actions on X (crypto Twitter), it claims to have faced “extortion” from the exchange.

Web3 security firm sees activity identical to Kraken on other exchange platforms

Web3 security firm Hexagate has identified on-chain activity similar to CertiK’s interaction with the Kraken exchange platform across different chains: Base, BNBChain, Optimism, Arbitrum, Avalanche, LineaBuild and Polygon.

While the platform notes that exchange platforms may not have been impacted and presents no evidence for the same, it shows proof of the on-chain activity in a series of tweets on X. The firm lists exchange platforms like OKX, BingX, Gate.io and Binance.

The firm notes that the activity was traced back to May 17.

Post the @krakenfx breach, we've detected similar activity on @base, @BNBCHAIN, @Optimism, @arbitrum, @avax, @LineaBuild and @0xPolygon trying to target @okx, @BingXOfficial, @gate_io, and @binance and others and some unknown addresses, with matching signature hashes.

NOTE: We… pic.twitter.com/JyMZy0Uira
— Hexagate (@hexagate_) June 20, 2024

CertiK informed the community of multiple bugs as part of the investigation and assessed the scope of the exchange’s vulnerability. CertiK says it's behind Kraken's $3 million bug exploitation.

For sharing the actual evidence of the on-chain activity, Hexagon was slammed for sharing the information in tweets. The firm defended themselves, noting that the incident was publicly known.

Guys, I know you want to showcase your solution but if there is actually an attack going on then it's reckless to comment on it publicly before the named parties responded to your disclosure.
— Oliver | Hats (@0xAngler) June 20, 2024

This incident is publicly known and was publicly announced by the companies themselves with their evidence. All we did is traced onchain similar attempts of the same thing that was shared on CT. We waited more than a day to share - we never post if there is any threat to funds.
— Hexagate (@hexagate_) June 20, 2024

FXStreet reached out to OKX, BingX, and Gate for comments but did not receive any before publishing.

Share: Cryptos feed

Information on these pages contains forward-looking statements that involve risks and uncertainties. Markets and instruments profiled on this page are for informational purposes only and should not in any way come across as a recommendation to buy or sell in these assets. You should do your own thorough research before making any investment decisions. FXStreet does not in any way guarantee that this information is free from mistakes, errors, or material misstatements. It also does not guarantee that this information is of a timely nature. Investing in Open Markets involves a great deal of risk, including the loss of all or a portion of your investment, as well as emotional distress. All risks, losses and costs associated with investing, including total loss of principal, are your responsibility. The views and opinions expressed in this article are those of the authors and do not necessarily reflect the official policy or position of FXStreet nor its advertisers. The author will not be held responsible for information that is found at the end of links posted on this page.

If not otherwise explicitly mentioned in the body of the article, at the time of writing, the author has no position in any stock mentioned in this article and no business relationship with any company mentioned. The author has not received compensation for writing this article, other than from FXStreet.

FXStreet and the author do not provide personalized recommendations. The author makes no representations as to the accuracy, completeness, or suitability of this information. FXStreet and the author will not be liable for any errors, omissions or any losses, injuries or damages arising from this information and its display or use. Errors and omissions excepted.

The author and FXStreet are not registered investment advisors and nothing in this article is intended to be investment advice.