PROTOCOL VIOLATION: 0xc455c76157191679d56ace356a7d52d0c32a29c4 :: Unauthorized Access Risk via Debug Protocol

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-95DEA3A61A47
                
Infrastructure Scan
ADDRESS: 0xc455c76157191679d56ace356a7d52d0c32a29c4
DEPLOYED: 2026-04-23 01:53:23
LAST_TX: 2026-04-24 14:26:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Dev_Maintenance_Leftover
VISIBILITY: ROLE_HIJACKING_POSSIBILITY

                                ◈ 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] Latency: 94ms. Protocol: JSON-RPC 2.0. [FETCH] Metadata hash (IPFS): 2354d0d3…63a5e005… [SCAN] Analyzing visibility: 2 public, 4 private methods. [MEM] Virtual memory mapped: 0x0000 -> 0xbd83. [VULN] Testing for ‘Reentrancy’ via external call trace. [SIM] Testing edge case: Zero-address transfer… [TRACE] Opcode dump: PUSH1 0x80 PUSH1 0x40 MSTORE… [VALID] Cross-checking with blacklist database… CLEAN. [DONE] System halt.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xaa33170348f06c15b68a655f302b667503fe4e1c 0xb39b76bedcbd54e57d15bb88e79668ae27fd292c 0x22dd7b06d6d2b5c24fb14f297ec83fb96cec99a3 0xb119bff557fda359dcc66267cf76698015a51775 0x72ba91b30f4a5d004dfcc1f9057f12c15e22221f 0xd976eb7c6a51f9565b24545ff095e7c60cb8fa25 0xeff9ad2d6aae8a41894c3718797c307013cfb7f9 0x0a5703ff96d94317775781d2f6d0a9aea39c10cc 0x13904eaa07e826cce9fabe36a6cba94724afc5f5 0x82690b436260ae5ddee20b52aa761e2250d7f67f 0x89bfaae1104c2590be9970ecc091f826c829a3f4 0x4c808860e0fd5a48874366c07e8eb3139979778a 0xc28ed0481d152beb49df5939f2d55514cdeedb60 0x36a8657340dbfcb0a03ae9dcdc57d946d00a0399 0x2da70f48abae28e8846f1c29c92b347c796a6392 0x70fdc756b814d2c4eab6cb597a0fd39b52fa4ebd 0x48f8e134952aa929f8673cab5149e4af1a80813c 0xb2ab35f0b3d5d21840a18ddffa465922af0784f0 0x87d8f90498124511b84a2f60799e892071b9ce78 0x4cd58edc1449cf54d70701141e251e7ac258d1f5
PROTOCOL VIOLATION: 0xc455c76157191679d56ace356a7d52d0c32a29c4 :: Unauthorized Access Risk via Debug Protocol

Deja una respuesta
