CredScore Defensible Verdict Report
Verdict on 0x67c4…5bbd ethereum
0x67c457ed0b7ddfcb141714199cd6ce30d56c5bbd
Verdict
Score
67/100
0 = maximum risk · 100 = clean
Tier
Medium
Decision posture
Review
Confidence
66%
Moderate — treat as directional
Review before proceeding
Executive summary
CredScore sees a 6.0-year-old wallet with 69 transfers. Review-sensitive fan-out distribution pattern and Balance unavailable warrant manual review before this case is treated as routine. Observed entity context: USDT Token, tether.
Wallet snapshot at analysis time
Transfers observed: 69
Wallet age: 6.0 years (2186 days)
Last activity: 1023 days ago
Unique counterparties: 28
Sanctions exposure count: 0
Mixer-like interactions: 0
Bridge-like interactions: 0
Primary risk drivers
- Review-sensitive fan-out distribution patternmedium
- Transfers observed: 69
- Unique counterparties: 28
- Top counterparty share: 49%
A review-sensitive fan-out distribution pattern was detected. The structural heuristics indicate this wallet distributes funds to multiple distinct recipients in a compressed fashion that raises review priority when combined with other signals.
- Balance unavailablemedium
- Native balance: Unknown
Missing core metrics reduce confidence and increase the chance of misclassification.
- Rapid outflow patternmedium
- Rapid outbound events observed: 18
Rapid outflow behavior can indicate routing, distribution, or non-routine operational flow that deserves review.
Offsetting factors considered
- Established history. Wallet age: 6.0y (observed)
- Observable activity present. Transfers observed: 69
- Moderately distributed counterparties. Unique counterparties observed: 28
Sensitivity — what would change this verdict
- Fresh activity could change this classification because the current signal is not recent.
- Improved data coverage for missing core metrics would likely improve confidence and may affect the trust score.
- Off-chain context would be particularly valuable here, the detected structural patterns raise interpretive ambiguity that on-chain data alone cannot resolve.
- The dormancy-reactivation pattern warrants direct inquiry, understanding what triggered resumed activity would substantially clarify the current behavioral picture.
Observed entity / protocol context
USDT Tokentether
Analyst notes
Loading…
Analyst notes
[no analyst notes added]