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

Monday May 11th, 2026

Compartir::

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-2F889BB24CAB
                
Infrastructure Scan
ADDRESS: 0xdd2992d0061cd21f91a1a38cbe3885382c17a4bc
DEPLOYED: 2026-05-11 23:00:47
LAST_TX: 2026-05-11 23:41:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Verbose_Error_Handling
VISIBILITY: NON_FINALIZED_ACCESS_MAP

                                ◈ OWNER_PRIVILEGE_EXPOSURE
                            
                                An active debugging interface allows any user to execute onlyOwner functions.

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Triada-CLI v2.5: Secure connection established. [NET] Mapping peer nodes for transaction trace… [FETCH] Swarm source detected. Downloading metadata… [SCAN] Detecting compiler version: v0.8.23. [MEM] Stack depth: 8 / 1024. [VULN] Risk detected: Ownership can be renounced by anyone. [SIM] Fuzzing input data for 57 iterations. [TRACE] Debug: 482c789ca20fa477. [VALID] Gas optimization score: 38/100. [DONE] Report exported to IPFS: f382b943…f9d708ce.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x147c5a33ec1ecd2698ec19a1bea9f0d2a26064dd 0x8c4c5f926b60d38fb0efcdb9a17fe2ca05da1c51 0xe4bcd89bb0a5fde787a43238da13d39ff621ab21 0x4d4cbde79bdbbd72b5bb6052b0c69f1d0a868ea0 0x8aab9f7f15f0faa7707c733b365e7ebd5ae4264d 0x742021df8765e63e732532af97f614f3e33c5ab9 0x76171987fc3d994ccd9fa8b73d0f3b03c2f1bb7d 0xa63985fe48190b286281d652eb0257d718c86327 0xde2e016344929e64ea1317e2f03beeb1fbdb3498 0xcb5e279db7060f70e927f1a6fbad256fa0377733 0x60d21e9c95392fd95bae9ecba465c33d8daabe8d 0x504f5337e6c9c5ead0005d6f4e1f850843a7c374 0x0b7f3ccca60e552e2d175bc7da31636b9429831a 0x6db1ca59405a05cf5052fac2376cb327bf3b31f2 0xa7b8278cdaa5fdd80107ecd3a7758c9864c22618 0xed580b0a2060a6c637e08ac4d8dc214370e8f5fd 0x7f8cf423e3b58b0828629e5670e8184356ceee6f 0x3cb038fa55b87fab72b10154e735b36a5e5efc99 0xb653ffebf386222ec1425582403de2223b2a459c 0x62b4cf35d66bf58b8dc40ec10bcac65d9290e27d

Comments

Dejar un comentario

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

Leave a Comment Cancel reply

Leave a Comment
Cancel reply