FEDERALItem 1.05 · mandatoryHackingRetail & ConsumerRetailApparelData ExfiltratedCustomer Data InvolvedPIIIdentity (basic)CriticalContained

VF Corporation

bd_0faf1d6a18a23d60 · schema v1 · pii pii-v1

Severity

Critical

Discovered

Dec 13, 2023

Filed

Jan 18, 2024

To disclose

5 weeks

Affected

35,500,000

Linked

3 records

Confidence

90%

Full breach record for VF Corporation →3 incidents on file

VF Corporation filed an 8-K/A amending its December 18, 2023 disclosure of a cybersecurity incident detected December 13, 2023. The threat actor was ejected December 15, 2023. Preliminary investigation estimates personal data of approximately 35.5 million individual consumers was stolen. VF does not retain SSNs, bank account, or payment card data; no evidence consumer passwords were acquired. Operations have substantially recovered.

J jump to incidentP pin to compareR raw source

SEC clockMateriality determined Dec 18, 2023 → Filed Jan 18, 202431d ✗ SEC 4-day late5 weeks discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 5 weeks / 36 days

Dec 13, 2023

Begins

Dec 13, 2023

Discovered

Dec 18, 2023

Scope determined

Jan 18, 2024

Filed

vs. sector median

4 wks faster

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitealphvbd_60c72c0902ed8ec82023-12-22 · +27dVerified

Regulatory filings (1) · sorted by filing gap

SEC 8-Kbd_b9037e596ac835962023-12-18 · +31dCandidate

Name: VF Corporation
norm: vf
SEC CIK: 0000103379
Domain: vfc.com

Name: VF Corporation
norm: vf
SEC CIK: 0000103379
Domain: vfc.com
Industry: Retail & Consumerllm
NAICS 315250 · Cut and Sew Apparel Manufacturing (except Contractors)

Discovered: Dec 13, 2023
Breach occurred: Dec 13, 2023 – Dec 15, 2023
Undetected for: 0 daysoccurrence → discovery
Materiality determined: Dec 18, 2023
Notification sent: —
Affected individuals: 35,500,000nationwide
Data types: PIIIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1041 Exfiltration Over C2 Channel
Threat actor: External
Regulator citations: Notified federal law enforcementNotified relevant regulatory authorities as required under applicable law

During the incident: Immediately began taking steps to contain, assess and remediate the cyber incident
Began an investigation with leading external cybersecurity experts
Activated its incident response plan
Shut down some systems
Notified and is cooperating with federal law enforcement and relevant regulatory authorities
Ejected the threat actor from VF's IT systems on December 15, 2023
Substantially restored the IT systems and data that were impacted by the cyber incident
Will be seeking reimbursement of costs by submitting claims to VF's cybersecurity insurers
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(36 days from discovery to filing)
Compliance flags: SEC 4-day late · 31d
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Clock breakdown: Statute Window Elapsed Threshold Status
SEC
Materiality determined: Dec 18, 2023
→ Filed: Jan 18, 2024
31d cal. 4 business days SEC 4-day late

Statute	Window	Elapsed	Threshold	Status
SEC	Materiality determined: Dec 18, 2023 → Filed: Jan 18, 2024	31d cal.	4 business days	SEC 4-day late

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

SEC 8-KDec 18 · first

SEC 8-K+31d · this page

Pattern: first filing Dec 18, last Jan 18 — a 31-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 filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statementThis record

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://www.sec.gov/Archives/edgar/data/103379/000119312524010243/d641969d8ka.htm
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Jan 18, 2024
Raw hash: 046f3cc66e2f3320a4c23ae1bf75e30c87ce35ef4c9ceaad614c695841a28558

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html35.2 KB

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (1) · sorted by filing gap

Reporting entityVF Corporation

Victim entityVF Corporation

Incidentdiscovered Dec 13, 2023

Stated responseImmediately began taking steps to contain, assess and remediate the cyber incident

ComplianceSEC 4-day late

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing