0xb809dc13a337515dc2978d3d674096d40113abcd :: Logic Analysis: Residual Debugging Functions

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-88BE73349950
                
Infrastructure Scan
ADDRESS: 0xb809dc13a337515dc2978d3d674096d40113abcd
DEPLOYED: 2026-04-23 10:05:59
LAST_TX: 2026-04-23 10:22:59

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Standard_Compliance_Gap
VISIBILITY: OPEN_ADMIN_ENTRY_POINT

                                ◈ 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: 20ms. Protocol: JSON-RPC 2.0. [FETCH] Received 33 segments of contract data. [SCAN] Running static analysis on JUMP instructions… [MEM] Tracking pointer 0x27a3a654 in memory heap. [VULN] Checking for ‘Dirty High Bits’ in address casting. [SIM] Reverting transaction at PC: 3979… [TRACE] Stack trace saved to /logs/TRD-84D41EE1.log. [VALID] Consensus reached on node cluster: 8/10. [DONE] Results pushed to ADMIN_DASHBOARD.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x73c33926b79e88291913d110d7a3979ccfdf8bc9 0xde050066092e82e566ac64e4e0058662ae4de10e 0x7fe423f5b0203d4f2d8b08a3705b48c129ba2e2d 0xf6ec158f38e30a8fb9ac27b719cb05b8e37057e4 0x9fec475d0f4b517da656b85b11c5d8ef7e1dda36 0x2fc22143a04b71a68b804bfca054021879cceb13 0xe1b949469197f6bd6e2b7bf200cefe352ddf65bf 0xbf553d8e8803e3756224641143a932d20139fee9 0xeb56d795c90766f1193831effb043a468f47bdb3 0xa0da1fbab2d7a6a33170689ce38a4be2b980070b 0xfa8682dd94f941acc16df7284b0511689b05f54e 0xb350cb9ded4001b16c4e53518f5d6627f1ee579b 0x08ee14cdfc21ae06838cfae635629a4f4b3a7be1 0xf7b708f165b5068278671d2a9f92d12d93ab9320 0xeb36ead844f4af9523e7bd35be6de6a04d506850 0xf9513a5b1a75110cd84b12566b818a3e82385c68 0xf3f7a038740615e5b961ff6ce0511437136d63cd 0xa06afa5ced46ff891228724de7019ee76e4e6cdd 0xb6ea8464fde0274ede6782eab514012d81205403 0x6e0740d8620b74ed3cc0bf3d927d6d0e17a40a46

796da11b4014dd2f9b49aac57e178322

PreviousWhat is Could not determine a TokenStandard type. in codama?

NextFIX THIS USE AUTHORITY RECORD IS INVALID. (Step-by-Step)