SashimiSwap Hack

TOTAL LOST $317K
Low Flash Loan Attack

Summarize with AI

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

Incident Overview

The attacker's address:

https://etherscan.io/address/0xa8189407…f55908

The transactions behind the attack :

https://etherscan.io/tx/0x713c2ce2…9bf069

https://bscscan.com/tx/0xdf719d25…cc3387

https://hecoinfo.com/tx/0xecde0b38…366438

The attacker used a bug in the calculations that are different from Uniswap. Due to fact that all tokens sit in one contract, he escalated it by:

- adding two fake tokens

- adding liquidity between both tokens and WETH/fake token

- swapping between UNI/WETH/fake tokens

- removing liquidity

Total funds were stolen:

- 80 ETH (Ethereum)

- 10,000 DAI (Ethereum)

- 45,000 USDT (HECO)

Stolen funds were deposited into Tornado Cash mixer:

https://bloxy.info/txs/calls_from/0xa8189407…f55908?signature_id=994162&smart_contract_address_bin=0x722122df…5b6967

Incident Report

Protocol / Project SashimiSwap
Date of Incident
Attack Technique Flash Loan Attack
Classification Exchange (DEX)

Protocol Information

Protocol Type Dexs
Affected Token SASHIMI
Official Website sashimi.cool/
Protocol Twitter/X @SASHIMISASHIMI5
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Collectibles & NFTs Decentralized Exchange (DEX) Token DeFi Gaming DAO Ethereum Ecosystem Yield Farming AMM

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 SashimiSwap's contract logic - root cause: exchange (dex)
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
Audited by Audit Report 1 — still lost $317K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • 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

Security Audit History

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 SashimiSwap

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