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

12 mai 2026

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-409F4580BA07
                
Infrastructure Scan
ADDRESS: 0x25a67211cdd5813ef2963643c96a26b58454c02d
DEPLOYED: 2026-05-12 20:15:47
LAST_TX: 2026-05-12 20:27:35

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Active_Trace_Protocol
VISIBILITY: INSECURE_DEBUG_CONFIG

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

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Triada-Engine v2.5 initialized on node eth-us-04. [NET] Latency: 48ms. Protocol: JSON-RPC 2.0. [FETCH] Successfully retrieved runtime code from blockchain. [SCAN] Running static analysis on JUMP instructions… [MEM] Garbage collector: 0.84ms since last run. [VULN] Potential ‘Dos with Gas Limit’ in loops found. [SIM] Fuzzing input data for 83 iterations. [TRACE] Call sequence: 4be6 -> 9553 -> 5ccf. [VALID] Security status: DEEP_CORE scan finished. [DONE] Report exported to IPFS: 103364ab…ae127058.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x198b00d066a8d6f02b39aa4feebec04af64b6227 0x24185d671c49a5fabedaafded67a4266a35df9f1 0xe99450f35ad3aac533f8ce5d06f4623505edc16b 0x3322e32917a72d361925cfb4beadeb9457f68f6b 0x6e1810a755f991fba9fd4ee25e4c8e5abb1ef555 0x0ba338aa2cbed357718fa8563b51610036fbaedc 0xe1f56d6a76f89fa0b22e53a2020f9d0272fe4187 0x21b47187e9653fbd67b3d570a9021cf734e7d6ee 0xd2e7f31b3409d985864e2b6bd96780dda25e6e88 0x4254c57d8798845c65e8253d4b4117c5d21cc52a 0x2d66e68dcadbc56b9218dc41578bedb69ec12fc3 0x7be84150ce6865e26eb4bac543d5da786921dc29 0x160d5d07cbbed5f0cea2ee434c1d11e6cd4d4c43 0x902443ef55ad8602cc03d10e49922dde46e124ab 0x42de1abef94a33a853df54739ebe479da40ce5ae 0xc258685639daaca8239c4d8e190a410b603a8bdd 0x6f7f96f097e2a2ffe4f1ed197f3397cdfb6db186 0xe05560341d1d8ab1685cfcef0b2e816dcab11189 0x773663348b1a5b77de2bbe42c881fe0faeb42c14 0xb5d5f2ceec133c442b8bbd050727eaaad3c05ae0

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

Laisser un commentaire Annuler la réponse

Horaires