Skip to main content

Ransomware victim disclosure

All victims

UBM Group (UBM Csoport)

listed as ubm.hu · Claimed by Embargo · listed 4 months ago

300 GB
Data size
4m
Age
since listed · data leaked

Status timeline

  1. ListedMar 11, 2026
  2. Data leakeddate unknown

At a glance

Group
Embargo
Status
Data leaked
Country
Hungary
Listed on leak site
Mar 11, 2026
Data size
300 GB

About the victim

AI dossier — public-source company profile

UBM Group (UBM Csoport) is a leading Hungarian agri-industrial conglomerate founded in 1996, specialising in compound feed production, grain and oilseed trading, large-scale pig farming, and related laboratory and advisory services. It is the sole agri-industrial company listed on the Budapest Stock Exchange (BÉT) and ranks as BÉT's 8th largest company by revenue outside the financial sector. The group has been expanding internationally, including into Italy.

Industry
Agricultural Feed Manufacturing & Grain Trading
Founded
1996

Attack summary

Severity: high — 300 GB of confirmed-published data including proprietary trade secrets (recipes), contracts, and databases from a publicly listed agri-industrial company constitutes significant exfiltration of sensitive business and potentially regulated commercial data at scale.

The Embargo ransomware group claims to have exfiltrated 300 GB of sensitive data from UBM Group, including proprietary feed recipes, internal documents, contracts, and databases, and has published the data.

high

Data the group says was taken

AI dossier — extracted from the leak post
  • Proprietary feed/compound recipes
  • Internal business documents
  • Contracts
  • Databases
  • Hungarian-language corporate documents

What the group claims

The UBM Group is a leading Hungarian agricultural company, founded in 1996, specializing in the production of compound feed, the trading of feed ingredients (gr... - 300 GB (sensitive data including recipes, documents, contracts, databases) Hungarian language documents will be transl...

Sources

Source

Indexed 4 months ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About Embargo

Embargo is a ransomware group that emerged in April 2024, operating with primarily financial motivations and demonstrating a focus on high-value targets across multiple sectors. The group has been observed targeting victims predominantly in the United States, Singapore, India, and France, with particular emphasis on technology, healthcare, manufacturing, business services, and financial sectors. Given the group's recent emergence and limited public documentation from major threat intelligence sources, specific details about their country of origin, operational structure, and technical methodologies remain largely unconfirmed by established security research organizations. With 37 known victims identified since their emergence, Embargo appears to follow established ransomware operational patterns typical of financially-motivated cybercriminal groups, though comprehensive analysis of their attack vectors, encryption methods, and extortion tactics has not yet been extensively documented by major cybersecurity firms or government agencies. The group's targeting of critical infrastructure sectors including healthcare and financial services aligns with broader ransomware trends observed throughout 2024, though specific notable campaigns or high-profile attacks have not been widely reported in public threat intelligence reporting. As of current observations, Embargo appears to remain active, though the limited timeframe since their emergence and sparse public documentation makes definitive assessment of their operational status challenging without additional confirmed reporting from established threat intelligence sources. The group has been linked to 40 public disclosures across our corpus. First observed on a leak site on April 21, 2024; most recent post June 30, 2026. The operation is currently active.

Timeline of this disclosure

  • March 11, 2026ubm.hu listed by Embargoon the group's public leak site
Data size
300 GB

Sector and geography

This disclosure adds to ransomware activity in the Technology sector, which has 3,549 disclosures indexed across all operators we track. Geographically, ubm.hu is reported in Hungary, a country with 7 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Embargo means ubm.hu appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Monitor for the data appearing on Embargo's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.