IMPROPER ACCESS LOG: Audit Log 0x10a61fad5b8b93dfe99d21c419d1a9a038406eef: Improper Debug-Mode Deactivation
ADMIN
Terminal :: Triada Ethereum Auditor v2.5
AUDIT_ID: TRD-046BE45193ED
|
Infrastructure Scan
ADDRESS: 0x10a61fad5b8b93dfe99d21c419d1a9a038406eef
DEPLOYED: 2026-05-08 11:53:11
LAST_TX: 2026-05-13 05:44:23
|
Compliance Status
STATUS:
OPEN_DEBUG_PORT EXPOSURE: Post_Deploy_Misconfig
VISIBILITY: UNFINISHED_STATE_DETECTION
|
|
◈ 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] Synchronizing with block height 24374. [FETCH] Reconstructing ABI from function selectors… [SCAN] Mapping internal logic flow and branching. [MEM] Allocating stack frame for EVM simulation… [VULN] Probing admin methods for ‘Access Control’ flaws. [SIM] Testing edge case: Zero-address transfer… [TRACE] Return data: 0x25fc4242… [VALID] Cross-checking with blacklist database… CLEAN. [DONE] Scan task 1A3695D6 finished in 41s.
|
NODE: eth-us-cluster-04
GAS_LIMIT: 21000
GAS_LIMIT: 21000
OPERATIONAL_SECURITY_SCAN_COMPLETED
0x850dd5eebf5cde04c08db12263d7a480e109aaf8 0x83e8871984d4831c6dbd773119ac39fa2cca4898 0xafd4faeeb8af384cde9ac1863405bc2af0b1755c 0x96168ec0d24437b7e7b07290723c16a29b95ec6d 0x4612005b9a81a56e44e934ab0e2985df017a6169 0x762eab0f446141229110ccae155d5549ffcead96 0xb4ee491af6c9ba6e2e16e5a1940432a0f8c621da 0xdd85f7562ee12314ec68917b343eba355f0da573 0x02de753ad667eb937de2bf1437b5c399f21d9356 0x3018e98f989f6d7a4a90f730a79f09d5e1837661 0x610a142afaa24c5930d7becb15bc0ad2ec02affe 0xed9ad5a2d333ac901fa40870b821680949822275 0x99204edd757628445012ac042fa118189e049c4b 0x919a991acacf91dbd8f258d516f9d88773336ec2 0x38b5639b3f21278f81c91c5b23e2285455307257 0x1dfde9a4ac50abdf3a708e78272be36b3fcc847f 0x8c6eace212af01c26b82e389dd74e4fa7fdfa9bd 0xa6e4c0ee2c0a79e57cec622f907f87cf1eba1d9f 0x2b30efe4f99ae424322efa5c977aae69da10b5bb 0x7b496cf1f5e4d67cfe1b953befb7e85485ad7786
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)