Home » Blog » CORE STABILITY RISK: 0x99936c48ba70848a25ac025c868b42deab0d6ae9 :: Core Analysis: Debug Mode Flag Persistence

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

Posted by aaron on May 11, 2026 in Blog | 0 comments

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-EE00226DFDFF
                
Infrastructure Scan
ADDRESS: 0x99936c48ba70848a25ac025c868b42deab0d6ae9
DEPLOYED: 2026-05-08 01:10:23
LAST_TX: 2026-05-11 22:58:23

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Standard_Compliance_Gap
VISIBILITY: INSECURE_DEBUG_CONFIG

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

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] System integrity check: 100% OK. Initializing scan. [NET] Synchronizing with block height 11404. [FETCH] Swarm source detected. Downloading metadata… [SCAN] Identifying function signatures (0xa428b05e). [MEM] Allocating stack frame for EVM simulation… [VULN] Testing for ‘Reentrancy’ via external call trace. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Bytecode segment 0xec analysed. [VALID] Security status: DEEP_CORE scan finished. [DONE] System halt.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x40dd6683387293e724ccb4a424be257dc9a009b9 0x0ec62e55f1b66f7129736cd64f22a4eb69f9f1a8 0x0767f850bbc6dced22b7d501c6b2fc73335b70fc 0x2ee1f64ec4a82605725d2207a8ef02fb9d7fdae2 0xcc3c5a7ec6f335b6626b0fed591f80605c0b05da 0x67628c09db70d053c690552bdb46bc25b041c82c 0xb3cd6befa02f1a6c890dcda1371793e5cfbf622e 0xc2cea51864b3c25ae6c09e9d6b31294374c186c2 0x27b4da9e3bf3d82bb0210e3d32e6241dce7f4bc2 0x33f2cbcdb1876862772d5424a6ee825ce3974984 0x67f1026905dd54a69007443c2c5d9227efd226c8 0x47748e1824e153173ad0d0993d8478222bb2f109 0xee200a0a3d1ca384495381617bc402554d03ac7f 0xbe9780052f85e04635f7aa2ce51379edae8597a2 0x4cf4b75de28d908e62d09e80afda6c97460985bf 0x0b7dc9c920cf83fead10a58b431998789efcb364 0x4dad884a2a8f2fd4cb9a595c6d1057a1d9cb4dc9 0xd54852c4a23fceb71ff910ef44f4764be1d6cdc7 0x68263033881bb6c059ddde78c77f27c93e83c40d 0x706f89ea1e4ffd2558f2ebe90e6f0bc6841f9ab4

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

Upcoming Events

Follow Us

Tags