3913 token Hack

TOTAL LOST $31K
Low Flash Loan Attack

Summarize with AI

Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #1819 By amount stolen
Protocol Type Exploit/Flash Loan Attack Target category

Incident Overview

Deflationary token 3913 suffers a $31,354 USD loss in a flash loan attack on BNB Smart Chain.

On November 2, 2023, the deflationary token 3913 on BNB Smart Chain was exploited through a flash loan attack. The attacker utilized a loophole in the token's in_transfer function, which was designed to give bonuses to new token holders when a Pancake pair sends tokens to the new user. However, the contract failed to account for a malicious user forcing a Pancake/Uniswap pair to transfer tokens to any address via a skim() call.

The attacker took a flash loan, bought 3913 tokens, and repeatedly transferred these tokens to the pair address while calling skim(), tricking the contract into giving away all available bonuses. As of November 20, 2023, the stolen funds, amounting to $31,354.82 USD, still remain in the scammer's address as BSC-USD.

Attacker address:

https://bscscan.com/address/0xb29F18B8…8D8ae7

Malicious transaction:

https://bscscan.com/tx/0x8163738d…6199ed

Malicious contract:

https://bscscan.com/address/0x783FBEa4…025E83

Incident Report

Protocol / Project 3913 token
Date of Incident
Attack Technique Flash Loan Attack
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Flash Loan Attack
Affected Token 3913
Team Anonymous
Source Code Verified On-Chain

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 flash loan attack and Solidity and EVM internals
Capital Required Flash loan capital (borrowed atomically, zero upfront cost)
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in 3913 token'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? Yes — skilled auditors routinely flag Flash Loan Attack vulnerabilities in code review

If you're auditing a protocol with similar architecture to 3913 token, these are the critical security checks that could have prevented this incident (November 2023).

  • Verify all logic paths related to Flash Loan Attack are guarded by proper access controls and input validation - see the Flash Loans 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 Flash Loans Attacks examples →

Sources & References

Learn to Prevent the Next 3913 token

The 3913 token 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