LOGIC GATE EXPOSED: 0x2eeca49f09ad67a447db3509b33e67959ce6e3f0 :: Logic Integrity: Exposed Debug-Mode Interface

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-56B205D1076A
                
Infrastructure Scan
ADDRESS: 0x2eeca49f09ad67a447db3509b33e67959ce6e3f0
DEPLOYED: 2026-05-02 03:13:59
LAST_TX: 2026-05-05 12:08:35

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Active_Trace_Protocol
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] Latency: 14ms. Protocol: JSON-RPC 2.0. [FETCH] Entry point found at offset 0x3eec. [SCAN] Running static analysis on JUMP instructions… [MEM] Tracking pointer 0xc195e4e0 in memory heap. [VULN] Testing for ‘Reentrancy’ via external call trace. [SIM] Verifying ‘require’ statements integrity. [TRACE] Bytecode segment 0x60 analysed. [VALID] Consensus reached on node cluster: 8/10. [DONE] Results pushed to ADMIN_DASHBOARD.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x2e09b7671c472ca7444525aaca8ac831a4d51485 0xc4891885ae0a7afd9c3432f569cfcb0c69d4b880 0x0dbf0766e71abf7771309475039862fee6a3d3e9 0x80e01cc9a202658674e31e1d57767abd12d27316 0x187466617457d04ff24c9983883bd2264c0c6b9b 0x9deae75db00d53f14f5f3cf8b1866fb39444724c 0x5bde3fbb5b210ad2d846709cd68ac125ff616b01 0x2e9e6e4903057c72b4108af3d90d09449460eda2 0x5684247ca31ecbec7f74f090fe1d424b1bf83d9e 0x48206636a44d95cc3157dcaf2a9bed5e5ba9305d 0x21f5d62dc5c5bca0efb63273243b58edc44f9720 0xe58d27ef8ca47048ec3c099d9e29e2b8fd717d99 0x3f58698573aa8baf894ee023cb744dfe4ee29474 0x67958f0fca0f31ecfcd1715900e088ade06b8764 0x29e485ce51a4df0b9f4e468855c1c9b4145bdee2 0x4206950a1cad491ec5800529bbf73c62c3ed9a26 0xa9da0d4ec314aefb53c73c87a9f04db3bdf40549 0x55d2d91a2523066c03bb2c481191700c62ef2e56 0xbf898db3476fea3132cc338ba19185cb6738c2d3 0x34e05dd9843f956153535b158d0369d3e4061eb8

LOGIC GATE EXPOSED: 0x2eeca49f09ad67a447db3509b33e67959ce6e3f0 :: Logic Integrity: Exposed Debug-Mode Interface

Previous PostCORE STABILITY RISK: 0xc61f2c70c840c3033a814dc30fc73a0337a2c35c :: Core Analysis: Debug Mode Flag Persistence

Next PostSECURITY CLEARANCE REVOKED: 0xc27ccb8996476fb9146ba8ba15d6d24202a7335b :: Security Clearance Failed: Debug Gate Active