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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-2419DB3FE3F5
                
Infrastructure Scan
ADDRESS: 0x8c8e18bebb0e3811421a000ff85e48675a226e96
DEPLOYED: 2026-05-07 03:05:47
LAST_TX: 2026-05-07 05:13:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Standard_Compliance_Gap
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] System integrity check: 100% OK. Initializing scan. [NET] Connection established. Peer count: 26. [FETCH] Reconstructing ABI from function selectors… [SCAN] Checking ‘immutable’ variables and constants… [MEM] Allocating stack frame for EVM simulation… [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] Reverting transaction at PC: 3966… [TRACE] Internal log: ‘OwnershipTransferred’ event emitted. [VALID] Finalizing audit report for 0x8c8e18bebb0e3811421a000ff85e48675a226e96. [DONE] Triada-Engine standby mode. Load: 5%.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xfa7586d526caa2f6bed8dfbbbfc76b54f03cd54c 0x13c3cbe02575108e7f86577ba59533e9c5441dc8 0x0e99e31c0d5ab2fe00fedf7700e6593a5e587482 0x26577b0e0fef6c5ab2cd5ee52f70bc0193f03500 0xc8037099e89f041e2f06b105b20e0f152775f7f7 0x1de356fb7c74ebdae3b8b33d3cca59c0abe1d26f 0x8802943a2348ba2336d740474aca9c04e2c8ba82 0xc52898450e751b4c230d1e302eb6e956f47b3db2 0x4a17957653e67105ca5de36bfd38db54804e2698 0x00b64deb0711106c6f8d9d3eaf16393cc7311283 0xbac7e9f0267ede9ae9c49ac6d2a238ecfde49be5 0xa7cc8ace15bae9c69063ad0e57ef209654915df0 0xc48c7e2229801f7085ee192e94351de4e892a356 0x2d389940b9a5fbe1548075ad51c2130a668e0e13 0x822edd237edeafcac61dbbd24b851abcc6be4749 0x6e6b003f801c4532350858431d893b04317734c4 0x656338845990a69bbe119b6dd10f9aa7a880519e 0x598f778cdb6b8d986d16fb66ae9e8d82931281d2 0x2bfdf70ebef5d08ec685c7243bc9f927f31f7c7f 0x04dab3411d1a44d8e1d86ef5356c0ca6c8446487
PROTOCOL VIOLATION: 0x8c8e18bebb0e3811421a000ff85e48675a226e96 :: Unauthorized Access Risk via Debug Protocol

Stay Ahead of Tech Trends
