HackingRetail & ConsumerRetailStolen CredentialsTargetedData ExfiltratedFinancial accountFinancial credentialsIdentity (basic)MediumContained

PAX Labs, Inc.

bd_cdfab40ab9f0cea1 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jul 15, 2016

Filed

Aug 12, 2016

To disclose

28 days

Affected · nationwide

6,00010 in this filing

Linked

4 filings

Confidence

65%

Full breach record for PAX Labs, Inc. →

PAX Labs, Inc. notified customers of a data breach affecting approximately 6,000 individuals. Unauthorized parties gained access to cloud-based servers for PAXvapor.com and JUULvapor.com between June 25 and July 22, 2016, installing unauthorized software to steal payment card data including CVV codes. PAX detected the incident on July 15, 2016, removed the malware, engaged forensic investigators, and implemented enhanced firewall and monitoring controls. Affected individuals were offered 12 months of identity protection services.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 20 days

discovery → filing · 28 days

Jun 25, 2016

Begins

Jul 15, 2016

Discovered

Aug 12, 2016

Filed

vs. sector median

3 wks faster

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

California State AGbd_ae35c365847dec6d2016-08-12Verified
New Hampshire State AGbd_8bd1ff1a24c029ad2016-08-11 · +1dVerified
Massachusetts State AGbd_a1430bc57e4c62122016-08-11 · +1dVerified

Name: PAX Labs, Inc.
norm: pax labs

Name: PAX Labs, Inc.
norm: pax labs
Industry: Retail & Consumerllm

Discovered: Jul 15, 2016
Breach occurred: Jun 25, 2016 – Jul 22, 2016
Undetected for: 20 daysoccurrence → discovery
Materiality determined: —
Notification sent: Aug 12, 2016
Affected individuals: 6,000state + nationwide
Data types: Financial accountFinancial credentialsIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: PAX removed this software on July 15, 2016
PAX removed that same day
Working with a forensics team on this investigation
Put in place additional security measures, including more aggressive firewall rules and detailed system monitoring tools
Arranged to have AllClear ID protect your identity for 12 months at no cost to you
Retained the services of a well-respected cybersecurity firm
Changes made: More aggressive firewall rules
Detailed system monitoring tools
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 28 days(28 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 ↗

New Hampshire State AGAug 11 · first

Massachusetts State AGAug 11 · first

California State AG+1d

Montana State AG+1d · 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/PAX-Labs.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 12, 2016
Raw hash: cab1222647f0c422fa20dcdb8220d662f1f1c45a20e763e866146518a0d27d10

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityPAX Labs, Inc.

Victim entityPAX Labs, Inc.

Incidentdiscovered Jul 15, 2016

Stated responsePAX removed this software on July 15, 2016

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov