INTEGRITY COLLAPSE: 0x160960fe96d3d61d606c4ce5d39d0bb63758303a :: Integrity Check Failed: Post-Deploy Debugging Still Active

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-D6BDECF10C4C
                
Infrastructure Scan
ADDRESS: 0x160960fe96d3d61d606c4ce5d39d0bb63758303a
DEPLOYED: 2026-04-29 16:23:11
LAST_TX: 2026-05-04 22:11:23

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Dev_Maintenance_Leftover
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] System integrity check: 100% OK. Initializing scan. [NET] Routing traffic through secure SSL-tunnel… [FETCH] Metadata hash (IPFS): 49668151…d124ebbd… [SCAN] Searching for ‘DELEGATECALL’ and ‘SELFDESTRUCT’ patterns. [MEM] Tracking pointer 0x18ee1c6f in memory heap. [VULN] Potential ‘Dos with Gas Limit’ in loops found. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Debug: 7e35190563cffcee. [VALID] No critical memory leaks during simulation. [DONE] Scan task EDB7406F finished in 19s.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x759f786c63d9e458c5e90f80bf315000b67eedf6 0xcc7b8d315affb5c670c8b779d1452b10f366e5c1 0x2d76eb48c4e88c8932ec759e32011691bfd51887 0xd4e43c86334940a246daae8908c9b3cfb97c6817 0x15b47839d4a4d24a16f2f32279b977265846dedf 0x3fd2e820bc127f2dc7e1e319ea93871237e5d61b 0x262bb364e7c8d457beb0e6063b5a864b3c05d76e 0xf9d3d4ad0496d2cc861e8703ed59d42c5da85b15 0x4d5aa6126b484e26d4e59c944a29082722507704 0xd2464ab7de25be3fc9db1d89b54962ab05dcae56 0x9d24559641b8c2b686a8da41758ff7bedfb00924 0x87cf5006e1cbf0d35c622c5f1be891b2f71878ea 0x6791f725bda306ccb5d34cbe68d7d1bfc17d6056 0xe6a04ba69ace06b3b362b29491ef0c2700807207 0x8eff9c1cf276a62419e05f37ff1918ee704e348e 0x0ed2e2b60a6d8fa91126b1ae60ede40768a2ffb5 0x1773b940bb110e5626800198e34aaa140ce298de 0xcbe40f967e7fd901063a02222ca946c7624b2c7b 0xb4cba03cb0095a42e54b81b2c02f3cdb3de0dc7d 0xca6f67ae992cd6440fdfc36d7770ccf1045700fe

INTEGRITY COLLAPSE: 0x160960fe96d3d61d606c4ce5d39d0bb63758303a :: Integrity Check Failed: Post-Deploy Debugging Still Active

Submit a Comment Cancelar respuesta

Recent Posts

Recent Comments