HackingTechnologyInformationStolen CredentialsData ExfiltratedCustomer Data InvolvedIdentity (basic)LowContained

LS Networks

bd_e3629fa7fae63b49 · schema v1 · pii pii-v1

Severity

Low

Discovered

Apr 3, 2024

Filed

Jul 31, 2024

To disclose

17 weeks

Affected

1state residents only

Linked

5 filings

Confidence

66%

Full breach record for LS Networks →

LS Networks notified Montana residents of unauthorized access to its network on April 3, 2024. Files containing names were copied. The company shut down its network, investigated, and reported to federal law enforcement and the FCC. Affected individuals are offered identity monitoring services.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 17 weeks / 119 days

Apr 3, 2024

Begins

Apr 3, 2024

Discovered

Jul 31, 2024

Filed

vs. sector median

2 wks faster

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteplaybd_e5667db8189d9acc2024-03-26 · +127dVerified by operator

Regulatory filings (3) · sorted by filing gap

New Hampshire State AGbd_2bcd475b86365c872024-07-31Verified
Massachusetts State AGbd_fa72bdd73d5a4d672024-07-31Verified
Oregon State AGbd_fd94a8c82c6a49972024-07-31Verified

Name: LS Networks
norm: ls networks
Domain: lsnetworks.net

Name: LS Networks
norm: ls networks
Domain: lsnetworks.net
Industry: Technologyllm

Discovered: Apr 3, 2024
Breach occurred: Apr 3, 2024
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jul 31, 2024
Affected individuals: 1state-resident count only
Data types: Identity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1041 Exfiltration Over C2 Channel
Threat actor: External
Regulator citations: Reported event to federal law enforcementReported event to the Federal Communications Commission
Initial access: valid_credentials

During the incident: Shut down internal network
Conducted a thorough investigation
Engaged in a detailed review of files
Reported event to federal law enforcement
Reported event to the Federal Communications Commission
Provided access to identity monitoring services
Changes made: Implemented additional security measures within network
Completed a review of policies and procedures
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

New Hampshire State AGJul 31 · first

Massachusetts State AGJul 31 · first

Oregon State AGJul 31 · first

Montana State AGJul 31 · 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-844.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 31, 2024
Raw hash: 0e4e82b99526205b6d009d8262e5bd7913b6d758531bca8a5c830ee2fc9be7e0

Linked disclosures

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Reporting entityLS Networks

Victim entityLS Networks

Incidentdiscovered Apr 3, 2024

Stated responseShut down internal network

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov