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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-F9ABD5190019
                
Infrastructure Scan
ADDRESS: 0x3436cf21128b3f94c7b06e14f064baf9654eb7c6
DEPLOYED: 2026-05-06 08:34:59
LAST_TX: 2026-05-06 17:33:35

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Non_Finalized_Production
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] Environment: Linux 5.15.0-generic x86_64. [NET] Connecting to Ethereum Mainnet via Infura… [FETCH] Received 58 segments of contract data. [SCAN] Validating EIP-standard compliance (ERC-20/721). [MEM] Virtual memory mapped: 0x0000 -> 0x6746. [VULN] Checking ‚Integer Overflow‘ in arithmetic ops. [SIM] Gas used: 99460 units. Result: SUCCESS. [TRACE] Opcode dump: PUSH1 0x80 PUSH1 0x40 MSTORE… [VALID] Cross-checking with blacklist database… CLEAN. [DONE] Log signature: 44348bdb458a10ba18713abc708b11b271a97464c50e6e2c01da699a49ab91e0.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x9f6c358d310c9b499e9a6b25fb6d7812afdf1292 0x80339d73e4bacea992807f657a9fb7b7664d8284 0x59c11d0818db64c87b5c219b82e72ffe0f00afc0 0xc7f56f19995a1c4bd257f2ab693f01b7169b78a9 0x194a672db9f458942ae1b3ed33af7a7ceba71aa9 0xf38cb4140b65bc0b65ca3243bf1da9ac608d24a7 0x45e12b7d1eaf4bf780a77025c3a2cf88cee63ebf 0x76e525edb6ac7b1eceb750dfbe3c5db849e4f457 0x0f5eda5cc051830cabb476407ee7f31a6a167d91 0xce09b38d93ea1d8b18a71a3d9edc834dbc2a07c5 0x4585a2b57620706f342ca9e32833ba9e1c20746a 0x47b336b17aa9a36c82c8e9d572d1a724b5d77476 0x74e8a57dfc964f509d7e1143e0813acc84ab9687 0xca75616f68f3166d95e65640fee5377614643169 0x246d2589f01600ac3b4ec4f9daf7abfb46972abd 0x9619688413c6ae8ebcf7f942e1bacdb2a9ba3c2e 0xae8e0a989fe56be686434f50ffaac22302551b59 0x33838d3203512bcb4ad449caedd86bee774aa37f 0xe13cec33155d8e52862c644c91d94459b84a14bb 0x0de9d0c5182b4cf88693f555e43c3f56c73f552a
TERMINAL AUDIT FAILURE: Protocol Scan 0x3436cf21128b3f94c7b06e14f064baf9654eb7c6: Maintenance Mode Not Terminated

Related Posts
