HackingTechnologyInformationStolen CredentialsCustomer Data InvolvedRansom DemandedIdentity (basic)Government IDMediumActive

IDScan.net

bd_c32faae28fb854c9 · schema v1 · pii pii-v2

Severity

Medium

Discovered

Sep 1, 2026

Filed

Sep 1, 2026

To disclose

—

Affected

1state residents only

Linked

5 filings

Confidence

68%

Full breach record for IDScan.net →

IDScan.net notified Massachusetts residents on September 4, 2026, that an unauthorized third party may have accessed customer data on or around September 1, 2026. The incident involved full names and driver’s license or other government-issued identification numbers. Access required payment, suggesting a ransomware or extortion motive. The investigation is ongoing, and the company has engaged third-party specialists and is cooperating with federal law enforcement. Free credit monitoring is being offered.

J jump to incidentP pin to compareR raw source

Incident timeline

Sep 1, 2026

Begins

Sep 1, 2026

Discovered

Sep 1, 2026

Filed

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

Delaware State AGbd_7ab6f2e9bb61c7f42026-09-04 · +3dVerified
South Carolina State AGbd_c3c519e0fc8bdbcc2026-09-18 · +17dCandidate
Oregon State AGbd_ec8a1d6e3cdbd9f02026-09-18 · +17dVerified
Texas State AGbd_c3ad18e32571540b2026-09-21 · +20dVerified

Name: IDScan.net
norm: idscannet

Name: IDScan.net
norm: idscannet
Industry: Technologyllm

Discovered: Sep 1, 2026
Breach occurred: Sep 1, 2026
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Sep 4, 2026
Affected individuals: 1state-resident count only
Data types: Identity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Cooperating with federal law enforcement on their investigation
Initial access: valid_credentials

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.

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 · this page

Delaware State AG+3d

South Carolina State AG+17d

Oregon State AG+17d

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://www.mass.gov/doc/2026-1577-idscannet/download
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Sep 1, 2026
Raw hash: 5f45d9bcca93fa49204b8bd8319963311031c7dbe838f6788d630382db5aae06

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 provenancewww.mass.gov