SECURITY GAP DETECTED: 0x95cde3c5e1ddda2c75e7d07dc25b8657a0dba0c5 :: Detailed Report: Debug Interface Security Gap
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-08613FD5B1DB
|
Infrastructure Scan
ADDRESS: 0x95cde3c5e1ddda2c75e7d07dc25b8657a0dba0c5
DEPLOYED: 2026-05-14 07:31:11
LAST_TX: 2026-05-14 08:36:23
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Active_Trace_Protocol
VISIBILITY: ADMIN_ACCESS_VULNERABILITY
|
|
◈ OWNER_PRIVILEGE_EXPOSURE
An active debugging interface allows any user to execute onlyOwner functions.
Deactivate access mode immediately! |
> Execution_Trace_Log
[SYSTEM] System integrity check: 100% OK. Initializing scan. [NET] Latency: 25ms. Protocol: JSON-RPC 2.0. [FETCH] Received 11 segments of contract data. [SCAN] Running static analysis on JUMP instructions… [MEM] Gas profile: Opcode ‘SSTORE’ cost analysis started. [VULN] Potential ‘Dos with Gas Limit’ in loops found. [SIM] Simulation completed. No state corruption detected. [TRACE] Internal log: ‘OwnershipTransferred’ event emitted. [VALID] No critical memory leaks during simulation. [DONE] Triada-Engine standby mode. Load: 6%.
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0x2bb3fe2582a34a838d2c2dbfc31fe8b2f26ca943 0xc3fd725fc0ff620dcd40c4ebdd96ef529eafe9bc 0x66df283aa87a5cf0e40738357a09c2d0fc88bd93 0x2022678dbe71315ac17e950e3374f0bfc9898698 0x7e33aceeceb78396fe2c797f4947ba0c8f836592 0xfd08e12abf39472c5a683d3f5cd032e2fe99582c 0x02de753ad667eb937de2bf1437b5c399f21d9356 0x576d3bec47e1673aec8676dcef49fea49b372f50 0xcd43b2b6fed6373b603da7595a3cd43832dedbc7 0xa29bb7cd71fae392cbb9ad813b4f85b698388e97 0x3687419c57c1920e64876b327364340bdbf8ffa2 0x240226730cd8e64786bf2f5cef32a803917a8fa1 0x210f09b83b63f04d59d3ca9fec6cab2ec575f194 0xd64f16c6a169a44090225bd8eed3449c9cc1a86f 0xa5633a903c42eff87e280bfd18aa35069e6d27ba 0xe2d3ff36a2841f084f2dc2d8e445638f258574a6 0x8c4f064fbf9f2854ed632fd2154411a2805ffa9c 0xfde5899d703f964e3cea22327ce3e75fd6e1be35 0x6e4dc70383eb3e03048116797f4b945ebcab933e 0x2e02e7bbf639fe19ace6c37daab3299e67db18f9
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)