UnitedLex Corporation
bd_94b8e14fe4dfd9d5 · schema v1 · pii pii-v1
Full breach record for UnitedLex Corporation →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group ALPHV / BlackCat 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
Post text · scraped from the leak site
"UnitedLex delivers unparalleled transformation for legal and business in the Digital Age. We are committed to excellence in every aspect of our client, employee, and community relationships."
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 5, 2023
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?Ransomware claims (2)
- Leak Sitedonutleaksbd_526f749b7a0343542023-04-04 · +1dVerified by operator
- Leak Sitemontibd_19ff77b27ef4e8ae2023-03-17 · +19dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Maine State AGbd_286b470919becd342023-07-12 · +98dVerified by operator
- Indiana State AGbd_5d4fc4ae16e9f3e72023-07-12 · +98dVerified
- Vermont State AGbd_cc400061f6870efc2023-07-12 · +98dVerified
- New Hampshire State AGbd_83a6575b5d02774c2023-07-17 · +103dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 106d gap
- Massachusetts State AGbd_26375dd5859c32ca2023-07-20 · +106dVerified
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Apr 5, last Jul 20 (MA) — a 106-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.
alphv
According to ransomware.live, The operators of the ALPHV/BlackCat ransomware began their activity in December 2021, making posts on Dark Web forums to promote their affiliate program, offering other actors the opportunity to engage in a 'new type of ransomware family' developed from scratch using the Rust programming language. Some clear evidence indicates that the actors behind this new ransomware are not new to cybercrime, and there were links to other affiliate programs such as DarkSide, BlackMatter, and REvil. (After several attacks against large companies, these groups faced pressure and arrests, necessitating the termination of their operations). As a security measure, the operators of ALPHV implemented the requirement for the execution of the ransomware payload by providing an 'access token,' which is supplied by the owners of the Ransomware-as-a-Service to the affiliate. This token is added to the victim's ransom note so that they can contact the threat actor responsible for encrypting the data. ALPHV affiliates employ double and triple extortion techniques, meaning the publication of the company's name on leak sites, threats of data leakage, and lastly, threats of DDoS attacks against the organization. Source: https://github.com/crocodyli/ThreatActors-TTPs