Flocker is a relatively new ransomware group that emerged in May 2024, operating with apparent financial motivations and having compromised at least 59 known victims within a short operational timeframe. The group's origin and affiliations remain largely undocumented by major threat intelligence organizations, with no confirmed country of origin or clear operational model regarding RaaS capabilities established in public reporting. Based on available targeting data, Flocker appears to employ opportunistic attack methodologies that have successfully compromised organizations across diverse sectors including technology, public sector, financial services, and transportation/logistics, though specific technical details regarding their initial access vectors, encryption methods, or data exfiltration practices have not been publicly documented by authoritative sources. The group has demonstrated a notable geographic reach with victims identified across the United States, UAE, Taiwan, Canada, and Zambia, suggesting either broad targeting capabilities or affiliate operations, though no specific high-profile campaigns or major incidents have been publicly attributed to them by federal agencies or established security researchers. As of current reporting, Flocker appears to remain active given their recent emergence timeline, though comprehensive threat intelligence regarding their operations remains limited in open-source reporting from authoritative cybersecurity organizations. The group has been linked to 59 public disclosures across our corpus. First observed on a leak site on May 3, 2024; most recent post July 31, 2025. The operation is currently inactive.
Sector and geography
This disclosure adds to ransomware activity in the Technology sector, which has 3,549 disclosures indexed across all operators we track. Geographically, Q***M is reported in United States, a country with 11,033 ransomware disclosures in our corpus.
If your organisation is affected
A listing by Flocker means Q***M 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, CISA (United States), as required for your jurisdiction.
- Monitor for the data appearing on Flocker'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.
