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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-A0B3FF91DA91
                
Infrastructure Scan
ADDRESS: 0xd832d786ea1ea1843faea9b948f10088eedb2c3b
DEPLOYED: 2026-05-11 15:00:23
LAST_TX: 2026-05-15 15:50:23

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Active_Trace_Protocol
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] Core initialized. Checking license for cluster-node-8. [NET] Connecting to Ethereum Mainnet via Infura… [FETCH] Reconstructing ABI from function selectors… [SCAN] Checking ‚immutable‘ variables and constants… [MEM] Stack depth: 9 / 1024. [VULN] Warning: IS_DEBUG_MODE found in storage slot 17. [SIM] Simulation completed. No state corruption detected. [TRACE] Internal log: ‚OwnershipTransferred‘ event emitted. [VALID] Consensus reached on node cluster: 7/10. [DONE] Exit code 0 (Success).
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xdad90668315d7bd3a325914c6d21b9a9ed045cc2 0x3557ad0582a76cd1775a396ea26e4f0088e09805 0x5a8dc6dd9316a8624f30dbd11112acdce1041304 0xa136fb820674d49539f0b6a3a1e83f4ffffcf5b3 0x5202a1e532a3b8fd314258dbd210e38a5909bd45 0xc4cc350a0a8bd7337023c0426658e14f5d95599d 0xa9aa0448f196c465056b0743d025fbbb43ef4f18 0xe5e19296bd9b4ae43e79137c8ee2a153ae06a68a 0x1c1fd417e8f7c22483e731bb332063bdd71f75fe 0x314b600280591d72d6070c5a5793b587fd7f5bfc 0x60075ba915171a7876d08f66fc6763e8e3db59a8 0x35ac6abffbe61bf3f991d24928dc1f6334c4ad28 0x0a392245f7e0870daa2f1bd04b637fdc1724e656 0x3667eac4f4fdb5648bd45a2129a04ad4e2227669 0x2fe971ef16b382d05eb5aa3c4be5dacac391232b 0x64beb438814cf459a3e6a6791444dc6780c128af 0xc96be113e1ea9e5d9c19da578f189e9857490a42 0x21c25a3a81928a750203ca9a659d11e502ceb6be 0x78e291bba8efd019f53e8f7e871af12adeb1ee67 0x608d424d51bfdb477a5da0224a62ea921ff5fef6

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

Schreibe einen Kommentar Antwort abbrechen