0xb3beb7a93435678e53b93eb9e2a4bcf7969c749a
General Analysis Summary for 0xb3beb7a93435678e53b93eb9e2a4bcf7969c749a
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 |
---|---|---|---|
0x463240e…
|
40
High
|
Short time frame between transactions
Very short time between transactions
Transaction amount significantly lower than average
Part of suspicious wallet community
Low transaction fee
Transaction amount halved compared to previous transaction
|
No tags
|
0xcc3403c…
|
100
High
|
High frequency transactions (less than 1 minute interval)
Related to 126 high-risk transactions (highest score: 100)
Receives funds from exploit address: 0xb72334...
Very short time between transactions
Transaction amount significantly lower than average
Transaction involves DeFi exploit address: Bybit Exploiter 21
Part of suspicious wallet community
Low transaction fee
Large transaction amount
|
No tags
|
0xf6a2492…
|
100
High
|
Transaction involves DeFi exploit address: Bybit Exploiter 15
Related to 128 high-risk transactions (highest score: 100)
Receives funds from exploit address: 0x229093...
Part of suspicious wallet community
Low transaction fee
Large transaction amount
Transaction amount doubled compared to previous transaction
|
No tags
|
Primary Analyst: Cladious Auto
Email: [email protected]
Generated: 2025-07-15 16:19:34 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.