HackingConstructionConstructionTargetedData ExfiltratedIdentity (basic)LowContained

WELBRO Building Corporation

bd_fc0ec945019c4694 · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 19, 2023

Filed

Apr 29, 2024

To disclose

23 weeks

Affected

2state residents only

Linked

5 records

Confidence

65%

Full breach record for WELBRO Building Corporation →

WELBRO Building Corporation issued a supplemental notice regarding an unauthorized network access incident. Suspicious activity was detected on November 19, 2023, covering access between November 14-19, 2023. An unknown actor accessed files containing names and other personal information. WELBRO engaged third-party cybersecurity specialists, reported the incident to federal law enforcement, and offered 12 months of credit monitoring through Epiq.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 5 days

discovery → filing · 23 weeks / 162 days

Nov 14, 2023

Begins

Nov 19, 2023

Discovered

Apr 29, 2024

Filed

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

Linked disclosures

Why this link?

Ransomware claims (2)

Leak Site8basebd_8325940a30c788862023-11-21 · +160dVerified by operator
Leak Sitedispossessorbd_a6ac6dd2f22e1b9f2023-11-21 · +160dVerified by operator

Regulatory filings (2) · sorted by filing gap

Maine State AGbd_5d16d47d722438fd2024-04-29Candidate
Massachusetts State AGbd_b69f6ba93b204ca72024-04-29Verified

Name: WELBRO Building Corporation
norm: welbro building
Domain: welbro.com

Name: WELBRO Building Corporation
norm: welbro building
Domain: welbro.com
Industry: Constructionllm

Discovered: Nov 19, 2023
Breach occurred: Nov 14, 2023 – Nov 19, 2023
Undetected for: 5 daysoccurrence → discovery
Materiality determined: —
Notification sent: Apr 29, 2024
Affected individuals: 2state-resident count only
Data types: Identity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Regulator citations: reported this incident to federal law enforcementreporting to regulatory authorities, as required

During the incident: Took steps to secure our network and minimize any disruption to our operations
Launched an investigation into the nature and scope of the incident with the assistance of third-party cybersecurity specialists
Deployment of an advanced threat protection and monitoring tool
Reviewing existing security policies and implemented additional cybersecurity measures
Reported this incident to federal law enforcement
Offered you access to three bureau credit monitoring and identity theft protection services for twelve (12) months at no cost to you, through Epiq
Changes made: Reviewing existing security policies
Implemented additional cybersecurity measures to further protect against similar incidents moving forward
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Maine State AGApr 29 · first

Massachusetts State AGApr 29 · first

Montana State AGApr 29 · first · this page

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/Consumer-notification-letter-1318.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 29, 2024
Raw hash: 6b98571348014235a7f107eb70764103345f758527066d360a879ebfb832def6

Linked disclosures

Ransomware claims (2)

Regulatory filings (2) · sorted by filing gap

Reporting entityWELBRO Building Corporation

Victim entityWELBRO Building Corporation

Incidentdiscovered Nov 19, 2023

Stated responseTook steps to secure our network and minimize any disruption to our operations

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov