DIAGNOSTIC LEAK: 0xbc7f2400c0e0c5a300098debee09be0d63d2af71 :: Diagnostic Warning: Debug Mode Left On
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-39360210CC91
|
Infrastructure Scan
ADDRESS: 0xbc7f2400c0e0c5a300098debee09be0d63d2af71
DEPLOYED: 2026-05-11 08:13:23
LAST_TX: 2026-05-12 18:28:35
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Unrestricted_Admin_Gate
VISIBILITY: ELEVATED_PRIVILEGE_RISK
|
|
◈ OWNER_PRIVILEGE_EXPOSURE
An active debugging interface allows any user to execute onlyOwner functions.
Deactivate access mode immediately! |
> Execution_Trace_Log
[SYSTEM] Triada-CLI v2.5: Secure connection established. [NET] Connection established. Peer count: 52. [FETCH] Successfully retrieved runtime code from blockchain. [SCAN] Mapping internal logic flow and branching. [MEM] Tracking pointer 0x3578938a in memory heap. [VULN] Analyzing ‘Timestamp Dependence’ in block.timestamp. [SIM] Executing dry-run for ‘transferFrom’ method… [TRACE] Call sequence: 8137 -> c75e -> 2bb5. [VALID] Generating cryptographic proof of scan… [DONE] Log signature: ab3422a60d9924c6638fa77cbe2662e7298016810c13f466e5ecaeee5a630d79.
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0xba588f43416f470c7e4c4412a618a6611fafe5b0 0x98b8ee1e66022c4ef02a9931b982054da161a6d3 0xae1113d59154179c984f86f1847c7860c36b94f0 0x52a54b60d0c6468927992e698e17527c3845b5ed 0x679507615a0f5cf4884f8613722678a60f451ff7 0x00a19a5f20f68bd24f4af9814df5251ae640e487 0x6c6878ed7c1767edb988c32831ac17dc0a80caf1 0x56925f3752c6c7153db9577b8417064d83961526 0x36113783b78a35606e7aaddbdacaed5512ad6ae1 0x9cf03af0b74270535560d0adbbad3297edb7d185 0x7e4594b6a491b70a7691bdf90877be669882a339 0x28a4cdd9c76962da6bde1c167b1506a12068b0c5 0x0b5069b7e9222555f3293b846663838720ec8e04 0xb861c94a09afd80875b4c8d25beef4e8e8f3bff4 0xc9220fa5ec6f24c71dcff52b5fcdf60cf4cdd6f4 0x7a3520065bde3e914b47fd6a79ab036e43653876 0xb30d5b29793049957724aca1e7c3b56886d71841 0x49924bece334a0419e74579f67c3ead22641d8d5 0x3ed7e936f2954da950289e358c6b844f0935cb72 0x6c4186468168c99f64903c2751ea4bb0a24813d1
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)