Skip to content
Cyber Threat
CTI Academy Sponsor CTI Academy
Ransomware victim

Dian

Listed by Medusalocker on · organisation based in Colombia

dian.gov.co

Disclosed
Nov 4, 2026
Leak-site listing date
Threat group
Medusalocker
95 victims listed
Country
Colombia
#26 most targeted
Sector
Not recorded

ThreatAI analysis

Compiled from this incident record and the threat intelligence profile for Medusalocker. Figures and technique mappings are quoted from the source data, not inferred.

About the Medusalocker group

Medusa is a DDoS bot written in .NET 2.0. In its current incarnation its C&C protocol is based on HTTP, while its predecessor made use of IRC. Medusalocker has listed 103 victims since November 2021.

How Medusalocker is documented to operate

Parent PID Spoofing T1134.004 Stealth Privilege Escalation

Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. New processes are typically spawned directly from their parent, or calling, process unless explicitly specified. One way of explicitly assigning the PPID of a new process is via the <codeCreateProcess</code API call, which supports a parameter that defines the PPID to use. This functionality is used by Windows features such as User Account Control (UAC) to correctly set the PPID after a requested elevated process is spawned by SYSTEM (typically via <codesvchost.exe</code or <codeconsent.exe</code) rather than the current user context.

MITRE ATT&CK reference

MITRE ATT&CK techniques attributed to Medusalocker across its recorded activity, not a finding about how Dian was reached.

Incident analysis

Dian was listed by Medusalocker ransomware, a group with 95 victims recorded in this database. The listing appeared on the group's leak site on November 4, 2026.

Dian is based in Colombia. Colombia ranks #26 worldwide for ransomware disclosures, with 147 victims in this database.

Medusalocker typically follows a double extortion model: data is exfiltrated from the victim's systems before files are encrypted, so the victim faces two demands at once — pay to restore access, and pay to keep stolen data unpublished. The leak site, where this listing appeared, is the lever for the second demand.

Source. Public leak-site disclosures aggregated via the ransomware.live API. The disclosure date is when the listing was published, which can differ from the date of compromise. This site does not publish or link to stolen data. Last updated .

Frequently asked questions

Was Dian attacked by ransomware?

Yes. Dian was listed as a victim of the Medusalocker ransomware group on November 4, 2026. The organisation is based in Colombia. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked Dian?

Dian was attacked by Medusalocker ransomware. Medusalocker is one of the most active ransomware groups, having claimed 95 victims globally. The group typically employs a double-extortion model: encrypting the victim's files and threatening to publish stolen data.

When did the Dian ransomware attack occur?

The ransomware attack on Dian was disclosed on November 4, 2026. This date reflects when the victim was published on the threat group's leak site, which may differ from the actual date of initial compromise.

What data was stolen in the Dian ransomware attack?

The specific data stolen from Dian has not been independently verified by this platform. Ransomware groups typically exfiltrate data before encrypting systems and use the threat of publication to pressure victims. Sensitive business data was likely targeted.

How can organisations protect against Medusalocker attacks?

To defend against Medusalocker and similar threat actors, organisations should: maintain regular offline backups tested for restoration; implement network segmentation to limit lateral movement; deploy multi-factor authentication on all remote access; use endpoint detection and response (EDR) tools; conduct regular phishing and security awareness training; and monitor threat intelligence feeds for indicators of compromise (IOCs) associated with active groups.