            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-1FB9E38092E8
                
Infrastructure Scan
ADDRESS: 0x84d960ab0090cdea3f2672dbd154408ee5a48e52
DEPLOYED: 2026-04-30 18:02:47
LAST_TX: 2026-04-30 19:40:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Active_Trace_Protocol
VISIBILITY: UNFINISHED_STATE_DETECTION

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

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Recovery mode: OFF. Debugging symbols: ENABLED. [NET] Routing traffic through secure SSL-tunnel… [FETCH] Swarm source detected. Downloading metadata… [SCAN] Mapping internal logic flow and branching. [MEM] Virtual memory mapped: 0x0000 -> 0x7ac0. [VULN] Risk detected: Ownership can be renounced by anyone. [SIM] Mocking MSG.SENDER as 0x541a37be23d515a6477807e6160ed0a65d4c2933. [TRACE] Bytecode segment 0x50 analysed. [VALID] Comparing result with Triada-Security-Standard. [DONE] Scan task E43F803C finished in 52s.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x4d6d27431c7991b02bbff73b6ff3b013f2da5b73 0x23ebaae54db96bb7d5010fee4f508c074fa0e217 0x3088d8fdb914be78baac80361f7453dc7aec7f44 0xf3387cbdf35a03c8d23282b115ffab6b83b5648a 0x1b02ee7a57c81826ebc7586b388c8010cf905c40 0xcd29ba07e732a2099ea7c03cbb4e80ad814b8b21 0x4dfcab024f8bf5e4fc735ac7ef1d0851d81cebef 0xd256a9f833bae5d1179a0e03f4a569445251da80 0x1756b2b23077f09fa120475dd34b5666ec6f63ab 0xb04d7eea9009f24b979cabd4f80cf867b7846e1c 0x185c80966548d8c1c29289d4579a3e85e01a7134 0xa602e32da1f5468689a81a1c1f03e27a861f00af 0x8b9234b808ed1878e1f820ac64ad4946295b17fc 0x09c686f0ed978b4a47f4a41da4cf32eb62410891 0x057e4f1612c352dc6616598c6609da01003b071c 0xb44e8f51a81a4e3a195c4c0efe0f288aac2f8804 0xc821ecf5b535ae05e707fbff7bf0fa8f96183bb6 0x95f12a3aac50218c717d6c1d0cd7ef33d03bd545 0xfbaaa4c60353532ec780968de47ec4e786a4cf1e 0xf3010e34a4d0436713d299f4a93df48ca1e45582
SAFETY PROTOCOL FAILED: Safety Report 0x84d960ab0090cdea3f2672dbd154408ee5a48e52: Debug-Interface Security Flaw

Leave a Comment Cancel Reply
