Tricon Energy
bd_8e5106be1d15d53e · schema v1 · pii pii-v1
Full breach record for Tricon Energy →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Lynx 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
TRICON is an international trader and marketer for main petrochemicals, essential as building blocks for the finished products.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 29, 2024
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Indiana State AGbd_d07d399f19d5d2c82024-11-06 · +38dVerified by operator
- Massachusetts State AGbd_f80ee504f10c039c2024-12-06 · +68dVerified by operator
- Texas State AGbd_983f0c8cbf79401b2026-03-25 · +542dVerified
Filing propagation · 3 filings · 3 states
View merged incident ↗Pattern: first filing Nov 6 (IN), last Mar 25 (TX) — a 504-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.
lynx
According to ransomware.live, Lynx is a ransomware-as-a-service operation that emerged in mid-2024 as a rebrand of INC Ransomware (whose source code was sold for $300,000 on the RAMP forum), claiming ~300 victims across manufacturing, business services, technology, and transportation with an 80/20 profit split for affiliates.