Fortress Loans Hack
Incident Overview
Fortress Loans was attacked due to oracle vulnerability. An attacker was able to manipulate the project's oracle which allowed them to borrow differrent number of tokens for the amount of ~$3m (~1k ETH and 400k DAI).
Fortress Protocol is a decentralized marketplace for Lenders and Borrowers with Borderless Stablecoins. Fortress Loans became a victim of attacker that manipulate with the price oracle, which made possible to get about $3m and launder them through the TornadoCache.
Attack flow:
Attacker created unverified smart-contract (https://bscscan.com/tx/0x4800928c…af5039) which was later used to send a series of transactions (https://bscscan.com/tx/0x13d19809…b061bf).
A series of transactions allowed them to propose Fortress Governor Alfa contract with a malicious proposal, for which they themselves voted to set the FTS extremely valuable. The attacker then borrowed a huge amount of tokens that exchanged for ETH and DAI. Then all stollen funds were transferred across the bridge to the Ethereum network and laundered via TornadoCache.
As the time of this writing information on this case is scarce. More sources will be added if the case should develop.
Attacker address on BSC: https://bscscan.com/address/0xA6AF2872…5d22Ad
Attacker address on ETH. Here all the stolen funds were laundered through TornadoCache: https://etherscan.io/address/0xA6AF2872…5d22Ad
Bridging transaction from BSC to ETH:
BSC: https://bscscan.com/tx/0x36fd458d…7e9eea
ETH: https://etherscan.io/tx/0xcf852b02…543af5
Attacker's smart-contract (BSC): https://bscscan.com/address/0xcd337b92…463a45
Attack transaction: https://bscscan.com/tx/0x13d19809…b061bf
Incident Report
Protocol Information
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Fortress Loans, these are the critical security checks that could have prevented this incident (May 2022).
- Verify all logic paths related to Governance and Oracle Exploit / Other are guarded by proper access controls and input validation - see the Oracle Manipulation & Price Manipulation attack class for patterns
- Audit oracle price feeds for manipulation risks - ensure time-weighted average prices (TWAPs) or multi-source aggregators are used, not spot prices
- 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Proof-of-Concept Exploits
On-Chain Evidence & References
Sources & References
-
01
Source 1 https://rekt.news/fortress-rekt/
- 02
Learn to Prevent the Next Fortress Loans
The Fortress Loans 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.