DisclosureLens
GLOBALMalwareManufacturingManufacturingRansomwareFogRansom DemandedActor NamedMedium

Apache Mills, Inc. (apachemills.com)

bd_88335360b6fa6e18 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Oct 24, 2024

To disclose

—

Affected

Not disclosed

Linked

2 filings

Confidence

50%
Full breach record for Apache Mills, Inc. (apachemills.com) →

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Fog on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: ManufacturingDiscovered: 2024-10-24
View aggregator listing on ransomware.liveView merged incident timeline

Source: Ransomware.live

Post text · scraped from the leak site

27 GB

Incident timeline — mostly unverified

? — ?

Breach window unknown

Oct 24, 2024

Claim posted

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Claim → filing

—

Compliance clock

Not assessable

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Filing propagation · 2 filings

View merged incident ↗
Leak SiteOct 24 · first · this page
Maryland State AG+130d

Pattern: first filing Oct 24, last Mar 3 (MD) — a 130-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claimThis record

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 statement

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

Source ceiling

  • actor name
  • victim claim
  • ransom/leak status
  • discovery date
  • materiality
  • notification
  • affected count
  • confirmed data types
  • compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.

About this groupFirst seen 2021-12-20

fog

According to ransomware.live, Fog, which uses the .flocked extension for encrypted files, was first observed in May in campaigns by Storm-0844, a threat actor known for distributing Akira. By June, Storm-0844 was deploying Fog more than Akira.

189 victims claimed globally189 tracked hereFull profile →