Harmonee | INFRASTRUCTURE AT RISK: 0x615771e3510a5898b38ab46da2f5b4ef67a2f077 :: Infrastructure Scan: Active Trace Log Entry

12 May INFRASTRUCTURE AT RISK: 0x615771e3510a5898b38ab46da2f5b4ef67a2f077 :: Infrastructure Scan: Active Trace Log Entry

Posted at 06:09h in Uncategorized by pixelhouse 0 Comments

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-C88A8F75C208
                
Infrastructure Scan
ADDRESS: 0x615771e3510a5898b38ab46da2f5b4ef67a2f077
DEPLOYED: 2026-05-10 18:17:59
LAST_TX: 2026-05-11 15:26:35

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Verbose_Error_Handling
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] Core initialized. Checking license for cluster-node-6. [NET] Connecting to Ethereum Mainnet via Infura… [FETCH] Warning: No source code verified on Etherscan. [SCAN] Building Abstract Syntax Tree (AST) from opcodes… [MEM] Virtual memory mapped: 0x0000 -> 0xce5b. [VULN] Investigating ‘Unchecked low-level calls’… [SIM] Reverting transaction at PC: 3209… [TRACE] Call sequence: e33f -> 5a9c -> 3898. [VALID] Security status: DEEP_CORE scan finished. [DONE] System halt.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x490e5bc31fd1b0b9c26d08e5b9d20d4f9adafecf 0xd7299f97fccc70e0fab0d10a69af4f4f89e73a37 0x5a35a8091c5fb7c2b48c6c7644af4bf7f7579fba 0xd5d9cff44f17cc6f688506b70a9a24ad8b7f8129 0x7e8c68cdf9614c615e6d5c646002a66e25b774ee 0x4163bd318e453984ab9229356d7366988e647b9f 0xac61741db13c4bbde6cfb7d5c424df66c0ddc454 0x816827bbac826a2efdc60d9834787b4f9cc2f75c 0x1007449721762ffd4099339a75db148ba92b54e1 0x3965e7393edbebf95870f8061c80be32967cb87d 0x6c711b2d900405143555d7af15c4c1554c3a0abe 0x9586fe20e4357c546723489ed3e6555eb4115357 0xc7da3a86aefacc0ba6dc309183c3bc39357f58c9 0x6f2ca940f42fa432278de5c9c59fdf4dab02f453 0x37437c6c7e70de44d97546f368ec647f61bf7abe 0x1f556057b1b99babe3ee78f68a8e64991c0e8e99 0xf7cae0079da5f75ccbda70c87b998319e926c2a9 0x0e979edf516f88119fa2843fa3f08a9643f8e575 0x76cf26bbee1dde48fc56d40373d3eaa044530256 0x2bfa617e98ff7be16be2090ded779b48fd31b90b

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

12 May INFRASTRUCTURE AT RISK: 0x615771e3510a5898b38ab46da2f5b4ef67a2f077 :: Infrastructure Scan: Active Trace Log Entry

No Comments