Durvet — alleged breach
Clustered 2 filings across 1 jurisdiction · filing window Oct 17, 2025 → Nov 5, 2025. View entity profile → Other incidents for this victim →
incident inc_ea76e73893324b4c · merged by deterministic · confidence 100%
Unverified threat-actor claim — not a regulatory filing
Attribution, victim identity, and counts shown here derive from qilin'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.
Litigation Timing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Member cascade — every filing about this breach
- OCT 17Leak siteqilin postfirst filing · attacker claim · unverifiedauto-linkedday 0
- NOV 5Leak siteqilin postmost recent · attacker claim · unverifiedauto-linked+19d
- Watching: SEC 8-K · state-AG notices · victim statement. Median claim → filing gap is 75 days (day 306 of watch).
Roll-up facts
- Breach window
- —
- Discovered
- —
- Affected
- —
- Data types
- —
- Threat actor
- Qilin (self-attributed)
Empty by design — an unverified claim can't establish these.
If this claim is true — what to expect
- ~75dMedian claim → filing gap for Qilin's claims that DID corroborate — how fast confirmation arrives when it arrives, not how likely it is. A filing merges here automatically and upgrades this page.
- 3%Share of Qilin's claims later corroborated by a regulatory filing (1,540 tracked, 365-day window). Most claims are never corroborated — this page stays an unverified claim until one is.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
No regulator filing linked yet.
No SEC filing or victim statement yet.
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.