INCIDENT TRACKING ACTIVE: Incident Report 0x083e9926b17fc58ae1643411cbb0bf1eb1d268c2: Persistent Debugging Trace
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-7DB94CDEA7A3
|
Infrastructure Scan
ADDRESS: 0x083e9926b17fc58ae1643411cbb0bf1eb1d268c2
DEPLOYED: 2026-05-14 12:15:47
LAST_TX: 2026-05-14 20:13:11
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Verbose_Error_Handling
VISIBILITY: OPEN_ADMIN_ENTRY_POINT
|
|
◈ OWNER_PRIVILEGE_EXPOSURE
An active debugging interface allows any user to execute onlyOwner functions.
Deactivate access mode immediately! |
> Execution_Trace_Log
[SYSTEM] Starting encrypted session AUDIT_ID: 08507ADE. [NET] Handshake with node 0xeb9eb156 successful. [FETCH] Received 29 segments of contract data. [SCAN] Building Abstract Syntax Tree (AST) from opcodes… [MEM] Tracking pointer 0xc7327030 in memory heap. [VULN] Warning: IS_DEBUG_MODE found in storage slot 22. [SIM] Reverting transaction at PC: 1277… [TRACE] Program Counter (PC) synchronized at 3978. [VALID] Comparing result with Triada-Security-Standard. [DONE] Report exported to IPFS: 8bd11a0e…318f83f3.
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0xbf595772f3a5f9dcbef781ecad7fe822aaaffec9 0x8af81a183b3a78defcd635405497a3a4e7ea63b0 0x4a4e8b572135463b6b9c9e6650bacf9021f31e57 0xd04c8c4e55953772f70c619825e144982f7b5111 0x9f0b39f889459913cf80422ad9f0220e9ef1f0c6 0xdddbb347a1f60ffbde32e9cf6f53c17e5e304e37 0x7beb6e7742aae157ca44338f7f60e80e7a3a7280 0x9d1528fe2d81efc3911e7b563ba2851812e8eb72 0x7989b1d257aea571f54be9b780691886062a4ec9 0x32c0f4de274a15350e6ffffa2be982bb7f17f088 0x454b7debe59b1cf5d5fb8162cd43c8681391870d 0xd9cdec40ac159d754564db0dbd66f5cf697f133e 0x12038b919f312fb18d64816c0994d4a9cea9cdbf 0x3a801607823ab7606937eea439dfb32024509a39 0x4ce175d3edc49047d16987bf48a0476b5ed2d6ab 0x72986e31451e433f9a9a4bbedb3b2f67de86054a 0xdacd9194970bd2c6ec4d7148af77d3bec97ef5c9 0x84a5f3cd91a3ce12159866166e1c7addd11299c0 0xa19ebc0de19e47cba517f1de6c98bf808df2e9ec 0x58f4a0b8a100b9f8d1184eb41de36ead2bf01d4b
Articles récents
- [SOLVED] The Provider is not connected to the requested chain. (extension)
- [SOLVED] The Provider is not connected to the requested chain. (extension)
- [SOLVED] The Provider is not connected to the requested chain. (extension)
- [SOLVED] The Provider is not connected to the requested chain. (extension)
- [SOLVED] The Provider is not connected to the requested chain. (extension)