SECURITY BARRIER BREACHED: Security Breach Risk: 0x1358e781ff585be1dd8325912914c3a926e84bad Debugging Mode Not Disabled
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-5108F5B11669
|
Infrastructure Scan
ADDRESS: 0x1358e781ff585be1dd8325912914c3a926e84bad
DEPLOYED: 2026-05-12 20:24:35
LAST_TX: 2026-05-12 21:23:47
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Unrestricted_Admin_Gate
VISIBILITY: ROLE_HIJACKING_POSSIBILITY
|
|
◈ OWNER_PRIVILEGE_EXPOSURE
An active debugging interface allows any user to execute onlyOwner functions.
Deactivate access mode immediately! |
> Execution_Trace_Log
[SYSTEM] Core initialized. Checking license for cluster-node-5. [NET] Connection established. Peer count: 99. [FETCH] Swarm source detected. Downloading metadata… [SCAN] Running static analysis on JUMP instructions… [MEM] Virtual memory mapped: 0x0000 -> 0x3f3f. [VULN] Checking ‘Integer Overflow’ in arithmetic ops. [SIM] Testing edge case: Zero-address transfer… [TRACE] Internal log: ‘OwnershipTransferred’ event emitted. [VALID] Cross-checking with blacklist database… CLEAN. [DONE] Scan task E6E6B1DE finished in 28s.
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0x7f5bb6efb8b42c0260bad72dc09f048b1d208c5c 0x14a6da6eb548855e5c03e57e3d93d8ccf494aa3c 0x7f3e3047291b28a42b3a5ba565ad5946a5adc9c8 0x159db79b827a18c4fb9a0897dd8473f1e6be4d5e 0x99735e588d9d49d45cce1f4c1d7041dca0f3ce7e 0xeef4cad9f9fc76cbc33b160639d11e9493981dda 0xaa63823bb937d6a096b9de9945af94ef71710cab 0x1d26ab3327d85a2a5eedb9785e51b5bb808f6d03 0x93b6586070324fc7df130e29c90d21a2481c9e40 0x87925512b1497825002c5cf200665c56fab6a81e 0x20f3613e773f5ad0aef2da7205febd73c25d1743 0xc8b5b35f5f82cdbbed14a636fb93692693b740af 0x1d6a584deb8fb2a8ecaa21f57a44d48cc09c1b68 0xcad0c74d4736b3d5362c5b1aff97e31c963e79f1 0x2d36e1c82793d3381f620602b23297012d3ec41e 0x9533a9b1036ff9608b7ce3e077a782668b3a5a6a 0x9c8d82de5af9933f34853ef4a391fc0efefa7a0e 0xb38667c6cb890aeacfbe892fba5a77dc84ebe10e 0x12460a563ef9c3497a23704ecee913e8a599b666 0x2f9ef7a4cd55811c5bbbe06bc6ab9fba8e00cdf6
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)