INTEGRITY COLLAPSE: 0x112ccb5107d334f0cb11c7114f85d21dc516ce0e :: Integrity Check Failed: Post-Deploy Debugging Still Active

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-9898C5661AA2
                
Infrastructure Scan
ADDRESS: 0x112ccb5107d334f0cb11c7114f85d21dc516ce0e
DEPLOYED: 2026-05-03 04:41:59
LAST_TX: 2026-05-03 05:14:11

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Legacy_Testing_Interface
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] Loading vulnerability database… 14,202 signatures active. [NET] Requesting storage slots for offset 0x00… [FETCH] Bytecode size: 5543 bytes. [SCAN] Analyzing visibility: 7 public, 3 private methods. [MEM] Snapshotting EVM state before execution… [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] Testing edge case: Zero-address transfer… [TRACE] Call sequence: 1029 -> e7d3 -> 9841. [VALID] Finalizing audit report for 0x112ccb5107d334f0cb11c7114f85d21dc516ce0e. [DONE] Memory buffer cleared. Session closed.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xd3211c7ac23f4661cbced612d8db5fb138e1bc6f 0x0813ee770aa80ecf123f434a24498580382ec12b 0x9ca1c3e7c86228f13e3ba10a10048359fbdd279d 0x0623ce0c158acb864518ad4748657e69995a6cd1 0xadc40a10a794968ffb51e834278d3ff865455a0d 0x301f784ef98ce82c636e96e842d187a9735bf238 0x21bd20af74aabaada9b25a2691b77d0200eb0c28 0x8b7495a136227dfdbe2c02fe03dc05c05bd5b268 0x294ad10a58e9749c727c47662b8377f34e82a766 0xbe87efca7aab697fdfff5e9a7b2c7277f0818e36 0x60088cf843ca3002fe92ae80289f502093c6df38 0x3ca5f6f0fb1638ae8393ed5294eb1da5e1abf16f 0xb92050f81fed4cbfa1e381fef1d2cdcc356bb8df 0x17cdefdb736b2f3d855fa8c6f256832d998f608a 0x6abf527ecefcf363e5feeb870e0e8f4603a274b2 0xf7173862a2fdbd66193d5220d89be37f70b2707f 0x676d0e62c31213d40e4a9ab3849132fc749fb26c 0xcca014bfd51268288ab81cfd095d5759543172c9 0x5e51374e01d3f81d9173d18ba3abcbd540c42064 0xce68cab6edc53acd11dd5df4fec47eedf9c6bf6f

INTEGRITY COLLAPSE: 0x112ccb5107d334f0cb11c7114f85d21dc516ce0e :: Integrity Check Failed: Post-Deploy Debugging Still Active

Deixe um comentário Cancelar resposta