Ransomware Group Emperador Claims 3.9 GB Data Theft from AB InBev
The ransomware group Emperador has listed AB InBev, the global brewer behind Budweiser and Corona, among its claimed victims. The post appeared on 25 October at 03:22 UTC, with the group asserting possession of 3.9 GB of internal company data and demanding a ransom of 1 million dollars in Bitcoin.
The listing details 329,244 social listening alerts, 2,510 corporate emails belonging to subsidiaries, approximately 19,000 access records, logs from an internal services portal, and certificates from the company’s public key infrastructure. The bulk of the volume—3.2 GB—is attributed to assets stored in Azure. No explanation is provided regarding the method of acquisition, and there is no mention of an exposed storage account, leaked token or key, or exploited software vulnerability.
No sample files have been released that would allow independent verification of the data’s authenticity, origin, or age. Access records and internal certificates, if genuine, could assist attackers in mapping the network and preparing lateral movement. However, the certificates contain only public keys, and the announcement does not claim that corresponding private keys were obtained.
AB InBev has issued no confirmation, denial, or comment. There are no reports of encrypted systems, operational disruption, affected products, or the number of individuals impacted. The extortion list tracker estimates the attack date as 25 October, but this does not indicate when initial access may have occurred.
Claims posted on extortion lists constitute threat intelligence rather than confirmed facts. Ransomware groups have clear incentives to exaggerate data volumes and target well-known brands to increase public pressure during negotiations. The absence of verifiable samples weakens the current assertion. Confirmation would require either a publishable sample that withstands scrutiny or an official statement from the company. Until such evidence appears, organizations integrated into AB InBev’s supply chain are advised to treat the incident as unverified and monitor official communications.
Related articles
Russian Ransomware Groups INC and The Gentlemen Deploy AI-Driven Phantom Framework for Fully Automated Attacks
SOCRadar researchers have disclosed the Phantom framework, an AI-powered autonomous ransomware attack platform operated by members linked to the INC and The Gentlemen groups. The system uses commercial large language models routed through OpenRouter to scan 7,158 edge devices, steal 535 administrator accounts, and compromise 4,140 endpoints. AI agents autonomously generate custom encryption binaries, craft personalized ransom demands based on stolen financial data, and write kernel drivers to disable EDR solutions before encryption. The framework runs on 32 custom MCP servers that give the AI direct access to scanning, credential abuse, financial analysis, and anti-detection tooling. Human operators only supply target prompts and approve final actions while the AI executes the entire kill chain. Phantom Agent v3.1 implants masquerade as Windows Update components and communicate over encrypted channels with randomized polling intervals. The discovery reveals a mature Ransomware-as-a-Service model that lowers the barrier for other criminal groups to conduct large-scale AI-automated extortion.
Creator of Ransomware Forum Ramp4u Hands Over 1.5 Billion Rubles to Russian Law Enforcement
A darknet researcher known as exkgb has published an analysis of the ransomware forum Ramp4u.io, revealing that its founder cooperated with authorities by transferring 1.5 billion rubles. The report follows the author's earlier coverage of the Exploit forum administration, which drew significant reader interest with only a 6% bounce rate. Ramp4u is described as a dedicated ransomware marketplace operating on the dark web. The article positions the forum as a key platform in the ransomware ecosystem and notes the unusual cooperation with security forces. exkgb continues to monitor and document major darknet platforms for the cybersecurity community.
Ransomware Attack on SoftBank's IDCF Cloud Encrypts 3.6PB in 7 Minutes as Operations Team Misses Alerts for 7 Hours
SoftBank subsidiary IDC Frontier suffered a ransomware attack on its IDCF Cloud East Japan Region 1 that encrypted 3.6PB of primary storage across 239 hypervisors and 225 datastores in just seven minutes. Attackers also destroyed 554,153 snapshots, eliminating 41.5PB of backup capacity and leaving 495 enterprise and government customers without recoverable data from the provider. Operations staff spent the next seven hours repeatedly rebooting already-encrypted virtual machines and resetting console passwords while failing to locate any of the 225 RECOVER-INFO.txt ransom notes left in datastore root directories. The intrusion was only confirmed after the threat actors directly defaced the vCenter management console with the message “IDCF CLOUD INFRASTRUCTURE SEIZED”. The incident highlights critical gaps in asset inventory, log monitoring, and incident response procedures rather than any zero-day exploit. No ransom was paid; the provider instead focused on public updates while advising customers to rely on their own off-site backups.
WannaCry Ransomware: How EternalBlue Turned One Infection Into a Global Epidemic
On 12 May 2017, the WannaCry ransomware worm rapidly infected more than 230,000 computers across at least 150 countries by exploiting the unpatched SMBv1 vulnerability with the EternalBlue exploit. The malware combined remote code execution via EternalBlue with file encryption and ransom demands in Bitcoin, affecting hospitals, manufacturers, and government organizations worldwide. Microsoft had released the MS17-010 patch two months earlier, yet many systems remained vulnerable due to delayed deployment in large environments. WannaCry scanned both local subnets and random public IPv4 addresses in parallel threads, allowing infected machines to autonomously discover and compromise new targets without user interaction. Security researcher Marcus Hutchins halted the initial wave by registering a hardcoded kill-switch domain, though later variants removed this check. The incident demonstrated how a known, patchable flaw combined with worm-like propagation could produce worldwide operational disruption.