SecurityBreakingUnverified

Trezor says ShipMonk breach affected another 67,000 customers

The newly identified records date from 2019 to 2021 and include names, emails, phone numbers, shipping addresses, and order numbers.

What happened

The newly identified records date from 2019 to 2021 and include names, emails, phone numbers, shipping addresses, and order numbers.

Why it matters

The incident may affect operational continuity, asset safety or trust around Security. Watch for verified scope and remediation.

Affected entities

View evidence

1 reports · 1 original report · 1 independent

  1. The BlockPrimary source · Supports · EN · 100%
    Trezor says ShipMonk breach affected another 67,000 customers

Claims

  • Trezor says ShipMonk breach affected another 67,000 customers Observed

Conflicts

No material conflict detected in the available evidence.

Timeline

  1. First reported

Market move following event

Market reaction is not yet available for this asset and time window.

Score explanation

Confidence · formula confidence-2.1.0
Source trust72
Independent corroboration51
Primary evidence35
Claim consistency82
Extraction confidence82
Attribution quality90
Impact · formula impact-2.1.0
Event magnitude100
Market relevance74
Entity significance42
Market breadth45
Novelty68
Urgency100
Ranking · formula rank-1.0.0
Confidence factor0.829
Freshness factor0.9999
Breaking bonus8
Trezor says ShipMonk breach affected another 67,000 customers | IntelCap