๐Ÿ” TokenERC1155

๐Ÿ“ 0x9326a154cF04e1268a47774cc276f62568bfD376 ยท ๐ŸŒ GNOSIS ยท ๐Ÿค– engine: heuristic
๐Ÿ’ฐ Balance: 0.0 ยท ๐Ÿ“ˆ Tx: 0

CRITICAL 2 HIGH 2 MEDIUM 0 LOW 2

Findings preview

CRITICALSensitive function without explicit access control
CRITICALSensitive function without explicit access control
HIGHSignature replay (missing nonce/cleanup)
HIGHAuthorization bypass via multicall/batch (self-referential call)
LOWFloating compiler version (^ or >=)
LOWLogic depends on block.timestamp
INFORMATIONALSensitive function without explicit access control
INFORMATIONALCross-chain bridge exploit (forged message / delegate hijack)
INFORMATIONALAMM pair reserve manipulation (privileged burn / sync)
INFORMATIONALToken mechanic incompatibility (deflationary/rebasing/fee-on-transfer)
INFORMATIONALInsufficient input validation (arbitrary address/param)
INFORMATIONALSmart account vulnerability (ERC-4337/7579 init/signature)
INFORMATIONALTransfer logic flaw (custom hook / fee-on-transfer desync)

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 (heuristic). Static analysis only unless noted as PoC-confirmed โ€” not a substitute for a manual audit before mainnet deployment with real funds.