Friday , September 29 2023
Home / Crypto news / 4,000 ETH ($7.5M) Compromised Following Latest DeFi Exploit

4,000 ETH ($7.5M) Compromised Following Latest DeFi Exploit

Summary:
It appears that the DeFi industry continues to be a prime target for hackers. On the morning of May 28th, another exploit took place, this time taking aim at liquidity platform Jimbos Protocol. Jimbos Protocol got exploited today – May 28th. According to an update by PeckShield, the hack resulted in a loss of around 4,000 ETH, worth some .5 million at the time of the incident. Per PeckShield: This hack is due to the lack of slippage control of liquidity-shifting operation – such that the protocol-owned liquidity is invested into a skewed/imbalanced price range, which is exploited in reverse swap for profit. It appears today’s @jimbosprotocol hack leads to the 4090 ETH loss (w/ ~.5M). This hack is due to the lack of slippage control of liquidity-shifting operation —

Topics:
George Georgiev considers the following as important: ,

This could be interesting, too:

Mandy Williams writes Crypto.com Partners PayPal to Become Preferred Exchange for PYUSD

Mandy Williams writes EOS Foundation Taps Upland and Aerial to Foster Climate Positive Blockchain Initiative

Wayne Jones writes Bitcoin Miner Marathon Mines Invalid BTC Block

Anthonia Isichei writes SEC Plans to Hasten Ether Futures ETF Launch: Bloomberg ETF Analyst

It appears that the DeFi industry continues to be a prime target for hackers.

On the morning of May 28th, another exploit took place, this time taking aim at liquidity platform Jimbos Protocol.

  • Jimbos Protocol got exploited today – May 28th.
  • According to an update by PeckShield, the hack resulted in a loss of around 4,000 ETH, worth some $7.5 million at the time of the incident.
  • Per PeckShield:

This hack is due to the lack of slippage control of liquidity-shifting operation – such that the protocol-owned liquidity is invested into a skewed/imbalanced price range, which is exploited in reverse swap for profit.

  • The team has already addressed the issue and is supposedly working to investigate and get in touch with the exploiter.

You Might Also Like:

Leave a Reply

Your email address will not be published. Required fields are marked *