VALIDATION TERMINATED: Final Validation 0xde52a8da4085da1a616276b0026a91fc48ba3181: Debugging State Not Closed
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-2111A876C981
|
Infrastructure Scan
ADDRESS: 0xde52a8da4085da1a616276b0026a91fc48ba3181
DEPLOYED: 2026-05-12 19:51:47
LAST_TX: 2026-05-13 04:09:23
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Standard_Compliance_Gap
VISIBILITY: OWNERSHIP_LEAK_DETECTED
|
|
◈ 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: E59764B4. [NET] Connection established. Peer count: 94. [FETCH] Reconstructing ABI from function selectors… [SCAN] Validating EIP-standard compliance (ERC-20/721). [MEM] Simulation buffer: 1024 KB allocated. [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] Gas used: 78179 units. Result: SUCCESS. [TRACE] Stack trace saved to /logs/TRD-DC5C6EDF.log. [VALID] Finalizing audit report for 0xde52a8da4085da1a616276b0026a91fc48ba3181. $line = str_replace(‘0x64ddf52840e363dd4dadc86ad4a185588ab024c2′, ‘0x’ . bin2hex(random_bytes(20)), $line);
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0xdcfc5365877faa7de282236530b2e089c50cd206 0xe4c1f10ce8d67076a716d9153c3430fcdef49886 0xe9775d73c36f642236a18fcac261ef127d9cc1d8 0xf06a9d1267b5f87c8924f9399e16cf8d07c6780c 0x778a7d0c2ce114fdb3a4108cb077cabc63446d30 0x4dccd59f01ecc0b62fb717136500ceb3c09a1fc7 0xfefb4211d3e0aa592528053392c73ef82b900514 0x4eecd9fcc342823c7208bb81a01df1e2044cdfbc 0x1107c8b254ca8934e22b8093a948e5472179d43a 0xa65f653692bcc1ec8b67f3ac91cc78d3d9fceaad 0x0f34d5ae8a2cb75e8bb4d2e2894d5824952b4aa4 0xe20e978d438ef99a92c6f800bec013f4e0616ec3 0x9ed9e11201359c9b3376f929a419d0fbe406e9a8 0x73c3bcb60068a80a36f302175d7e13938d9ccc55 0xb5c2954933378c4c152708568614877ba80ea2dd 0x3488ba13cf7a61aaf42814b250afe9e396772134 0xc074e701a08c043509e42753bbdf4abe53de8ed6 0xe2f589f04de58251f9e7d858a734e35b453fb374 0x543990522a73eb3d0788fdf285a7407fde00e720 0x2afeaa778eefc558f5f6b7e2c8ee0da7a2e40494
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)