Skip to main content

Ransomware victim disclosure

All victims

Workers' Compensation Fund Control Board (WCFCB)

listed as workers.com.zm · Claimed by Babuk · listed 1 year ago

17m
Age
since listed · data leaked

Status timeline

  1. ListedJan 27, 2025
  2. Data leakeddate unknown

At a glance

Group
Babuk
Status
Data leaked
Country
Zambia
Listed on leak site
Jan 27, 2025

About the victim

AI dossier — public-source company profile

The Workers' Compensation Fund Control Board (WCFCB) is a Zambian government institution responsible for administering workers' compensation benefits and programs. It operates as a regulatory and fund-management body for workplace injury and occupational health claims in Zambia.

Industry
Government & Public Administration — Workers' Compensation

Attack summary

Severity: high — Government institution handling sensitive personal and financial data (workers' compensation claimants). Confirmed data publication by ransomware operator targeting a public authority responsible for social protection.

Babuk claims to have compromised the WCFCB's systems and published data. The leak post is minimal and does not detail the scope of exfiltration or whether encryption was deployed.

high

Data the group says was taken

AI dossier — extracted from the leak post
  • workers' compensation records
  • employee/claimant personal information
  • government administrative data

What the group claims

workers.com.zm

Sources

Source

Indexed 1 year 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 Babuk

Babuk is a ransomware group that emerged in October 2020, operating primarily for financial gain through extortion campaigns targeting organizations across multiple sectors. The group is believed to have originated from Russian-speaking cybercriminal networks and operates independently rather than as a traditional Ransomware-as-a-Service model, though they have shown willingness to collaborate with affiliates. Babuk typically gains initial access through exploitation of unpatched vulnerabilities in public-facing applications and weak remote desktop protocol credentials, employs double extortion tactics by exfiltrating sensitive data before deploying their custom encryption malware, and threatens to publish stolen information on their dedicated leak site if ransom demands are not met. The group gained significant notoriety in May 2021 when they successfully breached the Washington D.C. Metropolitan Police Department, stealing and threatening to release sensitive law enforcement data including information on criminal investigations and police personnel. Following increased law enforcement attention after the police department attack, Babuk announced in May 2021 that they were ceasing ransomware operations and would focus solely on data theft and extortion, though various security researchers have observed continued sporadic activity from the group or actors using similar tools and techniques. The group has been linked to 188 public disclosures across our corpus. First observed on a leak site on October 25, 2020; most recent post April 23, 2025. The operation is currently inactive.

Timeline of this disclosure

  • January 27, 2025workers.com.zm listed by Babukon the group's public leak site

Sector and geography

Geographically, workers.com.zm is reported in Zambia, a country with 2 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Babuk means workers.com.zm 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 Babuk'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.