HackingRetail & ConsumerRetailVulnerability ExploitTargetedIdentity (basic)Financial accountFinancial credentialsLowContained

BLUE SPHERE CORPORATION

bd_cbf038c8ad3d9fd0 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jun 5, 2020

Filed

Oct 29, 2020

To disclose

21 weeks

Affected

10state residents only

Linked

4 filings

Confidence

66%

Full breach record for BLUE SPHERE CORPORATION →

Blue Sphere, LLC notified Montana residents of a data security incident where payment card information was acquired without authorization from its website. The company discovered the incident on June 5, 2020, and notified affected individuals on October 29, 2020. Affected data included names, emails, billing addresses, and full payment card details. Blue Sphere engaged forensic investigators and enhanced site security.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 21 weeks / 146 days

Jun 5, 2020

Discovered

Oct 29, 2020

Filed

vs. sector median

+13 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Indiana State AGbd_89f34105f481ef112020-10-29Verified
Maine State AGbd_03fda876284f781b2020-11-05 · +7dVerified
Massachusetts State AGbd_363a686f4281f23e2020-11-07 · +9dVerified

Name: BLUE SPHERE CORPORATION
norm: blue sphere

Name: BLUE SPHERE CORPORATION
norm: blue sphere
Industry: Retail & Consumerllm

Discovered: Jun 5, 2020
Materiality determined: —
Notification sent: Oct 29, 2020
Affected individuals: 10state-resident count only
Data types: Identity (basic)Financial accountFinancial credentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Initiated an investigation
Engaged a digital forensics firm to assist with the investigation
Took measures to enhance the security of the site
Changes made: Enhanced the security of the site
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 21 weeks(146 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 ↗

Indiana State AGOct 29 · first

Montana State AGOct 29 · first · this page

Maine State AG+7d

Massachusetts State AG+9d

Pattern: first filing Oct 29 (IN), last Nov 7 (MA) — a 9-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://dojmt.gov/wp-content/uploads/bluesphSamp.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Oct 29, 2020
Raw hash: 79755432eac14e8b5242dcdce7061c8ed6ba492b0d534c52a1f8ea892e1070c3

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityBLUE SPHERE CORPORATION

Victim entityBLUE SPHERE CORPORATION

Incidentdiscovered Jun 5, 2020

Stated responseInitiated an investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov