FilDA Hack

TOTAL LOST $2.0M
Medium Other

Summarize with AI

Affected Chain 2023 Incident surface
Recovered $229K 11.5% returned
All-Time Rank #647 By amount stolen
Auditors 1 Prior security audit

Incident Overview

On April 12th, 2022, an exploit occurred on FilDA resulting in compromised funds of up to $2 million. The dev team has identified the root cause and suspended all deposits and borrowing on FilDA-ESC. FilDA contracts on other chains remain unaffected.

The compromised funds amount to around 1.6 million USD and were mainly in the form of USDC, HUSD, BUSD, BTC, and ETH. The root cause of the issue is due to the protocol's inability to handle flashloans of ERC677 tokens properly. The attacker used a flashloan to borrow the underlying token, which was then deposited into the protocol via a callback function controlled by the attacker.

This resulted in lots of extra f tokens being minted. The borrowed token was then returned to the protocol via a flashloan callback, but lots of fTokens were left to the attacker, allowing them to redeem most of the cash in the lending pool. FilDA on other chains is not affected since the issue is only related to ERC677 tokens.

Attacker Address: 0x4a9a0cC1…858874

Money Laundering address: 0x93c3A805…6a4d74

Attacker contract: 0x00Ff915E…D05BC3

Incident Report

Protocol / Project FilDA
Date of Incident
Attack Technique Other
Classification Borrowing and Lending

Protocol Information

Protocol Type Lending
Affected Token FILDA
Official Website www.filda.io/bank
Protocol Twitter/X @FilDAFinance
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
HECO Ecosystem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in FilDA's contract logic - root cause: borrowing and lending
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Other audit checklist and test coverage
Audited by Certik — still lost $2.0M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to FilDA, these are the critical security checks that could have prevented this incident (April 2023).

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Funds Recovery

11.5%

Recovered

$229K

Net Loss

1770000

Security Audit History

Post-Incident Timeline

  • 2023-04-24

    Filda Team announced about returning funds. 160,000 $ELO and 21,000 $DAI were returned which is worth 229,000 $USD in total at the moment.

Sources & References

Learn to Prevent the Next FilDA

The FilDA hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial