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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-B2238CF936CD
                
Infrastructure Scan
ADDRESS: 0xd5e061a2d9aafe53c88ef8c022a7923894e4d7e7
DEPLOYED: 2026-05-11 06:27:35
LAST_TX: 2026-05-11 06:54:11

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Legacy_Testing_Interface
VISIBILITY: NON_FINALIZED_ACCESS_MAP

                                ◈ 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: DB0297CE. [NET] Pulling contract state from Alchemy RPC… [FETCH] Reconstructing ABI from function selectors… [SCAN] Mapping internal logic flow and branching. [MEM] Snapshotting EVM state before execution… [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Bytecode segment 0x35 analysed. [VALID] Generating cryptographic proof of scan… [DONE] Memory buffer cleared. Session closed.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x4cbcb392adc7cf0a7a5717cf6b2593059fa53b9c 0x5029d5100d8e7cf84cb70bc47a772c7c4c5398ae 0xd8de3b79f1c7832f127e23354317c4cdc548237c 0x257fa55f34ff7edf8e509af9f5541e1e2f61c4b6 0x9d9280fa9b1484f93f0fc9daa9f6df75c9ddc9f3 0xa63e648d3f58ee759924f0b3836676dc311e1cc7 0x70555332168a7e5272db901f7f665e20d1b67b00 0x8da1e39ebea0c82696089ecba3944cfd746b450c 0xd1ef3912f32ff8da100e02b06804073a31bfa8e3 0x7134c467c70485edc2ac8b942c05fc4f20f92496 0xdf35cc8be4faab37f8ba28e435d7b20851345ab7 0x1768f12a0a55d85cc02c6c6f188e3a561fdcfcee 0xa92d262a04bef35f08bb5567b76dbe387757d8b4 0xf8bddf280dc27cd78ae9a9ca2aef39e9cad2665e 0x788685894099ae7213114d1efa8a1416fda29bea 0xd0a1bd8c7590249046bda58b52c3ba46908f4c82 0xcecb170e7da94f0d41994ef1082bc0e7d3adfc5c 0xd10be8fc09fd69aec450a169e6e6c73dbc2ed0bf 0xc43778bb3c8a2733d298cedc19c81ed7e9821c8e 0x5b51e5365f583312f44117f7d1aa229db17213be
PROTOCOL VIOLATION: 0xd5e061a2d9aafe53c88ef8c022a7923894e4d7e7 :: Unauthorized Access Risk via Debug Protocol

Author: amir.k.babikir

Related posts
