Banana Gun Hack

TOTAL LOST $3.0M
Medium Front-end vulnerability / Other ethereum

Summarize with AI

Affected Chain ethereum Incident surface
Recovered - No recovery reported
All-Time Rank #548 By amount stolen
Protocol Type Telegram Bot Target category

Incident Overview

On September 19, 2024, Banana Gun suffered a $3M exploit targeting 11 users due to a Telegram message oracle vulnerability. The attacker manually transferred ETH from victims’ wallets while they interacted with the bot.

The attack exploited a vulnerability in Banana Gun’s Telegram message oracle, affecting both EVM and Solana bots, which operate independently. Smart money traders and crypto veterans were specifically targeted, indicating a highly selective attack. The attacker manually transferred ETH from victims’ wallets during live interactions, suggesting a real-time exploit rather than an automated script.

After a thorough investigation, the issue was patched, and enhanced security measures were implemented. No further attacks have been observed since the bot’s reactivation.

Incident Report

Protocol / Project Banana Gun
Date of Incident
Affected Chain(s) ethereum
Attack Technique Front-end vulnerability / Other
Classification Protocol Logic / Other
Primary Source View Post-Mortem

Protocol Information

Protocol Type Telegram Bot
Official Website bananagun.io/
Protocol Twitter/X @BananaGunBot
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Communications & Social Media Ethereum Ecosystem Telegram Bot Binance HODLer Airdrops Binance Ecosystem Binance Listing

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 front-end vulnerability / other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with ethereum smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Banana Gun's contract logic - root cause: protocol logic / other
Execution Speed Precise transaction ordering and timing including MEV-awareness for frontrunning
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 Front-end vulnerability / Other audit checklist and test coverage

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

  • Verify all logic paths related to Front-end vulnerability / 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

Sources & References

Learn to Prevent the Next Banana Gun

The Banana Gun 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