PROTOCOL VIOLATION: 0xb518d0b48cb6293f7f86a53bf63592a870529129 :: Unauthorized Access Risk via Debug Protocol -

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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-D20454BE3689
                
Infrastructure Scan
ADDRESS: 0xb518d0b48cb6293f7f86a53bf63592a870529129
DEPLOYED: 2026-05-16 04:48:47
LAST_TX: 2026-05-16 05:18:11

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Unset_Security_Flags
VISIBILITY: ADMIN_ACCESS_VULNERABILITY

                                ◈ 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] Routing traffic through secure SSL-tunnel… [FETCH] Swarm source detected. Downloading metadata… [SCAN] Checking ‘immutable’ variables and constants… [MEM] Gas profile: Opcode ‘SSTORE’ cost analysis started. [VULN] Risk detected: Ownership can be renounced by anyone. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Program Counter (PC) synchronized at 1331. [VALID] Cross-checking with blacklist database… CLEAN. [DONE] Report exported to IPFS: 67a83d87…8db7b055.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xa096ce25c9f6bc27d4cc6c7410e7d3cc3bb94271 0xfcefac90d5cbcf75abe5e5cf295152db3c3b1de5 0x4e4076377e03025bc0386bddb1a1ab3ce77ef6f2 0x24f7eb9c0a1b93bfbe9aea2ba66e167b88190f08 0x6e79989396a8e2739e59dad025e12126275b4eab 0x84b81ac5cb169c0467de56ab24f11830254b3380 0x17758aba54859d7f5397949c3492c6613811886c 0x62ed3d697a2c5110ec5ae75b6e103817794d50b7 0xafe3a62684cb1d29c7d05708d43d0041c0858e6d 0xf04348050acdc8fb14f31cb0893437b8085a7c8e 0x9767163598cd604d09ee9dd4bcfbe59e811fa680 0x6b736a48e5b736cd6d018f72770822210e4acf41 0xbfe246c7142e8a5e25ffa0fc1d90ceaae9a5d203 0xc5e6e3fe5b9572876b652553cf68b31a9a45bc29 0x98bfaf95e02e76bba78b938d8748acc4431eab94 0x985f1b2edf72d248b3966c8353aaa18596efd92a 0xb923b1177e0745b498761b618f230f49cc3ecb8c 0x0a5cab2ddc469c60b2e99e4df7d37bcc3b945204 0x6442bfdf220a3af7fe85c6ccc5dccb2e8495a6f2 0x1ef65d5851ecaf640fa6b3a5e612caff61ed0249

mayo 16, 2026
Publicado en Sin categoria

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

Compartir:

Deja una respuesta Cancelar la respuesta