Sementes Jotabasso
bd_7e0dd191c35b4c70 · schema v1 · pii pii-v1
Full breach record for Sementes Jotabasso →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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
We have received materials whose content not only raises serious questions but could also directly affect the reputation and sustainability of Sementes Jotabasso. These documents indicate the following: 1. Large-scale financial fraud and misrepresentation of accounts. 2. Illegal logging in violation of regulatory requirements. 3. Use of toxic and potentially hazardous ingredients in products. 4. Concealment of important information from regulatory authorities and partners. 5. Internal documents and correspondence revealing the true extent of what is happening.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 15, 2025
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.