AB InBev was listed on 25 October 2026 by the emperador ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). emperador listed 27 organizations that month and 63 in total.
- Listed 24 days ago.
- 1147 organizations were listed by all groups in October 2026, see the month.
- 26 in Agriculture and Food Production that month.
- 4 in BE that month.
Updated 2026-11-15 09:20 UTC. Data: public leak-site listings. How we work.
AB InBev
Threat Group Post & Evidence
- Listed by
- Emperador 63 listings in total
The listing states no data size and no ransom demand.
Dark Web Leak Proof Screenshot
Original Source (Safe Tor Stream)The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
AB InBev is the world's largest brewer, headquartered in Belgium, known for Budweiser, Corona, and Stella Artois . We hold 329,244 AB InBev social-listening alerts, 2,510 corporate emails across all subsidiaries, 19K access logs, GBS portal records, internal PKI certificates, and 3.2GB of Azure blob assets. Our demand is $1,000,000 in BTC. [Sector: Retail, Manufacturing]
Amounts as written
- 3.2GB
Kinds of data mentioned
-
Email and communications
“We hold 329,244 AB InBev social-listening alerts, 2,510 corporate emails across all subsidiaries, 19K access logs, GBS portal records, internal PKI certificates, and…”
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with AB InBev (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask AB InBev directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what AB InBev can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: email and communications.
Within 30 days
- Keep watching AB InBev A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are AB InBev
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: email and communications.
Within 3 days
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 3.2GB. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties EU/EEA: GDPR Art. 33 and 34 require notifying the supervisory authority within 72 hours of becoming aware of a personal data breach, and affected people where risk is high. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Belgium.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Agriculture and Food Production organizations and ask them whether they were affected. Why: emperador listed 2 other Agriculture and Food Production organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
48/100 • GUARDEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.