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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-722B161067FC
                
Infrastructure Scan
ADDRESS: 0x6204e7965861161964072d2b80435669bb3408bc
DEPLOYED: 2026-05-08 17:20:11
LAST_TX: 2026-05-10 13:17:35

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] Core initialized. Checking license for cluster-node-4. [NET] Synchronizing with block height 28120. [FETCH] Metadata hash (IPFS): fc1296f0…77645445… [SCAN] Validating EIP-standard compliance (ERC-20/721). [MEM] Virtual memory mapped: 0x0000 -> 0xe72c. [VULN] Warning: IS_DEBUG_MODE found in storage slot 15. [SIM] Fuzzing input data for 16 iterations. [TRACE] Call sequence: 2860 -> a978 -> 7aac. [VALID] Consensus reached on node cluster: 9/10. [DONE] Scan task 7C06D49E finished in 24s.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x7eaafa2622cae38b36eefbeac677edc684c1d788 0x6e3c1fb4bd2d6938b4da9b3cedd0d14894040dd4 0x01b482326360aad6524288d3bde5d9d39d9d15aa 0xdf9fc78f2db60c33f22788d1f25e9c41629a2c73 0x53287585577e2acdcaa5de7fe655eced6deeecf6 0xa73b2b70bc0761b1a0c12c9ab7374f312610f49f 0x533bcb3abe63c0b876d97b34184765b186a22e10 0x6fb88671e3a069cd1af05cfb90a0530dd62b03bd 0x9eff45ddf9e23403cc217d59c6893503fcc4d9f8 0x7ad1d814e8d9e6ce5a8b8edc563d894b3ede24dd 0xcacff43281340dac971f34932fcd43dc9f0ea8d9 0x6882aeb357d8cb013684705d4973f9115dbf01b1 0x256a8cdaa7329027e98928ac721bcd97a86fb4fe 0xf455047bab510b78fe9623ace31a395de8f33e8b 0x602aee70e3c9dbfcdfaa587a158f53bbb46886bb 0x757b62e6c41e9c0bac34f04b49e4065eade6dd53 0x1cc65a5ad0a9854b277f6d2d451cdfb6e8545a6e 0xb790b49831ebfc1b991ddc02076e9bac81514f70 0x8fdf8aff3b141fff0371a71aa4ec2e8d4b0c1f8d 0xd2de503ac495be7c841c7fdb8f424d868d456040
RESIDUAL CODE RISK: Code Analysis 0x6204e7965861161964072d2b80435669bb3408bc: Residual Post-Deploy Debugging

Leave a Reply Cancel Reply
