HackingTechnologyInformationStolen CredentialsCustomer Data InvolvedPIIIdentity (basic)Financial accountCredentialsLowContained

Staminus Communications

bd_232bf6b2d7780108 · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 10, 2016

Filed

Apr 15, 2016

To disclose

5 weeks

Affected

12state residents only

Linked

3 filings

Confidence

66%

Full breach record for Staminus Communications →

Staminus Communications experienced an unauthorized network intrusion on March 10, 2016, exposing customer names, credit card numbers, usernames, passwords, and contact info. The company notified the FBI, restored systems, relaunched its billing platform, and implemented MFA. Notices were sent to affected individuals on April 15, 2016.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 5 weeks / 36 days

Mar 10, 2016

Begins

Mar 10, 2016

Discovered

Apr 15, 2016

Filed

vs. sector median

13 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 · +3dVerified
California State AGbd_fef0b3592d60ade62016-04-11 · +4dVerified

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: Apr 15, 2016
Affected individuals: 12state-resident count only
Data types: PIIIdentity (basic)Financial accountCredentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: working with the Federal Bureau of Investigation (“FBI”) in its investigation of the incident
Initial access: valid_credentials

During the incident: Launched an investigation
Notifying law enforcement
Restoring its systems
Putting additional security measures into place
Relaunched our billing platform
Implemented multi-factor authentication requirements
Taken steps to notify credit card companies
Changes made: Implemented multi-factor authentication requirements
Relaunched our billing platform
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(36 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

Massachusetts State AG+1d

Montana State AG+4d · 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://dojmt.gov/wp-content/uploads/Staminus-Communications.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 15, 2016
Raw hash: d884e65257d6ba70b4871a0a900d60a2924474dd7a13b1e522b286b210cf6251

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityStaminus Communications

Victim entityStaminus Communications

Incidentdiscovered Mar 10, 2016

Stated responseLaunched an investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov