0x5c1fdc98dacb4ea0aa8a500c2179326ddc9f468d
General Analysis Summary for 0x5c1fdc98dacb4ea0aa8a500c2179326ddc9f468d
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 |
|---|---|---|---|
0x42d3a1b…
|
100
High
|
Related to 92 high-risk transactions (highest score: 100)
Receives funds from exploit address: 0x96244d...
Large transaction amount
Transaction involves DeFi exploit address: Bybit Exploiter 32
High frequency transactions (less than 1 minute interval)
Part of suspicious wallet community
Very short time between transactions
|
No tags
|
0x2b2f1fb…
|
100
High
|
Short time frame between transactions
Anomaly detected by Isolation Forest
Low transaction fee
Part of suspicious wallet community
Related to 51 high-risk transactions (highest score: 100)
Transaction involves DeFi exploit address: Bybit Exploiter 24
Transaction amount significantly lower than average
Receives funds from exploit address: 0x51e9d8...
Transaction amount halved compared to previous transaction
|
No tags
|
0x596eff9…
|
43
High
|
Short time frame between transactions
Large transaction amount
Low transaction fee
Part of suspicious wallet community
Transaction amount doubled compared to previous transaction
Very short time between transactions
|
No tags
|
Primary Analyst: Cladious Auto
Email: [email protected]
Generated: 2025-07-14 05:04:26 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.