HackingTechnologyInformationData ExfiltratedCustomer Data InvolvedIdentity (basic)Government IDMediumActive

IDScan.net

bd_c3c519e0fc8bdbcc · schema v1 · pii pii-v2

Severity

Medium

Discovered

Sep 1, 2026

Filed

Sep 18, 2026

To disclose

17 days

Affected

Not disclosed

Linked

5 filings

Confidence

67%

Full breach record for IDScan.net →

IDScan.net notified customers on September 4, 2026, that an unauthorized third party may have accessed and copied customer information, including full names and driver's license or other government-issued ID numbers, from its cloud accounts. The company discovered the incident on or around September 1, 2026. The investigation is ongoing. The company engaged third-party specialists, secured systems, and is cooperating with federal law enforcement. Free credit monitoring is being offered.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 17 days

Sep 1, 2026

Discovered

Sep 18, 2026

Filed

vs. sector median

9 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Oregon State AGbd_ec8a1d6e3cdbd9f02026-09-18Verified
Texas State AGbd_c3ad18e32571540b2026-09-21 · +3dVerified
Delaware State AGbd_7ab6f2e9bb61c7f42026-09-04 · +14dVerified
Massachusetts State AGbd_c32faae28fb854c92026-09-01 · +17dVerified

Name: IDScan.net
norm: idscannet

Name: IDScan.net
norm: idscannet
Industry: Technologyllm

Discovered: Sep 1, 2026
Materiality determined: —
Notification sent: Sep 4, 2026
Affected individuals: Not disclosed
Data types: Identity (basic)Government ID
Attack vector: Unknown
MITRE ATT&CK: T1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Cooperating with federal law enforcement on their investigation

During the incident: Took immediate steps to secure our systems
Engaged a team of third-party specialists to help determine the full nature and scope of the incident
Cooperating with federal law enforcement on their investigation
Reviewed our policies and procedures related to data security
Providing access to free credit monitoring and identity protection services
Changes made: Reviewed our policies and procedures related to data security
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 17 days(17 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 ↗

Massachusetts State AGSep 1 · first

Delaware State AG+3d

Oregon State AG+17d

South Carolina State AG+17d · this page

Texas State AG+20d

Pattern: first filing Sep 1 (MA), last Sep 21 (TX) — a 20-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://consumer.sc.gov/sites/consumer/files/Documents/Security%20Breach%20Notices/2026/Consumer%20Letter%20-%20IDScan.net_.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Sep 18, 2026
Raw hash: ee677909e9d586d576dc8471a18b54b606126bee3a2f783ef61cf0e66f9d8dc3

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityIDScan.net

Victim entityIDScan.net

Incidentdiscovered Sep 1, 2026

Stated responseTook immediate steps to secure our systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceconsumer.sc.gov