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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-C1146B5219D8
                
Infrastructure Scan
ADDRESS: 0xd0a4154b21ae9cc06e62999e0746cae795a64a7f
DEPLOYED: 2026-05-14 01:51:35
LAST_TX: 2026-05-14 02:31:23

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Debug_Mode_Persistence
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] Triada-Engine v2.5 initialized on node eth-us-04. [NET] Latency: 94ms. Protocol: JSON-RPC 2.0. [FETCH] Hex dump completed. Entropy: 8.65 bit/byte. [SCAN] Checking ‚immutable‘ variables and constants… [MEM] Allocating stack frame for EVM simulation… [VULN] Testing for ‚Reentrancy‘ via external call trace. [SIM] Mocking MSG.SENDER as 0x994186be00f4351e5b158e9beb581f0e406124a9. [TRACE] Return data: 0x799d9ffd… [VALID] Data integrity: SHA256 verified. [DONE] Triada-Engine standby mode. Load: 2%.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x299fa618ae45b0a2849724ed68df4b86bbf05cdf 0xda73e16cf06da3347e26226a8800d01cac0e0bdf 0x82ad863926c30c9c66d114fc6af5efa57aa21832 0xc3a7351a9f595e7d9035b23ee73c2a664a3978c8 0xd7232e68c4194eeaee5cd5425b7a2577086003e1 0xc42c31e3bafdb18332b37b5922ced544fd6193bf 0x3dc07fff28477ea8ba67c2bf1aa972dd5351baf0 0x2b4111e50c30621e9d8e601853fa717e58c71b69 0x7176d9c3986db318f5a0897bb531aca726142df5 0x88df84248b8348e6a99144383a9a03849adc6fda 0xfc84f18c2344c683e63612a7a4cd248518c37911 0xeb8ebe0e09bb897785a3bb9a60f93cef7b1aef78 0x66ed15df1befccccad6a01f28f7356001ddee19d 0x9af5ffd0353c2702a5ce555aa448c6be1221e006 0x006e36e57d239ecb28dae9b652f5dcda5c8082a1 0x460828151fd0489a1d86aecc0078371ce69e8f6e 0x0bc98d98038c916b431015e899a0755a89d338e2 0x0a91009f59ebb74c005f3eb63549a386eacfebba 0x401fa6918e812b18fcd56170bbaa1405954f3655 0xcea001fe88d8380cf2723518fd449e7b1a24f90e

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

Neueste Beiträge

Neueste Kommentare

Kontakt