HackingTechnologyInformationCustomer Data InvolvedIdentity (basic)Financial accountCredentialsLowActive

Staminus Communications

bd_fef0b3592d60ade6 · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 10, 2016

Filed

Apr 11, 2016

To disclose

5 weeks

Affected

Not disclosed

Linked

3 filings

Confidence

65%

Full breach record for Staminus Communications →

On March 10, 2016, Staminus Communications experienced an unauthorized intrusion into its network. The incident exposed customer names, credit card numbers, usernames, passwords, and contact information. Staminus took systems offline, launched an investigation, notified law enforcement (including the FBI), and implemented multi-factor authentication. The investigation was ongoing at the time of the notice.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 5 weeks / 32 days

Mar 10, 2016

Begins

Mar 10, 2016

Discovered

Apr 11, 2016

Filed

vs. sector median

14 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Massachusetts State AGbd_8ea0131901bca9b32016-04-12 · +1dVerified
Montana State AGbd_232bf6b2d77801082016-04-15 · +4dCandidate

Name: Staminus Communications
norm: staminus communications
Domain: staminus.net

Name: Staminus Communications
norm: staminus communications
Domain: staminus.net
Industry: Technologyllm

Discovered: Mar 10, 2016
Breach occurred: Mar 10, 2016
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Financial accountCredentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Regulator citations: Notified law enforcementContinuing to work with the Federal Bureau of Investigation (“FBI”) in its investigation of the incident

During the incident: Launched an investigation into the attack
Notified law enforcement
Restored its systems
Putting additional security measures into place to help prevent a future incident
Relaunched our billing platform, partnering with leading payment processors, Stripe and Zuora
Implemented multi-factor authentication requirements
Continuing to work with the Federal Bureau of Investigation (“FBI”) in its investigation of the incident
Taken steps to notify credit card companies of the credit card numbers that may have been accessed during this incident
Changes made: Implemented multi-factor authentication requirements
Relaunched our billing platform, partnering with leading payment processors, Stripe and Zuora
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

California State AGApr 11 · first · this page

Massachusetts State AG+1d

Montana State AG+4d

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://oag.ca.gov/ecrime/databreach/reports/sb24-60912
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 11, 2016
Raw hash: 3e568d0bc6a05de6ef8f087f2b5f4a28dac21d8a242829b0140d6ef4b8e9dbea

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityStaminus Communications

Victim entityStaminus Communications

Incidentdiscovered Mar 10, 2016

Stated responseLaunched an investigation into the attack

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov