MalwareRansomwareRansom DemandedCustomer Data InvolvedPIIIdentity (basic)Government IDMediumContained

Carpenter Co.

bd_446b8e72df69c9b3 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Mar 18, 2021

Filed

Jul 27, 2021

To disclose

19 weeks

Affected

4state residents only

Linked

5 filings

Confidence

66%

Full breach record for Carpenter Co. →2 incidents on file

Carpenter Co. experienced a ransomware incident on March 18, 2021, impacting IT systems. The company did not pay the ransom. Forensic investigation confirmed unauthorized access to employees' and contractors' personal information. Response actions included law enforcement notification, system containment, and forensic investigation. Remediation included enhanced network monitoring and active directory hardening. Identity monitoring services were offered to affected individuals.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 19 weeks / 131 days

Mar 18, 2021

Begins

Mar 18, 2021

Discovered

Jul 27, 2021

Filed

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Indiana State AGbd_d19122e30db7711c2021-07-28 · +1dVerified
New Hampshire State AGbd_87407076f951eb8b2021-07-29 · +2dVerified
California State AGbd_4e3bd9c6373123282021-09-11 · +46dVerified
Maine State AGbd_c6353158144d1d182021-09-11 · +46dVerified by operator

Name: Carpenter Co.
norm: carpenter
Domain: carpenter.com

Name: Carpenter Co.
norm: carpenter
Domain: carpenter.com

Discovered: Mar 18, 2021
Breach occurred: Mar 18, 2021
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 4state-resident count only
Data types: PIIIdentity (basic)Government ID
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: notifying law enforcement
Initial access: valid_credentials

During the incident: Notifying law enforcement
Locking out the unauthorized users from the Company’s system
Containing and removing the malware from the Company’s system
Undertaking a full forensic investigation of the incident with the assistance of an outside forensics investigation firm
Conducting a comprehensive information security assessment
Changes made: Adding network monitoring at internet egress points
Implementing active directory hardening measures
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Montana State AGJul 27 · first · this page

Indiana State AG+1d

New Hampshire State AG+2d

California State AG+46d

Maine State AG+46d

Pattern: first filing Jul 27 (MT), last Sep 11 (ME) — a 46-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.

Source URL: https://dojmt.gov/wp-content/uploads/OCP/a-notif-115.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 27, 2021
Raw hash: 900701d11ffbf96ee101ac4f2b65a9713aa00d5483db9b1db9b1edf85ab71781

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityCarpenter Co.

Victim entityCarpenter Co.

Incidentdiscovered Mar 18, 2021

Stated responseNotifying law enforcement

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov