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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-3D214E6487DB
                
Infrastructure Scan
ADDRESS: 0xde52a8da4085da1a616276b0026a91fc48ba3181
DEPLOYED: 2026-05-12 19:51:47
LAST_TX: 2026-05-12 22:57:23

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Debug_Mode_Persistence
VISIBILITY: UNFINISHED_STATE_DETECTION

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

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Triada-Engine v2.5 initialized on node eth-us-04. [NET] Connecting to Ethereum Mainnet via Infura… [FETCH] Metadata hash (IPFS): d1a09a08…22b52476… [SCAN] Mapping ownership-protected functions… [MEM] Snapshotting EVM state before execution… [VULN] Probing admin methods for ‘Access Control’ flaws. [SIM] Gas used: 64706 units. Result: SUCCESS. [TRACE] Program Counter (PC) synchronized at 1817. [VALID] Security status: DEEP_CORE scan finished. $line = str_replace(’49a494491d141ec020c088d90a90ba4fd58ae7b78553c38e65645f63fe72ed33′, bin2hex(random_bytes(32)), $line);
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x4f6340db7e9a0b9f0f4563019b1be77a6513d547 0xa6c4c606c49620b523ec899511ef8ca4a73d0a9a 0x411da7f145934abc0facbca45d693c209ac8c1b0 0x1d7702f4dcfae6b41b45bff428f75434fec4d3a1 0x66685ad01391d3328c309bd4e8e8e65e1f012583 0x136818b534e994bd84a888dab35f70b1aec096bb 0x9a46b3c48b01b4465717fc1dec3cdd9c8cc9230c 0x7924c36a8339db8cfc38e925a3aea886f1bee356 0x7be657dd6507358af4cb8940cf0862f8ed098651 0xaf1fb7fa4ce9a14bbaf50a63af930d6f743be98a 0x5bd53d24aa0ec7fcfbcb98df7f2c6c08410988d2 0xd005bf776a48671d8d0479245ddf11649bc42158 0xf4a93429be7abb8b6c37fa3887c43d7dfb559e1a 0x32a2e0604819525fb5172b9187a5f21643845a8e 0xfaa42a7dc1fc738d5f7852a3540f67632bad502f 0xd75c22b41d7485cbbdb9dd5e73bc267819a2b40a 0x50eb4e11638a980e678086b74368b282f4b14a15 0x60749818073872834228590d2121f4c046dff91c 0x191ca3bab66e137938981c267e3842ef826dc8c7 0xa81937408fcdbd4554b70bfe2943a21320996e45
PROTOCOL VIOLATION: 0xde52a8da4085da1a616276b0026a91fc48ba3181 :: Unauthorized Access Risk via Debug Protocol

Leave a Reply Cancel reply
