HGM, AGSC Hack

TOTAL LOST $75K
Low Phishing

Summarize with AI

Affected Chain 2024 Incident surface
Recovered - No recovery reported
All-Time Rank #1617 By amount stolen
Protocol Type Exploit/Phishing Target category

Incident Overview

Suspicious transactions involving Ant God Share Coin and Home Gould Mine (HGM) on the Binance Smart Chain (BSC) have been detected, resulting in a total loss of $75,000.

Multiple transactions involving Ant God Share Coin and Home Gould Mine (HGM) on the Binance Smart Chain (BSC) were revealed as suspicious. These transactions resulted in a collective loss of $75,000. The attacker was funded by Tornado Cash.

Following the attack, the stolen funds were deposited into an address associated with Tornado Cashas well.

Exploiter:

https://bscscan.com/address/0x27aeaa87…dc9204#internaltx

Attack tx:

https://bscscan.com/tx/0x91a35e2b…e36134

https://bscscan.com/tx/0xa49d5c9b…5f1da2

Example of Tornado Cash deposit

Incident Report

Protocol / Project HGM, AGSC
Date of Incident
Attack Technique Phishing
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Phishing
Team Anonymous
Source Code Unverified

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 phishing 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 HGM, AGSC's contract logic - root cause: token
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 Phishing audit checklist and test coverage

If you're auditing a protocol with similar architecture to HGM, AGSC, these are the critical security checks that could have prevented this incident (March 2024).

  • Verify all logic paths related to Phishing are guarded by proper access controls and input validation - see the Phishing Attacks attack class for patterns
  • 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

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Phishing Attacks examples →

Sources & References

Learn to Prevent the Next HGM, AGSC

The HGM, AGSC 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