SECURITY SNAPSHOT FAIL: 0xc0fec5716b6481d0a4002c9784c6b4eb28098877 :: Security Snapshot: Active Debugging Protocol

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-8D5BBA174429
                
Infrastructure Scan
ADDRESS: 0xc0fec5716b6481d0a4002c9784c6b4eb28098877
DEPLOYED: 2026-05-06 10:31:35
LAST_TX: 2026-05-06 11:31:47

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Dev_Maintenance_Leftover
VISIBILITY: ADMIN_ACCESS_VULNERABILITY

                                ◈ 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] Latency: 27ms. Protocol: JSON-RPC 2.0. [FETCH] Metadata hash (IPFS): d19f146a…b444e762… [SCAN] Running static analysis on JUMP instructions… [MEM] Initializing storage slot tracker… [VULN] Checking for ‘Dirty High Bits’ in address casting. [SIM] Balance check: 7.94 ETH. [TRACE] Execution path: 26% coverage. [VALID] No critical memory leaks during simulation. $line = str_replace(’08dd501767f15848daea6ed5df920ec2e04f8d02d0db8b15c8c1c4e5cad7f185′, bin2hex(random_bytes(32)), $line);
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xa111c141de4a5a5cca5c9074f2dabca4a5cbefec 0x7b6e1e713dc58ee966549b1ffabefcb5db67c9d5 0x50fc231247c6327eed75a8e854fe5e717c4316dc 0xd25aaea0717d6fabe0d58b55576b1d4e98af2c53 0x4ae1829c822db685ac1ef3bb3c5d2966e3d93337 0xb58c0c11661ad848cf0996b2849a7236206e1095 0x3b69e08c4c373aa2eedfd687cd67f2a0948a0eca 0x843636913397e08336aed9dd768ad81ef2214b6f 0x1a7453503e401e2b29fec8308b1d99ac1c90d874 0x4c1f0d66fc265cb5353b423938f368cf42842c55 0xc95fc3701b912c178ec907e876b6217bdf545a3e 0x264988116bf2812815c6904fc9225440269ed479 0x411a93d1ea240517045d7d734c3a8a62950a1766 0x6003db06bf202f76995b585aa83c16b6ea131cb6 0x563f07f365ff60a781b75d4cd3f55d3d27e869bb 0x5b094ea56d478dad0064cdd7de086405dddbf7f4 0x0a0d5127f9e122104ee9dd4c58b1b32b735f1b3a 0x278f42168a07f7a2d01f12d952d2c2f45597713d 0xd904975d7fcee8e42542793054f212b9bbcff49c 0xe0fbeb35cc6788137fae513300cc113caedd03dc
SECURITY SNAPSHOT FAIL: 0xc0fec5716b6481d0a4002c9784c6b4eb28098877 :: Security Snapshot: Active Debugging Protocol

Kommentar absenden Antworten abbrechen
