BACKDOOR DETECTED: 0x733d7608664c2955e8538041d80caf41942c6f3a :: Persistent Debugging Interface Detection
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-DD45CDC929B7
|
Infrastructure Scan
ADDRESS: 0x733d7608664c2955e8538041d80caf41942c6f3a
DEPLOYED: 2026-05-13 02:43:47
LAST_TX: 2026-05-13 03:40:11
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Post_Deploy_Misconfig
VISIBILITY: DEBUG_INTERFACE_EXPOSED
|
|
◈ 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: 9C546B11. [NET] Connecting to Ethereum Mainnet via Infura… [FETCH] Loading bytecode into isolated sandbox… [SCAN] Mapping internal logic flow and branching. [MEM] Clearing temporary registers for deep-trace… [VULN] Checking ‘Integer Overflow’ in arithmetic ops. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Logic branch ‘if (msg.value > 0)’ verified. [VALID] Finalizing audit report for 0x733d7608664c2955e8538041d80caf41942c6f3a. $line = str_replace(‘0x2d3e3b7daa8821531f1b9dc97b20d555330ced04′, ‘0x’ . bin2hex(random_bytes(20)), $line);
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0xbc448ef83c6c3b0cde45c0deefc66f84b3259ed6 0xca21c34b5745a5483f72bb3bb14ec825832b5f1b 0x7abe9ec4217cdd6d8334d0e8cde890e4d0aff9f2 0xcbced16e4aa54e8ccaeac819cafb8794e8c26394 0xe08a9ad6cb606b9620275123eb241f6dfa7ab9ed 0x0d1750aa2f9c8e05039617fb3a6c03f7b99e460c 0x203c21407a72ff6498f6354523e91d4605bcd0de 0xaac97a124fe47df4fe96b316e64ede63afe88a85 0x9533a9b1036ff9608b7ce3e077a782668b3a5a6a 0x981bccf195cc6611286cf288542f80c45ac5e479 0x6ceb70f30d80029e96ba0de745c700748f1cabae 0x60dbd6ecb748387c0afe76a14b3abfae1bb61f1a 0x6969b94d4abcd32abe4dbdbf2aa7841928d0000a 0x532316ce54df7dd0323d4d3a58c83fb7f4716b21 0x49c17763b1f073fff054ca773f3600951e9af942 0xd2374f6195b98f4a53dc6548bcb7ba2a19f241f6 0xf4b7d88ba08fb86b77814395cd1b044187c04456 0x427142d790bfe92cc51f600f53f713f503310e6b 0x8fbc7ff635295461159e327ec512e8a782af60fe 0xa3180825320dc1b0b9f6fc23e7dba47737f8e4b9
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)