HackingRetail & ConsumerRetailStolen CredentialsCustomer Data InvolvedIdentity (basic)Financial accountFinancial credentialsLowContained

Jofit

bd_304ebc9a9a2fe3fc · schema v1 · pii pii-v1

Severity

Low

Discovered

May 13, 2019

Filed

Aug 5, 2019

To disclose

12 weeks

Affected

10state residents only

Linked

4 filings

Confidence

64%

Full breach record for Jofit →2 incidents on file

JoFit, LLC notified customers of a breach involving payment card data (name, address, card number, CVV) for orders placed between Jan 18 and May 13, 2019. Suspicious activity was detected on May 13, 2019. The company engaged a security firm and enhanced website security.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 115 days

discovery → filing · 12 weeks / 84 days

Jan 18, 2019

Begins

May 13, 2019

Discovered

Aug 5, 2019

Filed

vs. sector median

+5 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

Massachusetts State AGbd_2e547b27f86d6eb62019-08-05Verified
California State AGbd_baa2d3531e2f86942019-08-05Verified
New Hampshire State AGbd_e32acc0d565222042019-08-06 · +1dVerified

Name: Jofit
norm: jofit
Domain: jofit.com

Name: Jofit
norm: jofit
Domain: jofit.com
Industry: Retail & Consumerllm

Discovered: May 13, 2019
Breach occurred: Jan 18, 2019 – May 13, 2019
Undetected for: 115 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jul 2, 2019
Affected individuals: 10state-resident count only
Data types: Identity (basic)Financial accountFinancial credentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1056 Input Capture
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Engaged a leading computer security firm to assist with the investigation
Enhanced the security measures for the website
Working with payment card networks to notify issuing banks
Changes made: Enhanced the security measures for the website
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 12 weeks(84 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 ↗

Massachusetts State AGAug 5 · first

California State AGAug 5 · first

Montana State AGAug 5 · first · this page

New Hampshire State AG+1d

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/OCP/Data-Breach-NotificationDetails9.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 5, 2019
Raw hash: 4f1b7ca58df753d179498303bdce8c1396b2a847f1ee606248f4708d60aae1a4

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityJofit

Victim entityJofit

Incidentdiscovered May 13, 2019

Stated responseEngaged a leading computer security firm to assist with the investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov