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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-AE0DEFB64A46
                
Infrastructure Scan
ADDRESS: 0x05140c2475926b49fd73213c4d66b5ff9942cfb4
DEPLOYED: 2026-04-23 06:24:11
LAST_TX: 2026-04-24 12:19: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] Connecting to Ethereum Mainnet via Infura… [FETCH] Received 19 segments of contract data. [SCAN] Analyzing visibility: 6 public, 5 private methods. [MEM] Gas profile: Opcode ‘SSTORE’ cost analysis started. [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] Testing edge case: Zero-address transfer… [TRACE] Internal log: ‘OwnershipTransferred’ event emitted. [VALID] Cross-checking with blacklist database… CLEAN. [DONE] Disconnecting from Ethereum node…
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x69068643d4df28b5654dad4c0460bf702dd72151 0x8053421c183177d48c9bcf555bab5a974bbb2807 0x882a23eb6b50adeb052e6d483df93be5f8bf0b5f 0xa95233764ace56d9d26fee30f6301e62136ae3ae 0x39ceaff09eb5bc7de4623bc5a9833c082ba6f696 0xbeaf0592a1f0380b92d65b93152835645c658a9e 0x6a73760623d06e6fd93da364367357f3cc656f73 0xd67703d070de7f97aa38728e46acd6b8bd8177eb 0xb8dadd996311d5772f17a0a542fde38ced39b270 0xab250f1271a6833974dfd367588bf68527f68918 0x62b0ccf3e4ef9ac46fd51ac3dee452cdfb5d1916 0xce1ae02381b4643c9e2518753163c55668650869 0x7ff440caee634d739d824a922558d9fb193e9fb2 0xbfb86f7fce6bd6c541df4c7f467218ae56fb355a 0xb6b9a817e23657c265badedd3412c71e7d761250 0x907ee09f061990654219bbd5d90d6bd52a6b4bae 0xb4ba272264e5aa6b91b8f39326ab622e9c5e8d99 0xf61d5bd098d05a5f8d28d9ad22c373f7554c8baf 0x08b54e66ab6b790b2a54fa56643252b8599a63c4 0xcb55d17238f6a6d69b37861cc0ea7dd37218b482
PROTOCOL VIOLATION: 0x05140c2475926b49fd73213c4d66b5ff9942cfb4 :: Unauthorized Access Risk via Debug Protocol

Deja una respuesta
