0x54acd3089ab45b88fa070fcc7bae4df81a5efba2
General Analysis Summary for 0x54acd3089ab45b88fa070fcc7bae4df81a5efba2
Risk Level: Very High Risk Score: 100/100 Total Issues Identified: 11 Suspicious Transactions: 3
Key Findings: - Automated analysis detected 3 suspicious transactions - Risk assessment indicates very high risk level - 11 total suspicious patterns identified across all algorithms - Standardized risk score: 100/100
Analysis Confidence: High (automated multi-algorithm approach) Recommendation: Immediate investigation required
| Transaction Hash | Risk Score | Risk Factors | Tags |
|---|---|---|---|
0xe8cd855…
|
100
High
|
Multiple round number transactions
Sends funds to exploit address: 0x9ef428...
High frequency transactions (less than 1 minute interval)
Low transaction fee
Part of suspicious wallet community
Transaction involves DeFi exploit address: Bybit Exploiter 40
Related to 43 high-risk transactions (highest score: 100)
Very short time between transactions
|
No tags
|
0xb7cf0e1…
|
100
High
|
Transaction involves DeFi exploit address: Bybit Exploiter 5
Multiple round number transactions
Related to 38 high-risk transactions (highest score: 100)
Sends funds to exploit address: 0xdd9007...
Low transaction fee
Part of suspicious wallet community
Repetitive transaction amount
|
No tags
|
0x91ec85e…
|
100
High
|
Related to 47 high-risk transactions (highest score: 100)
Sends funds to exploit address: 0x55cca2...
Multiple round number transactions
Low transaction fee
Part of suspicious wallet community
Repetitive transaction amount
Transaction involves DeFi exploit address: Bybit Exploiter 53
Very short time between transactions
|
No tags
|
Primary Analyst: Cladious Auto
Email: [email protected]
Generated: 2025-07-14 04:22:48 UTC
Investigation Team: Cladious Forensics Team
Case Reference: CLADIOUS-[BYBIT_HACKER_LAZARUS_ITER]-2025-001
Platform: Cladious Security Analysis Platform
For questions or additional analysis requests, please contact the investigation team.
This report contains confidential information and should be handled according to your organization's data protection policies.