INFRASTRUCTURE AT RISK: 0x6e1d13cad41d4ec8945b0f4be84176f993c5c546 :: Infrastructure Scan: Active Trace Log Entry

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-D06BF039C3AE
                
Infrastructure Scan
ADDRESS: 0x6e1d13cad41d4ec8945b0f4be84176f993c5c546
DEPLOYED: 2026-04-28 23:23:11
LAST_TX: 2026-04-29 12:15:35

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Standard_Compliance_Gap
VISIBILITY: UNFINISHED_STATE_DETECTION

                                ◈ 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: 3A7C2C43. [NET] Routing traffic through secure SSL-tunnel… [FETCH] Received 75 segments of contract data. [SCAN] Checking ‘immutable’ variables and constants… [MEM] Virtual memory mapped: 0x0000 -> 0x7f6e. [VULN] Warning: IS_DEBUG_MODE found in storage slot 19. [SIM] Mocking MSG.SENDER as 0x53f6d03b07f365e204dfe3e37b443446f9da33b1. [TRACE] Execution path: 73% coverage. [VALID] Signature verification: 0x78468b840bb4c4749898c46007493f515dd5d3c491290215e34f9400ddfdbda9. [DONE] Triada-Engine standby mode. Load: 5%.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x0d96a1bbf158ee798df59e61829f190acd66297e 0xa44aa528a2e824b6f7ebd9a0a31889325e7bace6 0x450ca92818449ef5ca7e5f580dc4340b25768e63 0xa1aa828304a4f3b95f029693fa22ed8c5f08c700 0x15820b677487287070ce20f4c6b935ba0e377240 0x58e5b6f9e66cb3ae623792ec409a93f1c26e8062 0xcca2de2dcd81149a2a5c930a485074dec7b57633 0xdb20396fd58128f41684c0f2e604e1b5e4f0d998 0x43da34711b18fa5ebcc422fae4e7528ed1f3d4b2 0xf5c052f2d60c63004621291944e37a733198c65b 0x04b136b35d59f180a88b5edd8c224f4ce481e7e3 0xc0c98face6d31e0501e743b72d247749d6c1770c 0xf1f831be8eb1320cbd400d2a50b8d8522885a69e 0x1fb5789fec2bfca23dd61ff3ff755b7154c692c7 0x4b7c9ba71bce97c80e0c8065edffc4266035d99c 0x1045749b4111553a2896a9f338fc921f7e77a9d1 0xa5ab06d172a86e1caa82fb53c410d4ea3c7c5714 0x3ead840d32a52f232802f54e7773f4d9945dbe28 0x7631adb09161c35e7a6a99691c1d9906a3822228 0x03b04f605e007a712da624c3fc9e3b948ab1910a
Blog

INFRASTRUCTURE AT RISK: 0x6e1d13cad41d4ec8945b0f4be84176f993c5c546 :: Infrastructure Scan: Active Trace Log Entry
