MEDIUMContract can receive ETH but has no withdrawal path
INFORMATIONALInline assembly usage
INFORMATIONALInline assembly usage
INFORMATIONALInline assembly usage
INFORMATIONALInline assembly usage
INFORMATIONALOutdated Solidity compiler
INFORMATIONALOutdated Solidity compiler
INFORMATIONALNaming convention violation
INFORMATIONALNaming convention violation
INFORMATIONALNaming convention violation
INFORMATIONALNaming convention violation
INFORMATIONALLarge numeric literal (hard to verify by eye)
INFORMATIONALLarge numeric literal (hard to verify by eye)
INFORMATIONALLarge numeric literal (hard to verify by eye)
OPTIMIZATIONPublic function that could be external
OPTIMIZATIONPublic function that could be external
OPTIMIZATIONAccess control issue (manual review required)
OPTIMIZATIONAccess control issue (manual review required)
OPTIMIZATIONAccess control issue (manual review required)
OPTIMIZATIONAccess control issue (manual review required)
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.
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.