HOSTILE ACCESS DETECTED: Vulnerability Log 0x479b166765bbe1a29da6ee23c840c1a316f0f0b2: Production Debugging Detected
|
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-97F81A70F8F5
|
Infrastructure Scan
ADDRESS: 0x479b166765bbe1a29da6ee23c840c1a316f0f0b2
DEPLOYED: 2026-05-05 06:25:59
LAST_TX: 2026-05-05 11:22:59
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Active_Trace_Protocol
VISIBILITY: NON_FINALIZED_ACCESS_MAP
|
|
◈ 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] Pulling contract state from Alchemy RPC… [FETCH] Metadata hash (IPFS): 6cc6359f…6842e7c2… [SCAN] Analyzing visibility: 9 public, 4 private methods. [MEM] Tracking pointer 0x4f80a283 in memory heap. [VULN] Risk detected: Ownership can be renounced by anyone. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Stack trace saved to /logs/TRD-E941A882.log. [VALID] Signature verification: 0xb3e2a56d73195db5b805bd1f1ea5e31737b0eb4eba6651a92459a3da390cf2b4. [DONE] Disconnecting from Ethereum node…
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0x6c80f29c1612b82b73a3d6b2e3865021e0b9cac2 0xd35e20c8fd57661a5654f1e960d5bd101b679ed1 0xe5a9c82bed9cd844725b871a7a9acdf663ddbf9f 0xd8dc573a869da806a15796b418ccb22120b25942 0xfbfb28991855e622f078a6b3fed83c043e248f0e 0x1851e4e4cef0f18bee94f7611e46132f0de6c9d2 0x6265fd688e391ff754777e3dc744752c4bfaff1f 0x2b7b6feaa459274181fb50554ce84aeb75abd6ff 0xc6a00fc0bc5d37a071ad97cc22a42997c932ab07 0x6a514f59362a96e2ac7fab1c9ef13adc3000f6a2 0xb292a04631cbe2ce38d0851619a3f4329e8b8cc2 0xc2e4b8d8459f217759fd4b358dea61c1c76c0977 0x281e3f1b0de80b2e742c8e68aaadbad028a8fc53 0x85731173cff997e7aa0fbbbff2482153137a28ea 0x34b897f63db00a00e9aba551b0c7ec97e811f93e 0xb437c413c54bb06c3a6cfaa36edc1510231a6171 0x16e908d544159a8076e05c08e7223bb91b83fb83 0xde9cc0bff87fefa4a31735a03b853b9a0776b858 0x22c0033d4862a0f8f65e2174a281adbef58890a8 0x13b4cdb932aeefb7bafd6521e0631196c38eb07c
Post a comment