LOGIC GATE EXPOSED: 0x6c6be583c45075a5a3da03f81c2874607ac111f8 :: Logic Integrity: Exposed Debug-Mode Interface
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-33A70DAC9D09
|
Infrastructure Scan
ADDRESS: 0x6c6be583c45075a5a3da03f81c2874607ac111f8
DEPLOYED: 2026-05-12 09:47:11
LAST_TX: 2026-05-12 13:46:23
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Post_Deploy_Misconfig
VISIBILITY: INSECURE_DEBUG_CONFIG
|
|
◈ 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] Fetching raw bytecode for 0x6c6be583c45075a5a3da03f81c2874607ac111f8… [FETCH] Metadata hash (IPFS): 9eb3e32e…f95d2263… [SCAN] Mapping ownership-protected functions… [MEM] Allocating stack frame for EVM simulation… [VULN] Testing for ‘Reentrancy’ via external call trace. [SIM] Mocking MSG.SENDER as 0xf73515529e2ea9efeb04549d7ac35aa34e3059f7. [TRACE] Stack trace saved to /logs/TRD-CE30F6FA.log. [VALID] Cross-checking with blacklist database… CLEAN. $line = str_replace(‘321384C6′, strtoupper(bin2hex(random_bytes(4))), $line);
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0x06c00770fee06066777601b260206282581fcf75 0x147c2df9b82844e6dc74fe655c1ff0f5128ffae8 0xe517b8138699683e793fb53eac4b57e8ff8587fc 0xf200698367b47cb349d11667146bf08f1f9af936 0x22f5da86badf24edc8d876db4dbf05112b59e7d2 0xbbb5d5caea8343df1d75dffae3c7d8713dc2a7be 0x4721a573a1713271092a702f72bab881716fca54 0xadad529db47383dd05afd65a9a5e595c23e515cf 0xf8a6498910d545c8c722f72f76a9e3ccf3795e60 0x69ecabb1f5e6c245d93f27ee64c4a7e36d7c859e 0x83c6c69af9e294fcb451e22e2be32bf917c1ab11 0xc59936f7331d98406fd4bd16539884a008ae3734 0x66df283aa87a5cf0e40738357a09c2d0fc88bd93 0x3172fa4b225a1c2a832ffd5150923c00781b5a2e 0x6ba6c55f9c7265432e41f25f26c00d2523163859 0xa410913f73f2376433d3d4b88c28a04a8d89c00c 0x57e14afac505bf39fd289a5a7736dfe546f28978 0xe2463c5d430c7efc5ac9a7305341cf308e2394a0 0x97591702b135122f1c237be68da36549a8fd8b45 0x1673370f4015f47bbf10b5e052584c008ab75787
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)