Skip to main content

VictimsDISCOLABINDU

DISCOLABINDU

claimed by IncransomFrancehigh · Confirmed exfiltration and publication of cl…
What this is

A claim by the operator that it has published the data.

No statement from the organisation is on record here. We index the listing; we never host the data.

Corroboration
not recorded

This row predates provenance tracking; the next feed run will stamp it.

Timeline
  1. Listed · Jun 11, 2026
  2. Data published · date unknown: the post does not say
Leak-post captureJun 11, 2026post text missingscreenshot missingverified missing
No screenshot on file. This row comes from a tracker listing; our crawler has not captured the page yet.
Posthttp://incblog6qu4y4m…onion/blog/disclosures/6a2a7bbf5ae71db30c1d4136
What the operator wrote
Unauthorized access has been gained to the company's confidential files, including client data, proprietary R&D, and financial documentation.

From the feed's summary of the post; we hold no capture of our own yet.

Size claimed
unknown
the post states no size
Records claimed
unknown
the post states no count
Ransom · deadline
not stated
we show unknown, never zero
Data the operator says was taken
client dataproprietary R&D documentationfinancial documentation

Extracted from the post text by the enrichment model; each item traces to a sentence in the capture.

Attack summary

The incransom group claims to have gained unauthorized access to the company's confidential files, including client data, proprietary R&D, and financial documentation. Data has been published.

Severity high: Confirmed exfiltration and publication of client data, proprietary R&D, and financial documentation represents significant business data exposure. The absence of a clearnet site and lack of proof file details prevent classification as critical, but the stated scope of sensitive data warrants high severity.

If this is your organisation
  1. Assume credentials were taken even where the post names none: reset, revoke sessions, enforce a second factor.
  2. Open the incident with CERT-FR and your regulator before data is published, not after.
  3. Watch the listing: a tracked domain is re-checked against every new post and you are paged when this one changes status or another operator names the organisation.

Method: the row comes from the operator's post, listed by an independent tracker and checked against our own Tor capture of the leak site. We publish the listing, the screenshot and the claim text; we do not download, host or redistribute leaked data. A post that changes is re-captured and this page updates.

Updated 4 months ago

Disclosure context

About Incransom

Incransom is a ransomware group that emerged in August 2023, operating with primarily financial motivations as evidenced by their targeting of high-value sectors across multiple developed nations. The group's origin and specific affiliations remain undocumented by major threat intelligence organizations, though their operational patterns suggest they likely operate independently rather than as a ransomware-as-a-service model. With 734 documented victims, Incransom has demonstrated a preference for targeting organizations in the United States, Canada, United Kingdom, Germany, and Australia, with particular focus on healthcare, technology, business services, and manufacturing sectors, though their attack methodology and specific technical capabilities have not been extensively documented by established security researchers or government agencies. The group's notable campaigns and specific high-profile victims have not been publicly detailed by CISA, FBI, Mandiant, or other reputable threat intelligence sources, suggesting either operational security effectiveness or limited visibility into their most significant operations. Based on available intelligence, Incransom appears to remain active as of recent reporting periods, though comprehensive analysis of their current operational status requires additional documentation from established threat intelligence sources. The group has been linked to 1,829 public disclosures across our corpus. First observed on a leak site on September 9, 2021; most recent post October 14, 2026. The operation is currently active.

Also tracked as: inc ransom, INC.

Timeline of this disclosure

  • June 11, 2026DISCOLABINDU listed by Incransom on the group's public leak site

Sector and geography

Geographically, DISCOLABINDU is reported in France, a country with 243 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Incransom means DISCOLABINDU 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, CERT-FR (France), as required for your jurisdiction.
  • Monitor for the data appearing on Incransom'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, recording every new disclosure and the moment the operator says the data was released. Each entry on this page is sourced from the operator's own publication, listed by an independent tracker (RansomLook) and checked against our own capture. 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.

DISCOLABINDU data breach — Incransom ransomware leak (2026) · Darkfield