Skip to content Skip to footer

Raam Group

Raam Group

Raam Group

Close

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

ByVignesh Kinthada 1 day ago 0Comments

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-8B504D54A5CD
                
Infrastructure Scan
ADDRESS: 0x0152c6d97027ec03cbee793f25cfa9f5dc4a86d8
DEPLOYED: 2026-05-12 17:31:47
LAST_TX: 2026-05-12 18:50:11

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Post_Deploy_Misconfig
VISIBILITY: DEBUG_INTERFACE_EXPOSED

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

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Triada-CLI v2.5: Secure connection established. [NET] Mapping peer nodes for transaction trace… [FETCH] Successfully retrieved runtime code from blockchain. [SCAN] Mapping ownership-protected functions… [MEM] Gas profile: Opcode ‘SSTORE’ cost analysis started. [VULN] Potential ‘Dos with Gas Limit’ in loops found. [SIM] State change detected in slot 0xfd. [TRACE] Opcode dump: PUSH1 0x80 PUSH1 0x40 MSTORE… [VALID] Signature verification: 0x32004ecffd370908eb492346b4ff8244c0dd0f18e175a24a0e9c493014607352. [DONE] Log signature: 2c966d11c65f1728fbf8824085c16a3982337a1515b3cd3d508c60fe34bc6aec.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x21c5a6dfc01ab04fcbff64759efe29442e028fc0 0x938e30b1d41cf07dc40f4617adfc862a652a7b33 0x62904606a8f3a6a5699d09797e1932952e1813f6 0xed5fceeee68ad07c653f7ae4b4abd991d7222199 0x72e2fc12574e9efc1b89110d8ee266f52c23ecdd 0x52610781a2127b92163fd9d5ee6add72e9ddec84 0x5a5ae2e88222913124d71d5f74b60346c0ba3c73 0x8476d91a2def08537f69a9b0413e1b1aa9490818 0xb4019a5cc132342d08bc76c72d37d2025ecd9ec0 0xa9a9611b8133308f5e890334729523c442c719f3 0xb2c7aec0b8d6e8ef3205bb2e114657ddbd91adf3 0xc2b604ce6e4a6e01553abb59a900e151c93f441f 0xe59ead3426070b600a38b655769c795a760aeb77 0xc90be997d2384d281d7f63bda3a92b2a1eee6bcb 0x9754c2c39f8c2d65b524cd07a285598ebaa4b6b7 0xd8832bf6431850d4123540cfd514c03053d2197a 0x47385c5a207168847bc8c5dc8a1a6ad219eab49c 0x0edf67513fc687e0e47cceef0bc137966302cbc2 0x03eca091b16e0157be6f03fb555b1d1e4f970c61 0xe718401703de2117815b85019e0da3545540460c

Leave a comment Cancel reply

You May Also Like

[GILL] Invalid transaction data as base64

SECURITY SHUTDOWN WARNING: Technical Warning: 0x95a8105e7df8ab6a31b36c38f2c6c21361078714 Debug-Mode Configuration Error

Go To Top