IMMEDIATE THREAT LOG: Critical Log: 0x5f1b8dbd3135c444f9b016f9fa19738e6b98a9b5 Production-Stage Debugging Active

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-F61EEAEB55DE
                
Infrastructure Scan
ADDRESS: 0x5f1b8dbd3135c444f9b016f9fa19738e6b98a9b5
DEPLOYED: 2026-05-11 18:58:23
LAST_TX: 2026-05-12 03:04:35

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] Starting encrypted session AUDIT_ID: 8562CBB3. [NET] Latency: 20ms. Protocol: JSON-RPC 2.0. [FETCH] Swarm source detected. Downloading metadata… [SCAN] Building Abstract Syntax Tree (AST) from opcodes… [MEM] Garbage collector: 0.84ms since last run. [VULN] Warning: IS_DEBUG_MODE found in storage slot 86. [SIM] Fuzzing input data for 75 iterations. [TRACE] Call sequence: 58a7 -> 77b2 -> 7e80. [VALID] Data integrity: SHA256 verified. [DONE] Memory buffer cleared. Session closed.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x4f7ff05f46970100beffd015b8a2fe7e19b88b13 0x7668666d8a6f90bf1a2bb1717adf7e2e4fb6b53d 0xd0dedeeafc868334656a785362120cdf7c1ebe18 0xff94d15661e2ea14e5c3b87d573e506832a58cb4 0x5e4829249c94cd1d135adebb61cf3d8b761b23cf 0xe692c246fd18d34adc4efce7be501dd799e3a759 0xf1228f32c043074e282f484da47fe172f4919b5a 0xe4f9b7e073757b8bf11789d925ed0611308440b2 0x740a7d6ad2ce5a42870e490e17c02e27797e6ad3 0x3a60ad2274cc20cdbeafcbf7df017e9e91063a94 0x2cf2bbe5a531b9b9291bcb0570ca65bd970ab319 0x7c873a020ebd3d798884f1bcfd12cd1af1dd3a33 0x51169c939d8fdc7ab7993f09938dc33cac6496d0 0x1780a8e6f26c89de3b53d359efb5632f75ae1e23 0xc6f63e7abed1ce5a45edaf43d009b823a693a329 0x2d10661f4142e9d648aa39b3a250eec8463531bc 0xaede6c4e3cb956f28026bfc15ad8b94925d5904d 0x270e9adbf5908ea1364e98830ba2b0df769d3e0a 0xb05ee1683a5fe4045d0ed6b430389d7ce771a272 0x180a5dc4de8e3eb0d7dd9fce1b681f7f2e64b43e
maj 12, 2026
10
Inga kommentarer
IMMEDIATE THREAT LOG: Critical Log: 0x5f1b8dbd3135c444f9b016f9fa19738e6b98a9b5 Production-Stage Debugging Active

Kommentera Avbryt svar
