Jumpn Finance Hack

TOTAL LOST $1.1M
Medium Rugpull

Summarize with AI

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

Incident Overview

Jumpn Finance was rugpulled and 4158 $BNB was stolen using a privileged function.

Jumpn Finance's $JST and $JAC staking pools were rugpulled. The scammer used 0x6b1d9018() privileged function on two pools and drained assets for a total 4138 $BNB. Consequently, 4100 $BNB was transferred through TornadoCash, the remaining 58 $BNB stays at the scammer's address.

Scammer address:

https://bscscan.com/address/0xd3de02b1…816982

Malicious transactions:

https://bscscan.com/tx/0x43e77e6e…65d218

https://bscscan.com/tx/0x48333962…96b72c

Withdraw transactions:

https://bscscan.com/txs?toaddress=0x0D5550d5…859b17&address=0xd3de02b1…816982

Incident Report

Protocol / Project Jumpn Finance
Date of Incident
Attack Technique Rugpull
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Affected Token JST
Official Website lumi.finance/
Protocol Twitter/X @LuminProtocol
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
DeFi Solana Ecosystem Arbitrum Ecosystem Ronin Ecosystem

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 Jumpn Finance'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
Audited by Audit Report 1 — still lost $1.1M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Jumpn Finance, these are the critical security checks that could have prevented this incident (October 2022).

  • 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

Security Audit History

Sources & References

Learn to Prevent the Next Jumpn Finance

The Jumpn Finance 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