Typus Finance Hack
Incident Overview
On October 15, 2025, Typus Finance suffered an oracle manipulation exploit that drained approximately $3.44 million from the TLP (Typus Liquidity Pool) contract on the Sui blockchain. The attacker exploited a missing authorization check in the oracle module to manipulate prices and drain 588,357.9 SUI, 1,604,034.7 USDC, 0.6 xBTC, and 32.227 suiETH before the protocol was paused within 15 minutes of detection.
The vulnerability stemmed from a missing assert check in the update_v2 function of the oracle module, which effectively bypassed authorization controls and allowed any address to update oracle prices without proper validation. This oracle module was originally deployed on November 13, 2024, but was not included in the scope of Typus Finance's May 2025 audit conducted by MoveBit. The attacker exploited this flaw to manipulate price feeds and drain assets from the TLP contract.
The first malicious transaction occurred at 13:05 UTC, with the team being alerted by a community member at 13:24 UTC. Within 15 minutes (by 13:39 UTC), all smart contracts were paused to prevent further damage. The exploit was isolated to the TLP contract, with user funds in personal wallets, SAFU vaults, DeFi Options Vaults, and user collateral for open positions remaining secure due to independent oracle verification systems.
Incident Report
Protocol Information
Market Context at Time of Hack
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 Typus Finance, these are the critical security checks that could have prevented this incident (October 2025).
- Verify all logic paths related to Oracle Issue 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:
Sources & References
Learn to Prevent the Next Typus Finance
The Typus Finance 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.