🔍 EIP173ProxyWithReceive

📍 0xE5C1936BC955d7a247f978698F781cD6849e1B36 · 🌐 ETH · 🤖 engine: slither+aderyn
💰 Balance: 0.0 · 📈 Tx: 0

CRITICAL 2 HIGH 0 MEDIUM 6 LOW 1

Findings preview

CRITICALdelegatecall to a user-controlled address
CRITICALdelegatecall to a user-controlled address
MEDIUMContract can receive ETH but has no withdrawal path
MEDIUMContract can receive ETH but has no withdrawal path
MEDIUMContract can receive ETH but has no withdrawal path
MEDIUMCentralization risk (absolute admin powers)
MEDIUMCentralization risk (absolute admin powers)
MEDIUMCentralization risk (absolute admin powers)
LOWreturn inside inline assembly
INFORMATIONALInline assembly usage
INFORMATIONALInline assembly usage
INFORMATIONALInline assembly usage
INFORMATIONALInline assembly usage
INFORMATIONALInline assembly usage
INFORMATIONALOutdated Solidity compiler
INFORMATIONALLow-level call usage
INFORMATIONALPUSH0 opcode (requires Shanghai EVM)
INFORMATIONALPUSH0 opcode (requires Shanghai EVM)
INFORMATIONALPUSH0 opcode (requires Shanghai EVM)

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.

👤
✉️
✈️
🌐
💬

Opens your email app, addressed to our team — nothing is sent from this page directly.

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.