DisclosureLens
State AGConfirmed1 filing · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Incident · single filing

Oxford Investment Group

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

Determination

Confirmed

Members

1 filing

States

1

Affected · reported

1

First → last filing

Apr 2, 2024

incident inc_869dc5b7a8f14949 · merged by deterministic

Confirmed breach. The filing describes a phishing attack. Discovered Jan 8, 2024 — the first regulatory filing landed 85 days later. 1 individual reported across the linked filings. Data reported: Identity (basic).

Litigation Timing

Notification delay
85days

Discovered → first regulatory filing

Not recorded for this incident

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

Incident timeline

? — ?breach window unknown
Jan 8, 2024discovered
notification delay · 85 days
Apr 2, 2024first & only filing
watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. APR 2NH AGNH AG noticeonly filing · 1 NH residentsday 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Discovered
Jan 8, 2024
NH AG
Data types
Identity (basic)
NH AG
Attack vector
Phishing
NH AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

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

SEC 8-K / victim statement

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.