Lava Lending Flash Loan Attack

Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' section to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.

Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!

Lava Lending Logo/Image

Lava Lending offered a decentralized liquidity market platform. An incident was reported on March 28, 2024 by PeckShield Alert, leading to the immediate pause of all lending markets to prevent further exploits. Community members collaborated with major exchanges to identify the exploit address, file law enforcement incidents, and list the address as malicious. Affected addresses were compensated by the Insurance Fund, independent of funds returned by the attacker. The protocol's exploit response procedures were followed, with ongoing investigations halted if 90% of user funds were returned. Updates to limit fees and claim pending fees as protocol fees have been made to enhance security.

This is a global/international case not involving a specific country.

About Lava Lending

"Decentralized, Cross-chain, Liquidity Markets. Borrow, lend, leverage, and basis trade liquidity positions from multiple DEXs across chains. Optimize your liquidity management with single asset zap-ins straight from your wallet."

"Firefighters are looking into a reported exploit. Please sit tight as we work with our community partners to resolve the situation and determine a clear plan of action."

"The incident was reported by PeckShield Alert to the protocol on March 28, 2024. Within 15 minutes of reviewing the report, all lending markets on the protocol were paused to prevent any further exploits. Lava community members reached out to contacts at major exchanges to identify the exploit address and prevent potential off-ramping of assets. Within an hour and with coordination of major exchanges, law enforcement incidents were filed. The address has also been listed as a malicious address on the blockchain explorer Arbiscan (Etherscan).

All affected addresses were identified and a contingency plan was enacted for compensation by the Insurance Fund, not dependent on the successful return of funds by the attacker.

An on-chain message was delivered to the attack address and the final recipient address of exploited funds in accordance to the protocol's exploit response procedures stipulating ongoing investigations will be halted if the attacker returns 90% of user funds."

"Firefighters have identified the exploit steps and are working to reproduce and test safety functions. A full post mortem will be delivered after details are confirmed."

"A compensation plan for addresses affected by the exploit has also been established. The compensation plan will go into effect in addition to and not determinate of the potential return of funds. "

"Update the _limitFees function to correctly limit fees even if they are generated only with one token. When the compound function is called for a second time in one block, claim any pending fees as protocol fees."

This is a global/international case not involving a specific country.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

• Known history of when and how the service was started.
• What problems does the company or service claim to solve?
• What marketing materials were used by the firm or business?
• Audits performed, and excerpts that may have been included.
• Business registration documents shown (fake or legitimate).
• How were people recruited to participate?
• Public warnings and announcements prior to the event.

Don't Include:

• Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
• Anything that wasn't reasonably knowable at the time of the event.

There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.

The Reality

This sections is included if a case involved deception or information that was unknown at the time. Examples include:

• When the service was actually started (if different than the "official story").
• Who actually ran a service and their own personal history.
• How the service was structured behind the scenes. (For example, there was no "trading bot".)
• Details of what audits reported and how vulnerabilities were missed during auditing.

What Happened

The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.

Key Event Timeline - Lava Lending Flash Loan Attack

Date	Event	Description
March 28th, 2024 4:57:33 PM MDT	Attack Transaction	The attack occurs against the Lava Lending protocol.
March 28th, 2024 10:42:00 PM MDT	Tweet Posted	A tweet is posted about the incident being looked into.
March 28th, 2024 10:45:00 PM MDT	Lending Market Paused	The lending market is reportedly paused as the incident is being looked into.
April 2nd, 2024 12:16:55 PM MDT	PostMortem Released	A postmortem is released on HackMD.

Technical Details

This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

Total Amount Lost

The total amount lost has been estimated at $340,000 USD.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

Immediate Reactions

How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

Ultimate Outcome

What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

Total Amount Recovered

There do not appear to have been any funds recovered in this case.

What funds were recovered? What funds were reimbursed for those affected users?

Ongoing Developments

What parts of this case are still remaining to be concluded?

Individual Prevention Policies

No specific policies for individual prevention have yet been identified in this case.

For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.

Platform Prevention Policies

Policies for platforms to take to prevent this situation have not yet been selected in this case.

For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.

Regulatory Prevention Policies

No specific regulatory policies have yet been identified in this case.

For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.