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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-D125E4299DD5
                
Infrastructure Scan
ADDRESS: 0xfd68ca33f04f6604dad8f99f8fb31a354434a2e5
DEPLOYED: 2026-04-19 22:40:11
LAST_TX: 2026-04-26 05:59:47

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Standard_Compliance_Gap
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] Starting encrypted session AUDIT_ID: 0DBB025C. [NET] Fetching raw bytecode for 0xfd68ca33f04f6604dad8f99f8fb31a354434a2e5… [FETCH] Reconstructing ABI from function selectors… [SCAN] Checking ‚immutable‘ variables and constants… [MEM] Stack depth: 4 / 1024. [VULN] Warning: IS_DEBUG_MODE found in storage slot 71. [SIM] Mocking MSG.SENDER as 0x4c2b5395dd0b94441082b9586bcd3826dec09abd. [TRACE] Debug: 4d97f33810b4f83f. [VALID] Comparing result with Triada-Security-Standard. [DONE] Scan task 0DBB025C finished in 82s.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xca21c32f1ca1795d36ea04a23f91c274bd06d4af 0x10e2c49e44b7456fa88b48098ae4dd3650e0199b 0x5e3fcf3fdd1ad97916fe152aa8bd7a5ad0ea97a2 0x5522ec80284299096331656eae8a20cc1173e56b 0x3390186f6f013ea28f92df902d5cf8745b9ddbde 0x478bf562b2a39ff8530ee41ff0dfb39d8bdd2192 0xac510ef9e1ee169926fae7b68b7c25614f3f93b6 0xb80ea71ef331be93c386e35a5db1aeb15eee8698 0xdd9e86191e59293b00bb438146742049463a2a13 0x29c91ad854090b04d7accbe2393b921f39476da8 0x4dcc626de114ed3c50c0d47159e5e74be3b888cf 0x45887cdafa4e511283ff9ba505da9901c8d893c2 0xf1558667e2f157965954a64a790cb49a20979d80 0x5c5980727005c8449965123b9f1746ab235b6070 0xa979f0f4fe82720c0659cf25b8b17948ee793909 0x397d7df89e109184df5ca344e00b6d6bd08c3a16 0x7db040968dae93ff467f0895b75fc7cc389f65ae 0xc7e750cdba95bc2f4766a481a1ce5ae2b294cc6c 0xd425c2446cae326b01abdd38cfeef9ee17ed75a8 0x4c32f90463a259f9b4ccafe28000102a25da1148

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

Schreibe einen Kommentar Antwort abbrechen