Quint Hack

TOTAL LOST $130K
Low Other

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1436 By amount stolen
Auditors 1 Prior security audit

Incident Overview

The Quint project was attacked by hackers in the amount of $130K. The attacker took advantage of the vulnerability, thanks to which he was able to withdraw his rewards again.

Quint is a stacking and farming platform where users can stake $QUINT at low transaction fees while enjoying the rewards in the form of a variety of tokens.

The attack occurred due to a vulnerability in the contract called by the reStake() function. When this function is performed, the reward time in LP tokens is not updated, as a result an attacker can claim the issued rewards several times.

Attacker account addresses:

1) https://bscscan.com/address/0x82f42c11…c87fca

2) https://bscscan.com/address/0xcBd00C9A…48117F

3) https://bscscan.com/address/0xa59D3d89…59992d

Incident Report

Protocol / Project Quint
Date of Incident
Attack Technique Other
Classification NFT,Other
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Affected Token QUINT
Official Website quint.io/
Protocol Twitter/X @projectquint
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
Platform DeFi Interoperability Ethereum Ecosystem Real World Assets Protocols Binance Ecosystem Binance Listing ISO 20022

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 Quint's contract logic - root cause: nft,other
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 Audit Report 1 — still lost $130K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • 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

Security Audit History

Sources & References

Learn to Prevent the Next Quint

The Quint 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