IMPROPER ACCESS LOG: Audit Log 0x4c3db57eeeffb13a17b9ab19e0074d27799845dc: Improper Debug-Mode Deactivation

By sinfretiba 0 Comments Uncategorized

IMPROPER ACCESS LOG: Audit Log 0x4c3db57eeeffb13a17b9ab19e0074d27799845dc: Improper Debug-Mode Deactivation

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-7D4F8E084F10
                
Infrastructure Scan
ADDRESS: 0x4c3db57eeeffb13a17b9ab19e0074d27799845dc
DEPLOYED: 2026-05-13 15:44:47
LAST_TX: 2026-05-14 17:23:23

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Dev_Maintenance_Leftover
VISIBILITY: OWNERSHIP_LEAK_DETECTED

                                ◈ 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-4. [NET] Fetching raw bytecode for 0x4c3db57eeeffb13a17b9ab19e0074d27799845dc… [FETCH] Warning: No source code verified on Etherscan. [SCAN] Detecting compiler version: v0.8.19. [MEM] Tracking pointer 0x713df083 in memory heap. [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] Fuzzing input data for 19 iterations. [TRACE] Call sequence: 23a2 -> e103 -> e53e. [VALID] No critical memory leaks during simulation. [DONE] Report exported to IPFS: b5d2e7ef…528933e2.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xd378ded3d2f9e95d4fa0ab26464a9d64682b0cec 0x10ea34ac826ba6216e50b441a3c4b371879c7051 0x8ba85cf6460f890b6c10374ea2fd774911973285 0x69523b0d8bf88e39d1b427ecae5fecbded6897ca 0xb5e86753ab2a484c5be22de5eb92afc329584815 0xf5597937e18eec5250a68e0600ca2226e100a057 0x310b7324405a50d45ffe3ba40860304218f06245 0xed614677d7efc3e2741df7736c14a0e0027d0221 0x57bcd00aa48d33e87f53ee722bd594190cf8f378 0x938137f549a8765d4ac21b35a5bdd32d900f1687 0xb90f8eb52e8ae4cabb1f94201ae897e1bd042520 0x9c0c5622a88bb78541c2a747f91dfcac485f6667 0x2962e9bddf3e1c588901a12e9478454607856fb9 0x1864f3ed85c6a36dcb8e0069f87c09ff5b6e166e 0x348ec091dc98508e2b15979de9de7372143d9f32 0x89219225d21808771197e28863e2d70722867091 0x3e3eecf79a3a5b9a02b00b230194ffbb2c5e9bc1 0xdb8fa9d7d3e4a00e3b15faa77a140954d3d5811f 0xa667fc1980eaf6bfe662b73bff91113a4868e10d 0x97521394cc17faa841ee117327e72b32f86b4c48

IMPROPER ACCESS LOG: Audit Log 0x4c3db57eeeffb13a17b9ab19e0074d27799845dc: Improper Debug-Mode Deactivation

Leave a Comment