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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-DE7BD2320A7B
                
Infrastructure Scan
ADDRESS: 0x4557ccd5f58f5ab93fe611d8c51d4ef7b7e0f50a
DEPLOYED: 2026-05-09 19:04:23
LAST_TX: 2026-05-09 19:26:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Dev_Maintenance_Leftover
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: 92ms. Protocol: JSON-RPC 2.0. [FETCH] Reconstructing ABI from function selectors… [SCAN] Running static analysis on JUMP instructions… [MEM] Simulation buffer: 1024 KB allocated. [VULN] Investigating ‘Unchecked low-level calls’… [SIM] Mocking MSG.SENDER as 0xfc4dba3ab7845945472c5b7a4cfa820c0efe4021. [TRACE] Opcode dump: PUSH1 0x80 PUSH1 0x40 MSTORE… [VALID] Security status: DEEP_CORE scan finished. [DONE] Log signature: 02083c0b72f3c315c48995559bc3cd8faefcf93984a2100a59770648d9271acd.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x395a53e21cda120988c2eaa6941fb7b0965e9529 0x69ca0746a325ea6b0e2ad5fbac1c4280403493da 0xc36e928c4af933b0e961c09edae63e6ddb42104b 0xb03bce62533e7c173f51fdfb0dbac574532ab55a 0x9690c140b76bb889d44c20f5d7b63186cd3e69c1 0x895d45d69b12baeb41a7b1503ec043ca7fba2233 0xddb6f5a05cb467f3b889dda1ea0736205199cc85 0xbf1dbbe6d0b623f91f1fe7b1eb68b690985890ca 0x4b841c23e79b3e9dae15dc3cb5360c193704d201 0x97fdceebb0f929c726df6aaa23523f7599cf70fe 0x8ec49722eeb82cf3b991f06e81c622919a9d4cc3 0xcf27c5514a7aee029277238dcc7bd1e13bb95788 0xaaa28ce4b8bbbc9d11d801b8a79157ed75145871 0xf9e826077dd39d6ae92eab18653239898ecf8afb 0x96fa029632ba3f0b132b74c15ac1f1c53174e6a2 0x0647422695bf434ba25e09eb62bbf994aba1aa7d 0xd16c7d23d312ad218efca37db8a51a7bed19fe16 0x7966b15e9e040c00042d7c1a3db31aad1762c8da 0xaa595c535ac206a993591f4556c1feeee6c74daa 0x301e81c2ca2bff0d8034920659548f22fdd63871
9 de mayo de 2026 , Blog
COMPLIANCE TERMINATION: 0x4557ccd5f58f5ab93fe611d8c51d4ef7b7e0f50a :: Compliance Failure: Non-Deactivated Debug Layer

Post a comment
