Skip to main content

Ransomware victim disclosure

All victims

Medipak Limited

listed as medipakpharma.com · Claimed by Dragonforce · listed 4 days ago

4d
Age
since listed · data leaked

Status timeline

  1. ListedJun 29, 2026
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Country
Pakistan
Listed on leak site
Jun 29, 2026

About the victim

AI dossier — public-source company profile

Medipak Limited is a Pakistani pharmaceutical manufacturer established in 1982 as the first integrated infusion solution and IV administration set manufacturing facility in Pakistan, with technical collaboration from Fresenius AG (Germany). The company produces large-volume parenterals, dialysis and irrigation solutions, IV administration sets, medical devices, ophthalmic preparations, and solid dosage pharmaceuticals for domestic and export markets.

Industry
Pharmaceutical Manufacturing & Medical Devices
Address
132/1, Quaid-e-Azam Industrial Estate, Kotlakhpat, Lahore 54700, Pakistan
Founded
1982

Attack summary

Severity: medium — Data has been published by the group (disclosed_status: data_published), indicating confirmed exfiltration; however, no specific proof files, screenshots, or data inventory details are provided in the truncated leak post, and the data types at risk remain unspecified. The target is a pharmaceutical manufacturer handling medical products and potential patient/operational records, which raises concern but lacks granular evidence of regulated PII at scale.

The dragonforce group claims to have breached Medipak Limited and published data. The post does not explicitly detail whether encryption, exfiltration, or both occurred, nor does it specify the data categories compromised.

medium

What the group claims

The Pakistani pharmaceutical company Medipak Limited (***.com) specializes in the manufacture of infusion solutions, medical devices, and pharmaceutical products.

Sources

Source

Indexed 4 days 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 Dragonforce

Dragonforce is a relatively new ransomware group that emerged in December 2023, operating with apparent financial motivations based on their targeting patterns and victim selection. The group's origin and potential affiliations remain unclear due to limited public documentation from established threat intelligence sources, though their rapid accumulation of 439 documented victims suggests either sophisticated capabilities or possible connections to existing ransomware infrastructure. Based on their targeting patterns across diverse sectors including manufacturing, business services, technology, and construction, Dragonforce appears to employ opportunistic attack methodologies, though specific initial access vectors, encryption methods, and extortion tactics have not been publicly detailed by major security firms or law enforcement agencies. The group has demonstrated a preference for targeting organizations primarily in English-speaking countries and Western Europe, with the United States, United Kingdom, Germany, Australia, and Italy representing their most frequent victim locations, suggesting possible language capabilities or geographic operational preferences. As of current reporting, Dragonforce appears to remain active given their recent emergence and ongoing victim acquisition, though the lack of detailed public analysis from major threat intelligence organizations indicates either operational security measures that have limited researcher visibility or that the group has not yet conducted sufficiently high-profile attacks to warrant extensive public documentation by CISA, FBI, or established security research firms. The group has been linked to 606 public disclosures across our corpus. First observed on a leak site on December 13, 2023; most recent post June 29, 2026. The operation is currently active.

Also tracked as: DRAGON FORCE.

Timeline of this disclosure

  • June 29, 2026medipakpharma.com listed by Dragonforceon the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Healthcare sector, which has 2,594 disclosures indexed across all operators we track. Geographically, medipakpharma.com is reported in Pakistan, a country with 9 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Dragonforce means medipakpharma.com 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 Dragonforce'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.