JBS Brazil is a multinational food company primarily engaged in the production and processing of meat, including beef, poultry, and pork. It operates globally, offering a wide range of food product...
Clustered 2 filings across 1 jurisdiction · filing window Mar 5, 2026 → Apr 8, 2026. View entity profile → Other incidents for this victim →
Attribution, victim identity, and counts shown here derive from a threat actor's public extortion-blog claims, aggregated by ransomware.live. They have not been validated by the victim or any regulator. Treat them as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
incident inc_c171f88c91584d18 · merge_method llm · confidence 50%
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
all Leak Site
Earliest sighting first · deep chronology in Litigation Timeline
JBS Brazil is a multinational food company primarily engaged in the production and processing of meat, including beef, poultry, and pork. It operates globally, offering a wide range of food product...
JBS Brazil is the world's largest meat processing company, headquartered in São Paulo, Brazil. It operates in the food and agriculture industry, specializing in the processing and distribution of beef, pork, poultry, and lamb products. Founded in 1953, JBS serves customers across more than 150 countries. The company manages thousands of employees and operates numerous processing plants globally, making it a dominant force in the global protein supply chain.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.