RESIDUAL CODE RISK: Code Analysis 0x471bcb0286297c18dc61f7efd343fa487bb8196b: Residual Post-Deploy Debugging

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-39F65B228467
                
Infrastructure Scan
ADDRESS: 0x471bcb0286297c18dc61f7efd343fa487bb8196b
DEPLOYED: 2026-04-23 01:16:23
LAST_TX: 2026-04-29 13:58:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Dev_Maintenance_Leftover
VISIBILITY: OPEN_ADMIN_ENTRY_POINT

                                ◈ 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] Handshake with node 0x78a8367a successful. [FETCH] Loading bytecode into isolated sandbox… [SCAN] Mapping internal logic flow and branching. [MEM] Gas profile: Opcode ‘SSTORE’ cost analysis started. [VULN] Potential ‘Dos with Gas Limit’ in loops found. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Bytecode segment 0x67 analysed. [VALID] Data integrity: SHA256 verified. [DONE] Report exported to IPFS: 6c98de14…aedf75f3.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x61d6c1936c379cfed021103dd7d631e93f643e07 0xc9aad1057aa21d0f023b962aa660335255a26b3d 0xec0611d2dbb92843b944978c2e7249bd7ff1b7dd 0xcc374b9971a0d5f92cfd1c5fa696a930cb3a9d94 0x790d639b96fd3421b540b05ceb0727229ec54160 0x8909dcaa8b12ab135f46c47d5fbabec943dd7e89 0x288a7864aee723e6ae10e7828b56d815c472a175 0x94d5b0182ee4a8bcb188b4b398ce03ba2c1f1c90 0x04b136b35d59f180a88b5edd8c224f4ce481e7e3 0xb1caa23776a7c05a8701c952ac80ec891023a9bb 0x65fbda4711f5a4aad6dae92baf9f3a20f5aff111 0xbd3af3aa9d530925cb425af7ddccc730fd7218e0 0xe8ae82c21a762baff24690d5699c1da43e62f9c0 0x361d760a6d68f7626120555b558741134853fbec 0x04b63c65428d99d44770197d7cef8635830b7b1b 0x1910c4cbc93f432a275168193dbd562ec4bab655 0x1d4f4e70ff3dfa1c2b9e551e5ab8e15204831767 0xa3d4f5bac9894cf067ceb7ddab86231a7fcc6d42 0x97fb4873238bb13ee44dae12a8a8547d49b2fe1b 0xbf634dca5c5644438fe930c2282787acdccbface
Posted in Genel
RESIDUAL CODE RISK: Code Analysis 0x471bcb0286297c18dc61f7efd343fa487bb8196b: Residual Post-Deploy Debugging

Write a comment Cancel Reply
