0xf2e3cdd90b8d1011852ec84abad1e52d1a6ea98b
General Analysis Summary for 0xf2e3cdd90b8d1011852ec84abad1e52d1a6ea98b
Risk Level: Very High Risk Score: 100/100 Total Issues Identified: 38 Suspicious Transactions: 10
Key Findings: - Automated analysis detected 10 suspicious transactions - Risk assessment indicates very high risk level - 38 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 |
---|---|---|---|
0xcfada95…
|
50
High
|
Low transaction fee
Large transaction amount
Transaction amount doubled compared to previous transaction
Short time frame between transactions
Anomaly detected by Isolation Forest
Very short time between transactions
Transaction amount significantly higher than average
|
No tags
|
0x1d113b8…
|
30
Medium
|
Low transaction fee
Transaction amount significantly lower than average
Short time frame between transactions
Very short time between transactions
Transaction amount halved compared to previous transaction
High frequency transactions (less than 1 minute interval)
|
No tags
|
0x5243b64…
|
43
High
|
Low transaction fee
Transaction amount significantly lower than average
Part of coordinated wallet cluster
Short time frame between transactions
Very short time between transactions
Transaction amount halved compared to previous transaction
|
No tags
|
0x3da2b11…
|
42
High
|
Low transaction fee
Transaction amount significantly lower than average
Transaction amount doubled compared to previous transaction
Part of coordinated wallet cluster
Short time frame between transactions
Very short time between transactions
|
No tags
|
0x021d129…
|
40
High
|
Low transaction fee
Transaction amount significantly lower than average
Part of coordinated wallet cluster
Short time frame between transactions
Very short time between transactions
Repetitive transaction amount
|
No tags
|
0x9351ed9…
|
100
High
|
Low transaction fee
Large transaction amount
High frequency transactions (less than 1 minute interval)
Transaction involves DeFi exploit address: Bybit Exploiter 31
Anomaly detected by Isolation Forest
Related to 119 high-risk transactions (highest score: 100)
Very short time between transactions
Receives funds from exploit address: 0xcd1a4a...
Transaction amount significantly higher than average
Transaction amount significantly higher than user average
|
No tags
|
0x06aa26a…
|
85
High
|
Low transaction fee
Large transaction amount
Round amount consistent with mixer
Short time frame between transactions
Anomaly detected by Isolation Forest
Very short time between transactions
Transaction amount halved compared to previous transaction
|
No tags
|
0x0632dd7…
|
50
High
|
Low transaction fee
Transaction amount significantly lower than average
Regular interval transactions between the same wallets
Part of coordinated wallet cluster
Short time frame between transactions
Very short time between transactions
Transaction amount halved compared to previous transaction
|
No tags
|
0xa58689d…
|
50
High
|
Low transaction fee
Large transaction amount
Transaction amount doubled compared to previous transaction
Short time frame between transactions
Anomaly detected by Isolation Forest
Very short time between transactions
Transaction amount significantly higher than average
|
No tags
|
0xccef832…
|
43
High
|
Low transaction fee
Transaction amount significantly lower than average
Part of coordinated wallet cluster
Short time frame between transactions
Very short time between transactions
Transaction amount halved compared to previous transaction
|
No tags
|
Primary Analyst: Cladious Auto
Email: [email protected]
Generated: 2025-07-16 01:18:59 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.