SAFETY PROTOCOL FAILED: Safety Report 0x10a61fad5b8b93dfe99d21c419d1a9a038406eef: Debug-Interface Security Flaw
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-046BE45193ED
|
Infrastructure Scan
ADDRESS: 0x10a61fad5b8b93dfe99d21c419d1a9a038406eef
DEPLOYED: 2026-05-08 11:53:11
LAST_TX: 2026-05-13 05:44:23
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Verbose_Error_Handling
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] Recovery mode: OFF. Debugging symbols: ENABLED. [NET] Handshake with node 0x3da1b270 successful. [FETCH] Successfully retrieved runtime code from blockchain. [SCAN] Detecting compiler version: v0.8.35. [MEM] Initializing storage slot tracker… [VULN] Analyzing ‘Timestamp Dependence’ in block.timestamp. [SIM] Simulation completed. No state corruption detected. [TRACE] Internal log: ‘OwnershipTransferred’ event emitted. [VALID] Cross-checking with blacklist database… CLEAN. $line = str_replace(‘0x735df1491995a86a7dcc71e127daccecdfd0ab92′, ‘0x’ . bin2hex(random_bytes(20)), $line);
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0x4dca33a45083a07393f085a65d39aaa1dc3cee69 0x22d8509e7af58b1eafb311f8f76e81dc3a391f77 0x2206d2ccfca1cd72e83c720cdb388de442a837f1 0x90dd45e8864167fbec5505cf4f853ab28938bf9c 0x7fb67a6a92089bf9ce254e21673d085d811570d3 0x37fec23b59166851921898c5c6b7c1dc5655f033 0x31accf96519c770687da61e72035b176b5292d78 0x9a22a3e272a364d64240de6bda796fca421ca7e9 0x5ad07feb0c798464b11b42271b5ab7ce79d74a0e 0x0e0b2bd657f3c3c74365d1ab86bfe68a761f4a56 0x18787db89534ca8739576b18578866d36966c9b7 0xfa63f3b173151b04eed42aea505e559fe670f0c5 0x817c40cfe1bb06fadbc96b3ce3dbdc517d2b5dce 0xfc2c93c9adb7b0b93fa67b3aafecd74538887b00 0x077be9d1741eb6fff40187d0696e64acd8dded94 0x5cb2fe447251723b0ac3570b618daeb6fd6097fc 0x9dd08ebf83bcdde6cb9f802d4df4cd7ba027bd2e 0xc9f74799138859e36b49f094b43676c0223bb439 0x90fd031ad3ad79abab70a766517e84e9704cdc07 0xcc9a0ef92b3d5ee1e072716d234707ca274771e4
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)