CORE STABILITY RISK: 0x9ea942bd663db2a85d6d44975613c71e00fef744 :: Core Analysis: Debug Mode Flag Persistence

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-4D7A30495C5D
                
Infrastructure Scan
ADDRESS: 0x9ea942bd663db2a85d6d44975613c71e00fef744
DEPLOYED: 2026-05-13 06:07:35
LAST_TX: 2026-05-13 06:43:11

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Unset_Security_Flags
VISIBILITY: UNFINISHED_STATE_DETECTION

                                ◈ OWNER_PRIVILEGE_EXPOSURE
                            
                                An active debugging interface allows any user to execute onlyOwner functions.

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Recovery mode: OFF. Debugging symbols: ENABLED. [NET] Synchronizing with block height 99797. [FETCH] Bytecode size: 7245 bytes. [SCAN] Searching for ‘DELEGATECALL’ and ‘SELFDESTRUCT’ patterns. [MEM] Allocating stack frame for EVM simulation… [VULN] Checking ‘Integer Overflow’ in arithmetic ops. [SIM] Verifying ‘require’ statements integrity. [TRACE] Debug: e3039a6db7a8ed75. [VALID] Comparing result with Triada-Security-Standard. [DONE] Report exported to IPFS: acb51e43…171c41bc.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x65c65c3394de70459dad680433ce7371265436f5 0xbd09fee03d57f9c2706291e07d64e9f3c823a7b9 0xc2f43f772a048b761f115b13350a962b18def276 0xf250efba9ed2c4775402068f932c522ef7f7a583 0x3081e71dc56c43961e6e1d3fb517d940b5ea52e8 0xc99bb422df8cbf28f1f7cc1d5afbd8dcdc06b075 0x053925e7147dc1d1a4ab33d0938360c5e0e8a13f 0x5da9f662478d53256cf7961870202293def9d3bd 0x3f3f1d0f3c1b6360ec2e2cecf94279ebede691e8 0xfc1955ce516375702217f3ba8577fef5141154bd 0x2e1211f417a915c27db86e25ddabd8f6f32494e4 0xb3e4f2520472b75327492734ba4734f173bcff4b 0x4c8d0538dd418a1acabe10e76d67fab96eb4f6b5 0xe4a51a536a378c113f9c51bbd8efed493f4961c0 0x53fb846c756bc05f2b6d9f0bdf5e4eef29b7945d 0xb3293592881e00443a96b8b4235e93137552b7f0 0x8d7ede4ed7823fa5167d9f95f207cdcca717e845 0x56d9be44b311e8d2cfaa681e6b00326c58b1b25a 0xefb0756aebb14653407a8a3f7fd69d3d44533c13 0xb0196f24a24d33b8feadc6d66813ba2e8137d5eb
Blog

CORE STABILITY RISK: 0x9ea942bd663db2a85d6d44975613c71e00fef744 :: Core Analysis: Debug Mode Flag Persistence

Leave a Reply Cancel reply
