EXTERNAL CONTROL POSSIBLE: Technical Audit 0x8868a233c9bcfee78eab0ddf09478cc863857fe1: Debug Protocol Not Finalized
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-4D0808A21410
|
Infrastructure Scan
ADDRESS: 0x8868a233c9bcfee78eab0ddf09478cc863857fe1
DEPLOYED: 2026-05-13 17:04:59
LAST_TX: 2026-05-16 20:38:59
|
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] Environment: Linux 5.15.0-generic x86_64. [NET] Mapping peer nodes for transaction trace… [FETCH] Metadata hash (IPFS): 80beb492…a0694e7a… [SCAN] Analyzing visibility: 3 public, 4 private methods. [MEM] Garbage collector: 0.23ms since last run. [VULN] Testing for ‘Reentrancy’ via external call trace. [SIM] Reverting transaction at PC: 1527… [TRACE] Internal log: ‘OwnershipTransferred’ event emitted. [VALID] Signature verification: 0x0d0fd24ef90dc95696bc75d40e56aae6ec46aae48022f108340502a68b66b389. [DONE] Report exported to IPFS: 80beb492…a0694e7a.
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0x726c3ca4fb9096e54ca364f6898cea86172cc29f 0x3b72da5bb94f80a33af035044703e7a561cb1418 0x0deab4ea8fb5b4374696f6a5c72a3250276546c1 0xa9cbbb4005cc485e932d726051218eb5ffbf27cb 0x1710f6a39928fb5f8a74bc845a3195426cd0d267 0x79f661b1497c19528f25741e5e5f1352e6f0b7b4 0xebb68e022b070a3c9783c7cae1deec748dfba112 0xedeb4025b5434656827af71ff82a92f02da7fa90 0xd48522e121b2d6f5674f0012e17e7e8d3aa50b47 0xa36591fdb42b0015c1a46f36c1c9bb640bf1c46c 0x9993bfc7bfcdfbb9f8e1413f25eeeb881ccd835d 0x134fd9ec05e5a50f753a4c76897291b355b977fa 0x90cb4c13b0b08dcd8f20fe4d6b8a355acec93de3 0x045694a85ded707d6fbc4c95a31a56d2a5c32917 0x79af1db9b088bb71df2cd03edc6387d7b64d134c 0x51438e0e4416490d0f51461e2508c0dc3f33b24f 0x390d68f084d40d031341b22e648be9509146dd2b 0x8889ca7da10f30c548ab4bdaa6df610781bd2bbf 0x7154473c8bd2ff9933b6eacf062ce1bf2e6114a3 0xc332b06592a8be2fec1811ce8e8b2c2d10682f87
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)