MCO
bd_70b5b900d98d7666 · schema v1 · pii pii-v1
Full breach record for MCO →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Fulcrumsec on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
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.
Source provenance
- Source URL
- https://www.ransomware.live/id/TUNPQGZ1bGNydW1zZWM=
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- May 1, 2026
- Raw hash
- 386c36a81ea90b0ec052bf8e89e11ec3cd37fe9ffd8ee259f7549438bfd754b3
Reporting entity
- Name
- fulcrumsec
Victim entity
- Name
- MCOnorm: mco
- Domain
- mycomplianceoffice.com
- Industry
- Financial Servicesllm
What this source establishes
- Source ceiling
- A leak-site claim can't tell us: discovery date · materiality · notification · affected count · confirmed data types · compliance clock. These stay blank until a regulatory filing or victim disclosure lands.
- Attack vector
- Ransomware· fulcrumsec
- Threat actor
- FulcrumsecExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.