How much was lost in the Beamsplittr hack?

The Beamsplittr hack resulted in $61K in losses on June 27, 2023.

What attack technique was used in the Beamsplittr exploit?

The Beamsplittr exploit utilized Rugpull. Understanding this attack vector is critical for smart contract auditors and developers building secure DeFi protocols.

How can developers prevent similar smart contract attacks?

Preventing smart contract hacks requires a combination of secure coding practices, thorough security audits, and understanding common attack vectors like reentrancy, oracle manipulation, and access control flaws. Smart Contract Hacking (SCH) provides hands-on training to help developers and auditors identify and prevent vulnerabilities before deployment.

Beamsplittr Hack

TOTAL LOST $61K

Low Jun 27, 2023 Rugpull

Affected Chain 2023 Incident surface

Recovered - No recovery reported

All-Time Rank #1673 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

Quick Summary

Beamsplittr project was rugpulled with 60,824 $USD lost by the deployer using a privileged function.

Details of the Exploit

Beamsplittr, an Ethereum-based token, fell victim to a rugpull by its deployer. Using a privileged function 'collectTaxDistribution', the deployer minted and sold 9,990,000,000,000 $BSPLT tokens for 31.98 $ETH, draining the UniSwap pool, and causing a loss of 60,824 $USD. The stolen funds were transferred to another EOA address and then deposited into the Incognito protocol.

Block Data Reference

Scammer Address:

https://etherscan.io/address/0x1BA8ff40…EC3533

Liquidity Draining Transaction:

https://etherscan.io/tx/0xe637b595…17e633

Deposit Transaction:

https://etherscan.io/tx/0xfb1405c2…f17494

Incident Report

Protocol / Project Beamsplittr

Date of Incident June 27, 2023

Attack Technique Rugpull

Classification Token

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token BSPLT

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 rugpull 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 Beamsplittr'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? Hard to catch — private key / OpSec failures are outside smart contract audit scope

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

Verify all logic paths related to Rugpull 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

01
Source 1 https://twitter.com/CertiKAlert/status/1673543606496550913?s=20

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Token
Year 2023

Learn to Prevent the Next Beamsplittr

The Beamsplittr 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.

Start Free Trial Browse Attack Library