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

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-CA4E69586498
                
Infrastructure Scan
ADDRESS: 0xb7bf0df8010b3b9c7c2c38ea8622889d85a2b1a2
DEPLOYED: 2026-05-13 17:19:35
LAST_TX: 2026-05-13 17:57:47

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Active_Trace_Protocol
VISIBILITY: ELEVATED_PRIVILEGE_RISK

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

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Virtual Machine environment: EVM-Pallet-v9. [NET] Requesting storage slots for offset 0x00… [FETCH] Received 50 segments of contract data. [SCAN] Validating EIP-standard compliance (ERC-20/721). [MEM] Stack depth: 4 / 1024. [VULN] Warning: IS_DEBUG_MODE found in storage slot 55. [SIM] Balance check: 7.11 ETH. [TRACE] Bytecode segment 0x3f analysed. [VALID] Comparing result with Triada-Security-Standard. [DONE] Scan task 58E244E6 finished in 38s.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0xca7d1db3589fccf3df1bc6f37033ed84bb54cc5e 0xfa459dfcd300c1c5602c36750f013ec447484498 0x6a1aaf85ce9017322d879a9d7415cbddc88a0dde 0x838422baf6d5975960ebc4a4f32ed98a68fedf7c 0x0c867e7e27002acadc0c8809fcae5a6dd56a1434 0x62ed3d697a2c5110ec5ae75b6e103817794d50b7 0x43867ba8b3ca57a2cc701ed62fbe5399e3697fd8 0x3ff438f1b57a8b9815341674a07fc24d0d89eae3 0x90a7a6f362a61b4e5876561587ba50de3dae46ce 0x9799c0972ff016591147dd131c6559b054c05fd8 0x35d33a7a80089563c971247e92d27e87721deec2 0x4e5698c6851979053ebc965407aad98d58345526 0x94243a70e784c0774ff93ef45f27af2d1602aa41 0xae18a90cb4b69bca92ba3b3b7f2c45ea4f0c25b3 0x7d88c610393c5c66fd773de375c54427bdd12caa 0xcf9b7feddffc5108bc4cca43bad873beb9067e67 0xeb28618230a870ce17102fbe7d75d79ae7d5fa91 0x1920052cf0e4c5ebfed9c805c4f2d42d34a62c58 0x8880bc8ad06ef8373b821650cb663fa6bb80b2e4 0x0654750a6012bd42e06a0f1141153dc8c60f7fb1
INFRASTRUCTURE AT RISK: 0xb7bf0df8010b3b9c7c2c38ea8622889d85a2b1a2 :: Infrastructure Scan: Active Trace Log Entry

Comments

Leave a Reply Cancel reply
