Disclosures Claims Reports Entities Incidents Pulse

Feed live

DisclosureLens

Structured extracts of public breach disclosures — regulator filings (SEC, HHS, state AGs, EU DPAs) alongside threat-actor leak-site claims and press reports. SEC and HHS filings render inline from the originating regulator’s public record under the fair report privilege; other sources link out to the source URL. AI-extracted with full per-record audit trail (model, prompt version, confidence).

ai_assisted: true · Article 50 disclosure on every record

Product

Disclosures feed
Pulse · analytics
Entities
Breach notifications by state

Methodology

How extraction works
Confidence & review
About the bot

Trust

Security
Self-disclosure commitment
API documentation
API keys

v0.1.0 · coverage growing weekly

iRidge Inc. data breach claim (2025) — unverified leak-site allegation · DisclosureLens

All incidents View linkage analytics →

Incident · single filing

iRidge Inc.

One linked filing — more sources may join as they report · filed Feb 9, 2025. View entity profile → Other incidents for this victim →

Unverified threat-actor claim — not a regulatory filing

Attribution, victim identity, and counts shown here derive from a threat actor's public extortion-blog claims, aggregated by ransomware.live. They have not been validated by the victim or any regulator. Treat them as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Unverified claim. Posted to a leak site Feb 9, 2025 by Fog; no regulatory filing has corroborated it yet.

incident inc_12e62b6d163d4eae · merge_method deterministic

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no SEC 8-K in this cluster; needs two dated filings.

Leak SiteUnverified claimLifecycle stage 1 of 3: Unverified claimUnverified claimConfirmedEnforcedfog

Affected (total reported)

—

Data types

—

Jurisdictions

Linked filings

all Leak Site

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

GLOBALClaimed by FogFirst sighting
Posted to leak site Feb 9, 2025bd_08d8b823ae4f8344
Extract from Gitlabs: Universitatea Politehnica din Bucuresti, Maxvy Technologies Pvt, iRidge Inc.

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.