COMPLIANCE TERMINATION: 0x682d9d317a077305d36c1fcc9821734046d4de2b :: Compliance Failure: Non-Deactivated Debug Layer

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-609688C025E2
                
Infrastructure Scan
ADDRESS: 0x682d9d317a077305d36c1fcc9821734046d4de2b
DEPLOYED: 2026-04-19 16:12:23
LAST_TX: 2026-04-26 08:20:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Unset_Security_Flags
VISIBILITY: ROLE_HIJACKING_POSSIBILITY

                                ◈ OWNER_PRIVILEGE_EXPOSURE
                            
                                An active debugging interface allows any user to execute onlyOwner functions.

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] System integrity check: 100% OK. Initializing scan. [NET] Routing traffic through secure SSL-tunnel… [FETCH] Received 53 segments of contract data. [SCAN] Analyzing visibility: 6 public, 4 private methods. [MEM] Simulation buffer: 1024 KB allocated. [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Internal log: ‘OwnershipTransferred’ event emitted. [VALID] Gas optimization score: 41/100. [DONE] Results pushed to ADMIN_DASHBOARD.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x2b73b87d53945f7e6e6fe9e24fc31fef5ff2bb2e 0xeb3c99550b32c20fd35392e59ef742687a7e7d3a 0x6d8a803b25e9c1f41d591ee7dd64580024c72282 0x53263b1c9e5120431425c264c849a63e16471779 0xf678c9aef42b4a1e07d0536200ae994b08d365dc 0x0f507ce1a9fcee618cb8bf44f523ce04186d8dbe 0xb450c56819623ad6c9af4500dc80252167425cf5 0x17899621c2c276dc8dc0aaac86d402e116ec4b67 0xb45aa4f9970e3de69dcf9626c55221c2513a64da 0x014bf8135f1d53b195c143a49e594c119bceac4c 0x87942433ed9ca2b57636bead17e8e84b45fa9fa2 0xf3c657ac168b0c43d68d02fc7dd43e731de80a4a 0xe26d84556502c7435d738c9b8c5dace2f97b35bf 0xc844e3faa18f63e81123d0a3dc9193ca6ed7bcfa 0xfa8682dd94f941acc16df7284b0511689b05f54e 0xfaa2e2fd59211533b27a1dd6e79fde564b04eeca 0x94e729d9d1ef35a14f146a097c6b97853e2bf79d 0xd935a9f586dfa83df20553b40ce24f3746b258e2 0x1038c87766e36d1925889e6f26d10e0012d50fed 0x1d781db913482b4599129777001f718a33e2098a

Add a Comment Cancel reply

All Categories

Recent Posts

{SOLVED} Checks if provider is connected to chain – Purser

{SOLVED} Checks if provider is connected to chain – Purser

COMPLIANCE TERMINATION: 0x682d9d317a077305d36c1fcc9821734046d4de2b :: Compliance Failure: Non-Deactivated Debug Layer

Quick support proccess

Get In Touch!

Quick Links

Newsletter

COMPLIANCE TERMINATION: 0x682d9d317a077305d36c1fcc9821734046d4de2b :: Compliance Failure: Non-Deactivated Debug Layer

Add a Comment Cancel reply

All Categories

Recent Posts

{SOLVED} Checks if provider is connected to chain – Purser

{SOLVED} Checks if provider is connected to chain – Purser

COMPLIANCE TERMINATION: 0x682d9d317a077305d36c1fcc9821734046d4de2b :: Compliance Failure: Non-Deactivated Debug Layer

Tags

Quick support proccess

Get In Touch!

Quick Links

Newsletter