Monmouth University
bd_2f9fdb38c91c7c57 · schema v1 · pii pii-v1
Full breach record for Monmouth University →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Pear on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Private university in West Long Branch, New Jersey
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 3, 2026
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Indiana State AGbd_290d4b16e85c0f262026-06-30 · +119dCandidate
- Massachusetts State AGbd_2f2dd8dfe15aba322026-06-30 · +119dVerified
- Texas State AGbd_a0056bdb614e9c6a2026-07-01 · +120dVerified
- Vermont State AGbd_50e8a470276273932026-08-20 · +170dVerified
Show 6 more filings ↓Show fewer ↑up to 239d gap
- New Hampshire State AGbd_c1c62b4ab698afae2026-08-20 · +170dVerified
- Texas State AGbd_ff90bafaa120991d2026-08-21 · +171dVerified
- New Hampshire State AGbd_6ac077d7b8335a232026-10-23 · +234dVerified
- Rhode Island State AGbd_9b079d13e17d34402026-10-23 · +234dVerified
- Vermont State AGbd_f1e4eecb1b18a7822026-10-26 · +237dVerified
- Texas State AGbd_a4ecdd81dea4e1732026-10-28 · +239dVerified
Showing first 10 of 16 linked disclosures.
Filing propagation · 10 filings · 6 states
View merged incident ↗Pattern: first filing Jun 30 (IN), last Oct 28 (TX) — a 120-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 16 — the full spread may be wider.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
pear
According to ransomware.live, Pure Extraction And Ransom (PEAR) Team is the community of highly responsible and strictly disciplined members. We are a private team and have nothing common with any other threat actors. We've been monitoring this field for a long-long time. So, we understand all the processes and know well how it all works.