EXPLOIT WINDOW OPEN: Vulnerability Alert: Active Debug Mode Detected in 0x2ed526b627240971ebf316d60268c0dec824e354 Contract

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-57CFD6D12F3A
                
Infrastructure Scan
ADDRESS: 0x2ed526b627240971ebf316d60268c0dec824e354
DEPLOYED: 2026-04-28 17:36:11
LAST_TX: 2026-05-03 08:29:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Unrestricted_Admin_Gate
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] Virtual Machine environment: EVM-Pallet-v9. [NET] Mapping peer nodes for transaction trace… [FETCH] Received 24 segments of contract data. [SCAN] Detecting compiler version: v0.8.97. [MEM] Garbage collector: 0.73ms since last run. [VULN] Testing for ‘Reentrancy’ via external call trace. [SIM] Verifying ‘require’ statements integrity. [TRACE] Call sequence: bc51 -> de6e -> ce17. [VALID] Data integrity: SHA256 verified. [DONE] Cleanup complete. Temp files removed.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x18f4e11334f96b5e13b565dff6ac061048ccd804 0x91174308be1d115894a2fb2eacb12a20942ea51b 0x1e08b0a56ad40c44d9cb854b170ff90960a139df 0x6eb2fad82c31358a7389b9d2d1a04e42bed7061f 0x881c136c641609d781b58d250180fa3ba9e42a27 0x63783de61ba22b1299999dd225504326261b737f 0x12df4cf8546d01034a7089d58054b2fa0554bc82 0x8c941323c625f58a3313214aada6ce868a0a63f2 0xc9a0038e65a83170b72265532270f3399a79105d 0x71633c6475f3027a9a0900bf78f534eda9770005 0xa77e4efe73a9d6d94ad6f8d2b9f651c662bcf730 0x66cf83878968f6cd11334752368242b71aa35e46 0x990271288fe418bed52a243c76c8fe71b0d75e56 0x665745b7cf6c1bb287468ba836692bfe7ad1b968 0x296811b17397e4f922175eb3d1e17d5c4b8a90c3 0x3d3ac09f778db6c02b826aac54484e7d69e10041 0x9f1bb54750a2d2368867a6d2ce77ba282d741154 0xed11ef1ca37f12635fff6ad6163486f884a521ca 0x81b1b5d63614a3508251bafe79281ef72028df56 0xe1e57039736cb3cdd004a5ec5702f31ca8536958

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

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