Skip to main content

Ransomware victim disclosure

All victims

MCO

Claimed by Fulcrumsec · listed 2 months ago

2m
Age
since listed · data leaked

Status timeline

  1. ListedMay 1, 2026
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Listed on leak site
May 1, 2026

About the victim

AI dossier — public-source company profile

MCO is an organization operating in the financial services sector, as classified by the threat-intel source. The acronym is highly ambiguous and shared by multiple entities across jurisdictions; no public site content was available to disambiguate. Specific details about its operations, location, or scale cannot be reliably established from the available evidence.

Industry
Financial Services

Attack summary

Severity: medium — Data is reported as published (data_published status) in a financial services context, which elevates severity above low; however, the extreme ambiguity of the victim identity, absence of any proof file count, no stated data size, and an AI-generated/uninformative leak post prevent a higher classification.

The group 'fulcrumsec' claims to have disclosed data relating to MCO, with the post status recorded as 'data_published', indicating exfiltration and publication of data. No further detail on the nature of the data or the scope of the attack is available from the truncated leak post.

medium

Original description

AI-summarised, not from the leak post

N/A The acronym "MCO" is too ambiguous to identify a specific company with confidence. Multiple organizations share this abbreviation across different industries and countries. Please provide additional context such as the full company name, industry, or country of operation to allow for an accurate and reliable description.

The leak post

captured from the group's site
FulcrumSec Browse victim listings from our recent concept campaigns: Index of /Shame Coming Soon: The Hardcoded Horror Show SLOPOCALYPSE NOW [email protected] Session: 05dc2052b7a29d8661f30cbf0ae4f2093e8c85324a16867df5dd5c24f0364d8b27 Tox: 969F8BE40B09537CD2A5038B9DA4BADE71C5F35DD666CC0D7632A6812D7AF72626D422D22540

Sources

Source

Indexed 2 months 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 fulcrumsec

FulcrumSec is a recently emerged ransomware group that was first observed in May 2026, operating with apparent financial motivations based on their targeting patterns across multiple countries and high-value sectors. Given the recency of their emergence and limited public documentation, the group's specific country of origin and potential affiliations remain unclear, though their targeting of victims across the United States, India, Netherlands, Colombia, and Japan suggests either a geographically distributed operation or deliberate international scope rather than nation-state backing. The group has demonstrated a preference for targeting technology companies, business services firms, and healthcare organizations, with 21 documented victims indicating a selective approach focused on sectors likely to yield significant ransom payments due to operational dependencies and sensitive data holdings. Their attack methodology details remain largely undocumented in public threat intelligence reports from major security firms, though their sector targeting suggests sophisticated initial access capabilities given the typically robust security postures of technology and healthcare organizations. No major high-profile campaigns or significant law enforcement actions against FulcrumSec have been publicly reported by CISA, FBI, or leading cybersecurity researchers as of available intelligence. The group appears to remain active as of the most recent observations, though the limited public intelligence on their operations suggests they may be maintaining a relatively low profile compared to more established ransomware enterprises. The group has been linked to 25 public disclosures across our corpus. First observed on a leak site on May 1, 2026; most recent post June 16, 2026. The operation is currently active.

Timeline of this disclosure

  • May 1, 2026MCO listed by fulcrumsecon the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Financial Services sector, which has 1,184 disclosures indexed across all operators we track.

If your organisation is affected

A listing by fulcrumsec means MCO 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 fulcrumsec'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.