How much was lost in the Boring Nakas hack?

The Boring Nakas hack resulted in $108K in losses on June 30, 2023.

What attack technique was used in the Boring Nakas exploit?

The Boring Nakas 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.

Boring Nakas Hack

TOTAL LOST $108K

Low Jun 30, 2023 Rugpull

Affected Chain 2023 Incident surface

Recovered - No recovery reported

All-Time Rank #1502 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

Quick Summary

Boring Nakas project faced a rugpull, causing a loss of 108,439 $USD by the token deployer.

Details of the Exploit

Boring Nakas is an ERC20 token that fell victim to a rugpull. The deployer of the project used a privileged function to withdraw 58.207 $ETH, equivalent to 108,439 $USD from the token contract. All the stolen funds were then transferred to another address and subsequently deposited into the Coinbase Exchange.

Block Data Reference

Scammer Address:

https://etherscan.com/address/0x57220b0f…B3867E

Withdrawal Transaction:

https://etherscan.com/tx/0xbf655779…58c7fd

Funds Transfer Transactions:

https://etherscan.com/tx/0x9c7afadc…31cd15

https://etherscan.com/tx/0xd624ac15…81191a

Incident Report

Protocol / Project Boring Nakas

Date of Incident June 30, 2023

Attack Technique Rugpull

Classification Token

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token BNAKA

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 Boring Nakas'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 Boring Nakas, 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/cyversalerts/status/1675769161673318400

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Token
Year 2023

Learn to Prevent the Next Boring Nakas

The Boring Nakas 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