Jointventure Finance Hack
Incident Overview
The contract deployer has locked part of tokens at:
https://etherscan.io/tx/0x6077ef8c…3c4dbc
The contract deployer added initial liquidity at:
https://etherscan.io/tx/0xde4ad6af…f4ed7e
The contract deployer used hidden minting functionality under the burnFrom() function to generate new tokens onto his wallet at:
https://etherscan.io/tx/0xa9d1f673…f4415e
The minted tokens were sold by the contract deployer at:
https://etherscan.io/tx/0x05e5b1fd…22439b
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 Jointventure Finance, these are the critical security checks that could have prevented this incident (January 2021).
- Verify all logic paths related to Rugpull 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 TrialLearn to Prevent the Next Jointventure Finance
The Jointventure 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.