ULose is a ransomware group first observed in June 2026 with an assessed primary motivation of financial gain, operating against a limited but targeted victim set of five known organizations. Based on available data, the group has concentrated its operations against South Korea, with targeting patterns spanning the Financial Services, Manufacturing, and Healthcare sectors, suggesting a deliberate focus on high-value industries where operational disruption and data sensitivity may increase victim willingness to pay. Due to the group's recent emergence and limited victim count, no comprehensive public reporting from CISA, FBI, Mandiant, or equivalent threat intelligence authorities has been documented at this time, and attribution regarding country of origin, RaaS affiliation, specific tooling, or initial access vectors cannot be responsibly stated beyond what the available telemetry reflects. No notable high-profile campaigns, record ransom demands, or law enforcement actions against ULose have been publicly recorded, which is consistent with a nascent or low-volume threat actor that may be in early operational stages, deliberately maintaining a low profile, or operating beneath the threshold that typically triggers formal advisories. The group's current status remains active as of its first observed date, though its trajectory, longevity, and potential rebranding activity should be monitored given the sensitive nature of its targeted sectors. The group has been linked to 5 public disclosures across our corpus. First observed on a leak site on June 9, 2026. The operation is currently active.
Sector and geography
This disclosure adds to ransomware activity in the Financial Services sector, which has 1,192 disclosures indexed across all operators we track. Geographically, MSICapital is reported in South Korea, a country with 18 ransomware disclosures in our corpus.
If your organisation is affected
A listing by ULose means MSICapital 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.
- Report the incident to your national CERT, KrCERT/CC (South Korea), as required for your jurisdiction.
- Monitor for the data appearing on ULose'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.
