Skip to main content

Ransomware victim disclosure

All victims

Indigo Group

Claimed by Secpo · listed 3 months ago

3m
Age
since listed · data leaked

Status timeline

  1. ListedApr 14, 2026
  2. Data leakeddate unknown

At a glance

Group
Secpo
Status
Data leaked
Country
Canada
Listed on leak site
Apr 14, 2026

About the victim

AI dossier — public-source company profile

Indigo Group is a Canadian company; beyond the country of registration and the name, no public site content was available to characterise its operations, sector, or scale with confidence.

Attack summary

Severity: critical — Confirmed exfiltration and publication of data affecting over 27,000 individuals (PII at scale) and 27,000 organizations across nearly 900,000 unique files; the volume and scope of personal and organizational data meets the critical threshold.

The group 'secpo' claims to have exfiltrated a dataset containing over 897,000 unique files (1,707,433 including duplicates), reportedly containing sensitive information on more than 27,000 individuals and over 27,000 organizations, with data described as published.

critical

Data the group says was taken

AI dossier — extracted from the leak post
  • PII on 27,000+ individuals
  • Records on 27,000+ organizations
  • 897,000+ unique files

What the group claims

The exposed dataset includes over 897,000 unique files (1,707,433 with duplicates) containing sensitive information on more than 27,000 individuals and over 27,000 organizations

Sources

Source

Indexed 3 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 secpo

SecPo is a ransomware group that first emerged in April 2026, operating with apparent financial motivations based on their limited documented activity. With only four known victims primarily concentrated in Canada, the group appears to target business services and manufacturing sectors, though their small operational footprint suggests they may be a nascent or highly selective threat actor. Due to the group's recent emergence and limited public documentation, details regarding their country of origin, potential affiliations, or ransomware-as-a-service model remain unclear to security researchers. Their attack methodology, encryption techniques, and specific tools have not been extensively documented by major security firms, likely due to their limited scope of operations and recent timeline of activity. No major campaigns, high-profile victims, or significant law enforcement actions have been publicly reported for this group, which aligns with their apparently small-scale operations. Given their recent emergence in 2026, SecPo's current operational status and long-term capabilities remain to be determined as security researchers continue to monitor their activities. The group has been linked to 5 public disclosures across our corpus. First observed on a leak site on April 14, 2026; most recent post April 29, 2026. The operation is currently active.

Timeline of this disclosure

  • April 14, 2026Indigo Group listed by secpoon the group's public leak site

Sector and geography

Geographically, Indigo Group is reported in Canada, a country with 314 ransomware disclosures in our corpus.

If your organisation is affected

A listing by secpo means Indigo Group 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, CCCS (Canada), as required for your jurisdiction.
  • Monitor for the data appearing on secpo'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.