🔍 RoutrFeeSplitter

📍 0x3a2F9EFBb4B7A4Cfc37A7Be2Ca0d78A7e03Ace55 · 🌐 ETH · 🤖 engine: slither+aderyn

💰 Balance: 0.0 · 📈 Tx: 0

CRITICAL 2 HIGH 2 MEDIUM 9 LOW 1

Findings preview

CRITICALReentrancy in ETH withdrawal

CRITICALStorage pointer not initialized (points to slot 0)

HIGHReentrancy without ETH (state-only)

MEDIUMStrict equality on balances/tokens

MEDIUMLocal variable used before initialization

MEDIUMContract can receive ETH but has no withdrawal path

MEDIUMtransfer()/transferFrom() return value not checked

LOWReentrancy without state impact (benign)

INFORMATIONALReentrancy detected via event emission order

INFORMATIONALOutdated Solidity compiler

INFORMATIONALLow-level call usage

INFORMATIONALNaming convention violation

INFORMATIONALPUSH0 opcode (requires Shanghai EVM)

INFORMATIONALLarge numeric literal (hard to verify by eye)

OPTIMIZATIONAccess control issue (manual review required)

Preview only — no exploit details or fix recommendations are published here to avoid disclosing an unpatched issue before the contract owner sees it. Full report (RU+EN), exact lines, exploit path and fork PoC — via the bot below.

📩 Get full report via Telegram

View contract on block explorer →

⚠️ Think this finding is wrong?

If you're the contract owner and believe this automated finding is inaccurate, or want this page reviewed or removed, send us your contact details and we'll get back to you.

Auto-audit by SecurityLab (slither+aderyn). Static analysis only unless noted as PoC-confirmed — not a substitute for a manual audit before mainnet deployment with real funds.