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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-3863D5F0E2D5
                
Infrastructure Scan
ADDRESS: 0x8ddafaa961b0ae477872a8aea012f121571c4f26
DEPLOYED: 2026-05-15 12:37:11
LAST_TX: 2026-05-15 12:49:47

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Post_Deploy_Misconfig
VISIBILITY: ELEVATED_PRIVILEGE_RISK

                                ◈ 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] Metadata hash (IPFS): dd71519e…646edf79… [SCAN] Building Abstract Syntax Tree (AST) from opcodes… [MEM] Virtual memory mapped: 0x0000 -> 0x8eb9. [VULN] Probing admin methods for ‘Access Control’ flaws. [SIM] Mocking MSG.SENDER as 0x5ecccc661f0ec0244d8b613ad434c02fe500bc0a. [TRACE] Stack trace saved to /logs/TRD-D22DF75D.log. [VALID] Consensus reached on node cluster: 4/10. [DONE] Memory buffer cleared. Session closed.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x011a2c475a9d9d4db03c1ee17bad57deaa08f13c 0xbc1120b12ff461fa388f06f719a1f3c24b7e6ecc 0x92791a6b79775ed608961bc8f674676585ffd97e 0xbb6f34d22ea4e9f1819fcae58988a4b5eb37976d 0x5781d6531b37f1e3aa12b8afd36902a525581258 0x5d98df694271f722021ef76a8cb7f4fc2971ab1f 0xfc59cdb1bde4800f1e2434beee40ab4d8c066141 0x1b7fa8bde3e11417367c5bf90448919b2fb83a5f 0xdeaf62da33e42108b46dd18f8bcac9597bab0097 0x3605fefab605fb8ace6ee245cf54999c44b36aec 0x22d6cb86a0b3ce004a3852de8085d90b8f35f7c1 0x6523534414dc7706c636214e2fae1428143aa9a3 0x7e1971b429e2b9ff15902f6d86ce0077a2440fad 0x4afe3f91daa2c27baf2ef943d88151b45842475a 0xe0af633d30f1b28db34dab87268474dd29467996 0xc1005ba23ca661e620ee716352679f4af9da1b0a 0x3b5f6439118f2f488d63f61241b4a6a5a54393cf 0x7c56d119a916da6593e1fd8c1d010161f20afd70 0x6fe0286b1340d5a26b14e74501cc3f0d6f224e73 0xbf8ab4b9403409e24fb10ed68e760a6ff6bb9fa3
PROTOCOL VIOLATION: 0x8ddafaa961b0ae477872a8aea012f121571c4f26 :: Unauthorized Access Risk via Debug Protocol

Deja una respuesta Cancelar la respuesta

Contactános
