FEDERALItem 8.01 · voluntaryHackingHealthcareManufacturingManufacturingMediumContained

REPLIGEN CORPORATION

bd_99074e17a936bd93 · schema v1 · pii pii-v2

Severity

Medium

Discovered

Jul 9, 2024

Filed

Jul 15, 2024

To disclose

6 days

Affected

Not disclosed

Linked

3 records

Confidence

67%

Full breach record for REPLIGEN CORPORATION →

Repligen Corporation (RGEN) filed an 8-K on July 15, 2024, disclosing that on July 9, 2024, it discovered that an unauthorized third party had accessed certain files on its information systems. The Company activated response procedures, notified law enforcement, and engaged external cybersecurity experts. The Company believes it has contained the incident, no systems were encrypted by malware, and its operations remain undisrupted; it does not anticipate a material financial impact. The full extent of the impact is under investigation.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 6 days

Jul 9, 2024

Discovered

Jul 15, 2024

Filed

vs. sector median

8 wks faster

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteinc_ransombd_329d94b6323fc8082024-07-03 · +12dCandidate

Regulatory filings (1) · sorted by filing gap

New Hampshire State AGbd_ba45402a11f9fd592025-01-06 · +175dVerified by operator

Name: REPLIGEN CORPORATION
norm: repligen
SEC CIK: 0000730272
Domain: repligen.com

Name: REPLIGEN CORPORATION
norm: repligen
SEC CIK: 0000730272
Domain: repligen.com
Industry: Healthcarenaics mapManufacturingnaics map

Discovered: Jul 9, 2024
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: —
Attack vector: Unauthorized Access
Threat actor: External

During the incident: Activated response procedures to investigate, contain, and remediate the incident
Notified law enforcement
Engaged external cybersecurity experts to assist with the investigation and other response activities
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 6 days(6 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

SEC 8-KJul 15 · first · this page

New Hampshire State AG+175d

Pattern: first filing Jul 15, last Jan 6 (NH) — a 175-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 filing

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

SEC 8-K / victim statementThis record

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

Source URL: https://www.sec.gov/Archives/edgar/data/730272/000119312524179061/d868921d8k.htm
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Jul 15, 2024
Raw hash: 9f7a1e7e8f7bf36560d68eec5f514fe5cd9308eee7c44335a7f784ae54144e2b

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html24.1 KB

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (1) · sorted by filing gap

Reporting entityREPLIGEN CORPORATION

Victim entityREPLIGEN CORPORATION

Incidentdiscovered Jul 9, 2024

Stated responseActivated response procedures to investigate, contain, and remediate the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing