{"id":11455,"date":"2022-06-09T10:10:58","date_gmt":"2022-06-09T10:10:58","guid":{"rendered":"https:\/\/nftandcrypto-news.com\/crypto\/attackers-loot-5m-from-osmosis-in-lp-exploit-2m-returned-soon-after\/"},"modified":"2022-06-09T10:11:00","modified_gmt":"2022-06-09T10:11:00","slug":"attackers-loot-5m-from-osmosis-in-lp-exploit-2m-returned-soon-after","status":"publish","type":"post","link":"https:\/\/nftandcrypto-news.com\/crypto\/attackers-loot-5m-from-osmosis-in-lp-exploit-2m-returned-soon-after\/","title":{"rendered":"Attackers loot $5M from Osmosis in LP exploit, $2M returned soon after"},"content":{"rendered":"
<\/p>\n
Osmosis, a decentralized exchange (DEX) built on the Cosmos network, was halted just before 3:00 am EST on Wednesday after attackers exploited a liquidity provider (LP) bug to the tune of roughly $5 million.<\/p>\n
The bug was first\u00a0identified<\/a>\u00a0in a Reddit post on the official Cosmos Network page. The user, Straight-Hat3855, brought attention to a \u201cserious problem\u201d with Osmosis (OSMO) that allowed users to arbitrarily grow LPs by 50% simply by adding and removing liquidity.\u00a0The Reddit post was quickly removed, but not before malicious actors took advantage of the bug, which saw approximately $5 million removed from liquidity pools on the Osmosis exchange.<\/p>\n Following the exploit and the identification of the LP bug, the Osmosis exchange was halted at a block height of 4,713,064, according to an announcement from Osmosis block explorer Mintscan.<\/p>\n Explaining how the bug worked in a series of posts in the Osmosis Discord was project moderator RoboMcGobo, who detailed how the flaw allowed attackers to add liquidity to any Osmosis LP and then immediately withdraw it for a 150% return on their initial deposit: \u201cEssentially, the function would give 50% too many LP shares for a join,\u201d RoboMcGobo wrote just after 4:00 pm on Wednesday, adding: \u201cIf one should have gotten 10 LP shares, 15 would be achieved out.\u201d<\/p>\n RoboMcGobo explained that the bug was \u201cexploited intentionally by a small number of users\u201d and \u201cseemingly unintentionally by a few others.\u201d\u00a0According to a Twitter thread from Osmosis, four attackers were responsible for 95% of the total exploit amount, with two of the attackers voluntarily stepping forward to return stolen funds.<\/p>\n Update:<\/p>\n – 4 individuals have been identified that account for 95%+ of realized exploit amount.<\/p>\n – 2 out of the 4 individuals has proactively expressed intent to return the exploited amount in full.<\/p>\n \u2014 Osmosis (@osmosiszone) June 8, 2022<\/a><\/p><\/blockquote>\n Roughly one hour following Osmosis\u2019 tweet concerning the attack, FireStake, a validator in the Cosmos ecosystem, posted a Twitter thread admitting that \u201ca temporary lapse in good judgment\u201d saw two members of its team exploit the bug to the extent of roughly $2 million. <\/p>\n Firestake told their 1,700 Twitter followers that they were \u201cthinking about [their] family\u2019s future\u201d when they continued to exploit the bug. However, after admitting to \u201cstressing through the night\u201d about the event, they decided to voluntarily return the funds and \u201cset things straight.\u201d<\/p>\n Dear @osmosiszone<\/a> community, many of you know about the Osmosis LP bug that occurred yesterday. <\/p>\n In disbelief of it being real, two members of @fire_stake<\/a> started testing to see if the bug existed, testing grew into a temporary lapse in good judgment, and…<\/p>\n\n
\n