Superior
bd_8b89c526e9eed9c6 · schema v1 · pii pii-v2
Full breach record for Superior →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Storm 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
Superior Ag is a cooperative that provides a range of agricultural services and products, including agronomy, livestock nutrition, grain marketing, and energy solutions. Established from the merger of local cooperatives, it serves farmers in southwestern Indiana, northern and central Kentucky, and parts of Illinois. The company focuses on enhancing food production and supporting its member-customers through expert insights and tailored services. With a commitment to community and member success, Superior Ag emphasizes quality and safety in all its operations. The company headquarters is located in 901 N Main Street, PO Box 420, Huntingburg, IN 47542, United States. 51-200 Employees
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 1, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
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.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
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.