HackingTechnologyInformationData ExfiltratedCustomer Data InvolvedPIIIdentity (basic)Government IDMediumContained

LS Networks

bd_2bcd475b86365c87 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Apr 3, 2024

Filed

Jul 31, 2024

To disclose

17 weeks

Affected

Not disclosed

Linked

5 filings

Confidence

65%

Full breach record for LS Networks →

LS Networks identified suspicious activity on April 3, 2024, and discovered unauthorized copying of files from its network on or around that date. The company shut down its internal network, investigated, and completed a review of affected files on July 8, 2024. Personal information, including names, addresses, and Social Security numbers, was potentially compromised. LS Networks notified law enforcement and the FCC, implemented additional security measures, and is offering identity monitoring services to affected individuals.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >90d17 weeks discovery → filing

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

Montana State AGbd_e3629fa7fae63b492024-07-31Candidate
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: Not disclosed
Data types: PIIIdentity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1041 Exfiltration Over C2 Channel
Threat actor: External
Regulator citations: Notified federal law enforcementNotified the Federal Communications CommissionProviding written notice of this event to relevant state regulators

During the incident: Shut down our internal network to review the security of the environment
Conducted a thorough investigation of the activity
Engaged in a detailed review of these files to determine what information was present
Notified federal law enforcement
Notified the Federal Communications Commission
Implemented additional security measures within our network
Completed a review of our policies and procedures to mitigate reoccurrence
Providing access to identity monitoring services for individuals whose personal information was potentially affected
Changes made: Implemented additional security measures within our network
Completed a review of our policies and procedures to mitigate reoccurrence
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 17 weeks(119 days from discovery to filing)
Compliance flags: Leak >90d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Montana State AGJul 31 · first

Massachusetts State AGJul 31 · first

Oregon State AGJul 31 · first

New Hampshire 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://mm.nh.gov/files/uploads/doj/remote-docs/ls-networks-lightspeed-20240731.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: c1ac73bd72ca571d9f868a50f534730bd8e6d37efebf7f1c42663eb80e41484b

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 our internal network to review the security of the environment

ComplianceLeak >90d

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov