The Computer Merchant, Ltd.
bd_6d00600f90f10c7c · schema v1 · pii pii-v1
Full breach record for The Computer Merchant, Ltd. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Play on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 15, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Indiana State AGbd_0bc9cb0fb948677e2025-08-19 · +400dVerified
- Vermont State AGbd_59bcb7c5698db8fd2025-08-19 · +400dVerified
- Nebraska State AGbd_6282f30064c7ed082025-08-19 · +400dVerified
- Montana State AGbd_80c1facf470aa5792025-08-20 · +401dCandidate
Show 6 more filings ↓Show fewer ↑up to 403d gap
- New Hampshire State AGbd_08dc2d6569d825102025-08-21 · +402dVerified
- Massachusetts State AGbd_29c30c22f0deaab42025-08-21 · +402dVerified
- California State AGbd_2b56afa7cd4618742025-08-21 · +402dVerified
- Washington State AGbd_785d79b5b8ebd3b32025-08-21 · +402dVerified
- Maine State AGbd_dfa81e3bb03611292025-08-21 · +402dVerified
- Texas State AGbd_09053f36a57de9092025-08-22 · +403dVerified
Showing first 10 of 11 linked disclosures.
Filing propagation · 11 filings · 10 states
View merged incident ↗Pattern: first filing Jul 15, last Aug 22 (TX) — a 403-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 11 — the full spread may be wider.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
play
According to ransomware.live, Initially observed in June 2022, the Play ransomware (a.k.a PlayCrypt) operates through double extortion, targeting numerous organizations in Latin America. Its Initial Access method is quite similar to other ransomwares, involving attacks such as Phishing, Exposed Services to the Internet, and Valid Account compromises. On April 19, 2023, the security company Symantec published two new tools developed by the Play group. These tools allow the malicious actor to enumerate and exfiltrate data from the internal network. The post mentions the following: 'Play threat actors use the .NET infostealer to enumerate software and services via WMI, WinRM, Remote Registry, and Remote Service. The malware checks for the existence of security and backup software, as well as remote administration tools and other programs, saving the information in .CSV files that are compressed into a .ZIP file for later manual exfiltration by threat actors.'Source: https://github.com/crocodyli/ThreatActors-TTPs