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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-55CE3C88DE21
                
Infrastructure Scan
ADDRESS: 0xf3cdb7f10e98d2de7cc5e6dcfda0883cc3e7dc0d
DEPLOYED: 2026-04-25 10:18:23
LAST_TX: 2026-05-02 09:01:23

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Unset_Security_Flags
VISIBILITY: NON_FINALIZED_ACCESS_MAP

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

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Environment: Linux 5.15.0-generic x86_64. [NET] Requesting storage slots for offset 0x00… [FETCH] Loading bytecode into isolated sandbox… [SCAN] Validating EIP-standard compliance (ERC-20/721). [MEM] Garbage collector: 0.24ms since last run. [VULN] Analyzing ‘Timestamp Dependence’ in block.timestamp. [SIM] Balance check: 6.98 ETH. [TRACE] Bytecode segment 0x1f analysed. [VALID] Finalizing audit report for 0xf3cdb7f10e98d2de7cc5e6dcfda0883cc3e7dc0d. [DONE] Disconnecting from Ethereum node…
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xb463cf7abb2f0a39e356c5d3dac8f03e580b636f 0xf61bc41b354c1cd65a2e5cffacefd036e6fe3171 0x10ed36a1e9d8d992e96fd77d15e6a38ace70b723 0x4d3a0bdfc045e40de4a0bad3082a5bbfdc52c77c 0x8f6ac296b9da70d2e9cd2747a7ed8d3b383884f0 0x9c7497513f65c27aad57aa4a3d4172b335de91ef 0xdd05e819337719ae2206f8d91bcd0e75d4117e69 0x25ed8fbb2f7793db2ce27e726393bc2d9dcb9ca5 0x42e4d379730452d161c7f1e7ce5c05e1827f6e88 0x4da17ee0f0030bba1e444169ff67ac09656bb0db 0x05ede4344567e54ae3041187b4280c8a7e101af3 0xc92b7f90fe70bc444d43b2af20fd6f1cd65c1cfb 0xd68832cde2f5d3311b88d224d84d43475bd489e9 0xa6266a29fa7f11d78104bd9cc413d923f0f8b5e3 0xb9f44e37f7f43e76486e37c4ac5646147f64f369 0xd406f183b34f3b303824f3f0ca694e4954aaaa1b 0x2ca0036b559c1e293eaac9dcd4674a0316d3100a 0x2e14465a9e858e00f4302ab60cd7b6c120efbc7b 0xca181a7ee5ffc37abc76ac400d27695b295dbf12 0x6bc40343b215a0d9aea80cb94c81e61caa719a6b
CORE STABILITY RISK: 0xf3cdb7f10e98d2de7cc5e6dcfda0883cc3e7dc0d :: Core Analysis: Debug Mode Flag Persistence

Leave a Reply Cancel reply
