CRITICALETH sent to an arbitrary, user-controlled address
CRITICALInitializer without access control
MEDIUMStrict equality on balances/tokens
MEDIUMStrict equality on balances/tokens
MEDIUMLocal variable used before initialization
MEDIUMReturn value of an external call ignored
MEDIUMVariable overwritten before its value is read
MEDIUMLow-level call return value not checked
MEDIUMContract can receive ETH but has no withdrawal path
LOWMissing zero-address check
LOWMissing zero-address check
LOWMissing zero-address check
INFORMATIONALReentrancy detected via event emission order
INFORMATIONALReentrancy detected via event emission order
INFORMATIONALLow-level call usage
INFORMATIONALNaming convention violation
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.