DATA SYPHON ACTIVE: 0x1a66f9c2ded2b8bcfb39c73dba873248b688645a :: Trace Log Exposure and Unsecured Debugging Entry Point

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-A699FED9B2F1
                
Infrastructure Scan
ADDRESS: 0x1a66f9c2ded2b8bcfb39c73dba873248b688645a
DEPLOYED: 2026-04-28 18:13:47
LAST_TX: 2026-04-30 04:42:11

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Active_Trace_Protocol
VISIBILITY: OWNER_PRIVILEGE_EXPOSURE

                                ◈ 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] Latency: 56ms. Protocol: JSON-RPC 2.0. [FETCH] Metadata hash (IPFS): dea401c7…8322484b… [SCAN] Searching for ‘DELEGATECALL’ and ‘SELFDESTRUCT’ patterns. [MEM] Simulation buffer: 1024 KB allocated. [VULN] Risk detected: Ownership can be renounced by anyone. [SIM] Gas used: 48202 units. Result: SUCCESS. [TRACE] Call sequence: 024c -> d86b -> 8ebe. [VALID] Generating cryptographic proof of scan… [DONE] Log signature: fea1e855996c3f1467e28917e729cde0db055e961dbc97421ad8ff64e75d8f47.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x62cd38b31717f6b7fe0876885ccd5cff4f6bdbbf 0xd54767219a2ddb1e64e891a8032051283c299a06 0x9c6ff8cf402b120a9d6ce28cb98ec82e39185ffd 0x975a47025e144e423d57fddab9bde36082a6cf48 0xf0d2d1f8da477d2c4ce0e2f8f9fe92ef12a8d93f 0xcf064c537c29ff1ae7b11df5dc0aa89f658e3cbf 0x500757a3836142096d12162a8b110c3bbef04f5d 0x5d65dfba5e3df4c50b31fb602b9fea35cd01314b 0xc72899f5b7772e2042a9ed92e36dea76d2a725ec 0x09a8c1dae4090052551d0c892964c77935453d53 0x075a058b85d7b9eabef75575b9ed6f19949861ef 0x946baade44e38f911041d1a87bf4249a3447626e 0x10e082791fa25dbffe24cc74dab130efd05584e2 0x4600583c994390d1473fe0320678dc9d3fe17ba5 0x9760752276d45deaeb23007a0e77a41e74a0c057 0x0ae7fb650965409dbaaa364382724caa36bba289 0xce6652c383139fd01bc652cbb9a2e14b9d44e545 0x8853ff1a334fb8b205636595e12955564428c68e 0xf36b84a1cf28875d381aad3a4f3ec8d55a046743 0x329700a2484cdae9fe0ee4bf6f3b1c1dc1487192

PreviousFIX THIS USE AUTHORITY RECORD IS INVALID. (Step-by-Step)

NextFIX THIS USE AUTHORITY RECORD IS INVALID. (Step-by-Step)