TERMINATION PROTOCOL IMMINENT: 0x821f8554980ff6623c4f0343a62b3e7350b6f333 :: Debug Interface Persistence Security Report
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-D840AFCCE2E2
|
Infrastructure Scan
ADDRESS: 0x821f8554980ff6623c4f0343a62b3e7350b6f333
DEPLOYED: 2026-05-12 16:36:35
LAST_TX: 2026-05-12 16:49:47
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Dev_Maintenance_Leftover
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] Virtual Machine environment: EVM-Pallet-v9. [NET] Connection established. Peer count: 18. [FETCH] Entry point found at offset 0x2334. [SCAN] Identifying function signatures (0xc6e78622). [MEM] Initializing storage slot tracker… [VULN] Investigating ‘Unchecked low-level calls’… [SIM] Mocking MSG.SENDER as 0x38eee497d1a22dca63365c8759ef9f7ff984de6e. [TRACE] Call sequence: e1bd -> cb77 -> e598. [VALID] Security status: DEEP_CORE scan finished. $line = str_replace(‘0x38eee497d1a22dca63365c8759ef9f7ff984de6e’, ‘0x’ . bin2hex(random_bytes(20)), $line);
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0x128dae34b9b28a441e23de481f110716dc9b765e 0xd9d5a18d3b15e91c071ad3deeefde4d00edfed0e 0xfb79c5c6053b76f9b7415d408f0a3fc1037ce5c5 0x6a2933ea871fd1c7e4e7773538c312525e28a4d3 0x9b44fb8ff15edbf9d8583831be97646bfe149378 0x57bbd01ec43b748fe4744d69610d24c04214fa2e 0x52c2b42d59acead4e576f0a3852a133faa0fde98 0x367b3883ab5721b196bbf5c2127ab32fd8679fa0 0xd6f811955ff89eb14b0e0d5f058a8b30d0bf4781 0xc75cfa89a7aca209ceac7aa341e3842c9c809cd5 0xd451f8065d73bb78d17fa780823d11b256af5911 0xc4c41336e00728313bbdfc1f76980bb17939ea7d 0xfe4a1b6c5d582ccd81e54e304fb061e2e51d5427 0xe83b6f310495a399c5a7f89e15d64af66e0a59b7 0xd76798dbb384b44152e897031b0206f89f489f22 0xa80186aa8c5ef09d281c7d75cbcd0bfdda88ba3b 0x8e1d9892876862e74213bfb83b4f6db989764325 0x4c9ce4620fccf4473be55b732c0a913a513be74f 0x748ba3e7812d0c5bba9c754b9f6ee535ed2b7327 0x077005a73c00b075f3518a1a7177f22afcbcd71a
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)