DisclosureLens
HackingTechnologyInformationStolen CredentialsTargetedPIIIdentity (basic)LowContained

Renkim Corporation

bd_64c48a55181aa69b · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 3, 2025

Filed

Jun 23, 2025

To disclose

16 weeks

Affected

Not disclosed

Linked

11 filings

Confidence

66%
Full breach record for Renkim Corporation2 incidents on file

Renkim Corporation notified consumers of a data breach where suspicious network activity detected on March 3, 2025, was traced back to March 2, 2025. An unauthorized third party likely obtained personal information used for processing mailings. Renkim engaged third-party experts and notified law enforcement.

Vermont clock VT AG >45 bday16 weeks discovery → filing
unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Incident timeline

undetected · 1 days
discovery → filing · 16 weeks / 112 days

Mar 2, 2025

Begins

Mar 3, 2025

Discovered

Jun 23, 2025

Filed

vs. sector median

3 wks faster

This filing is one of 11 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (10) · sorted by filing gap

Show 6 more filingsup to 46d gap

Filing propagation · 11 filings · 11 states

View merged incident ↗

Pattern: first filing Jun 1 (IL), last Aug 8 (CA) — a 68-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.