MAX USA Corp.
bd_e7cf7b6edda22c76 · schema v1 · pii pii-v1
Full breach record for MAX USA Corp. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Lockbit5 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.
Sanctions caution: Lockbit5 carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
The company specializes in developing innovative and durable tools such as rebar tiers, nail guns, a...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 26, 2026
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 (1)
- Leak Sitelockbit5bd_b670437a600ae18f2026-02-15 · +21dVerified by operator
Regulatory filings (3) · sorted by filing gap
- Nebraska State AGbd_cdd2d0c79f44fe3b2026-01-15 · +11dVerified
- Massachusetts State AGbd_d7f76c6a659b0c5b2026-02-18 · +23dVerified
- New Hampshire State AGbd_751bb5530112b2992026-02-20 · +25dCandidate
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Jan 15 (NE), last Feb 20 (NH) — a 36-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.
lockbit5
According to ransomware.live, LockBit 5.0 ("ChuongDong") emerged in September 2025 as the group's resurgence following the February 2024 law enforcement takedown, introducing cross-platform payloads targeting Windows, Linux, and VMware ESXi with enhanced evasion capabilities and continuing the RaaS affiliate model of its predecessors.