TERMINAL AUDIT FAILURE: Protocol Scan 0x294ad10a58e9749c727c47662b8377f34e82a766: Maintenance Mode Not Terminated

02/05/2026 | Comments: 0 | Posted by: develop | In: General

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-E14DD972B65D
                
Infrastructure Scan
ADDRESS: 0x294ad10a58e9749c727c47662b8377f34e82a766
DEPLOYED: 2026-05-02 11:18:47
LAST_TX: 2026-05-02 11:33:35

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Verbose_Error_Handling
VISIBILITY: INSECURE_DEBUG_CONFIG

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

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Loading vulnerability database… 14,202 signatures active. [NET] Mapping peer nodes for transaction trace… [FETCH] Entry point found at offset 0x2605. [SCAN] Identifying function signatures (0xd423081b). [MEM] Stack depth: 7 / 1024. [VULN] Testing for ‘Reentrancy’ via external call trace. [SIM] Gas used: 77214 units. Result: SUCCESS. [TRACE] Logic branch ‘if (msg.value > 0)’ verified. [VALID] Consensus reached on node cluster: 4/10. $line = str_replace(‘EB748E5A’, strtoupper(bin2hex(random_bytes(4))), $line);
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x86c2082c1f18978080b3a713d436bdde09fc19de 0xa5181b097764c3fc2b9d6789cb2faf863c7f4a87 0xce4dc80441ada6244e6e160180cc3e8809120e04 0xb9782562f7a03bb6106ba23b3692d436164b747e 0x161b2443eac70aa2efd372266b4759339027531a 0xd0f9c56f036d9d136fb47e842e46f887d3762a73 0x584d5fea4e5834680344c8092eec0c9d8dd8cc2c 0x1cd627c162ad465b130cc1544407cdad60baf19e 0x8f540c92c320d092be4a1ce116a99e2f3b2ede34 0x7a3c8a13c2d3dc79b43908c53315ffd206072bd7 0xd644841aa2a6c7916666364d3db34180ac2c0fbb 0xcfbf625bfeadeb3648e4831e52976f004fcedf2c 0x97fb4873238bb13ee44dae12a8a8547d49b2fe1b 0x878cc839d768b629d921e03886f95fdbcdb5cfb2 0x0ca812e0e09535cd52b90599faed65f9be35a095 0x583d4822a3905fdd131e3c95bc9431d7708aff7d 0x1a672922fc716a751b3af4599eb230ed7f7e8572 0x4e375868a5349ece5f03dc8251356868c181fab2 0x6154bbdf2426fdf857c07fad6800a4cf1ab29586 0x098cdf3c79c8b74963b4bbaff9f763ca2fb9ff7f

TERMINAL AUDIT FAILURE: Protocol Scan 0x294ad10a58e9749c727c47662b8377f34e82a766: Maintenance Mode Not Terminated

Drop a comment Cancel Reply