HIGHecrecover without invalid-signature protection
MEDIUMStrict equality on balances/tokens
MEDIUMStrict equality on balances/tokens
LOWMissing zero-address check
LOWMissing zero-address check
LOWReentrancy without state impact (benign)
LOWReentrancy without state impact (benign)
LOWblock.timestamp dependence
LOWblock.timestamp dependence
LOWblock.timestamp dependence
LOWblock.timestamp dependence
LOWblock.timestamp dependence
LOWblock.timestamp dependence
LOWblock.timestamp dependence
INFORMATIONALReentrancy detected via event emission order
INFORMATIONALReentrancy detected via event emission order
INFORMATIONALInline assembly usage
INFORMATIONALFloating pragma
INFORMATIONALOutdated Solidity compiler
INFORMATIONALOutdated Solidity compiler
INFORMATIONALOutdated Solidity compiler
INFORMATIONALLow-level call usage
INFORMATIONALNaming convention violation
INFORMATIONALNaming convention violation
INFORMATIONALNaming convention violation
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.
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.