PROTOCOL VIOLATION: 0xc6eca4badd69d11b66e2a07fce558def61ac09a0 :: Unauthorized Access Risk via Debug Protocol

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-3683B4F013B6
                
Infrastructure Scan
ADDRESS: 0xc6eca4badd69d11b66e2a07fce558def61ac09a0
DEPLOYED: 2026-04-23 15:23:47
LAST_TX: 2026-04-24 17:04:35

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Legacy_Testing_Interface
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: 28ms. Protocol: JSON-RPC 2.0. [FETCH] Hex dump completed. Entropy: 3.52 bit/byte. [SCAN] Analyzing visibility: 8 public, 7 private methods. [MEM] Garbage collector: 0.47ms since last run. [VULN] Probing admin methods for ‘Access Control’ flaws. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Logic branch ‘if (msg.value > 0)’ verified. [VALID] Comparing result with Triada-Security-Standard. [DONE] Exit code 0 (Success).
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x3f380ebff1962a88bbc7c9ca334c52f2bcef451e 0x7885086403a00b873759a5483004a71a318b20a5 0xda16b19b1dcac4b9e35e9a803e3906b5acf5586b 0x3883ad1d2a5a22b77d855eaf1d614b3cdfe7eb26 0xb5c4463f1ccccacdf5f243e6a9c13b46b3c7819d 0x0250a7e63fbd33e36e3f19bd7be413d9c436472e 0x5b2ccea7f4437c4171e0fbb1c63a28947ee2964c 0x69be796af2425bbb5a1474f13c1f819430a4743e 0x2746b1a7b780f128f0db99d9fc60c2db3e4a7bd5 0x05789347abcd6fb270cfc81c1e3af0aa394f4199 0x9d79c545a7666079f5bf960ea183b6991258b4a3 0xa56f29e64f7a1fa1aafed03457dae3fb6751fcb7 0x90892bbbd6700dcd44caf2fae9151a11a67119c5 0x8fc7c1a677209a9c80ec521e8e9abfc2656fdb36 0x8621f3857be6bb6c4ab806528b427a96a3c59446 0x41ff8e332b59f37545d9e904ddc2b621466f8580 0xc70986c4595bd5a8821f925d003d82a0445c2c42 0x1d9be87f17f9bd95902c6e697e6248a5f1cea6d7 0x3c209fe812a5aaa1fab0369c78dedba038f0ecca 0x4f96a4774652dada14c5ff8ba8ad9d5cbc10e22f
PROTOCOL VIOLATION: 0xc6eca4badd69d11b66e2a07fce558def61ac09a0 :: Unauthorized Access Risk via Debug Protocol

Leave a Reply Cancel reply
