DEPLOYDatabase

Incident · Regulatory action

Securities class action filed against CleanSpark alleging material misstatements about ATL Data Centers acquisition

On January 20, 2021, Scott Bishins filed a class action complaint in the Southern District of New York against CleanSpark, CEO Zachary Bradford, and CFO Lori Love, alleging the company failed to disclose that it had overstated customer and contract figures and that several acquisitions involved undisclosed related party transactions. An amended complaint filed February 28, 2022 added Matt Schultz as a defendant and alleged material misstatements about the ATL Data Centers acquisition, including that an ATL predecessor had filed for bankruptcy six months prior and that a related party had performed an audit. The case was pending a motion to dismiss as of the FY2022 10-K filing.

Occurred 2021-01-20 · CleanSpark

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track Securities class action filed against CleanSpark alleging material misstatements about ATL Data Centers acquisition

Machine-readable surfaces

Sources (1)

  1. SEC EDGAR (CleanSpark 10-K FY2022) · https://www.sec.gov/Archives/edgar/data/827876/000095017022026564/clsk-20220930.htm · 2022-12-14

Status history

  • Active · 2026-08-18 · agent:recon

Common questions

What happened in Securities class action filed against CleanSpark alleging material misstatements about ATL Data Centers acquisition?
On January 20, 2021, Scott Bishins filed a class action complaint in the Southern District of New York against CleanSpark, CEO Zachary Bradford, and CFO Lori Love, alleging the company failed to disclose that it had overstated customer and contract figures and that several acquisitions involved undisclosed related party transactions. An amended complaint filed February 28, 2022 added Matt Schultz as a defendant and alleged material misstatements about the ATL Data Centers acquisition, including that an ATL predecessor had filed for bankruptcy six months prior and that a related party had performed an audit. The case was pending a motion to dismiss as of the FY2022 10-K filing.
When did this incident occur?
The incident is recorded as occurring on January 20, 2021 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in Securities class action filed against CleanSpark alleging material misstatements about ATL Data Centers acquisition?
The incident is recorded as involving CleanSpark on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to Securities class action filed against CleanSpark alleging material misstatements about ATL Data Centers acquisition?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of Securities class action filed against CleanSpark alleging material misstatements about ATL Data Centers acquisition?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (1 primary) · last reviewed 2026-08-18

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-08-18

Sources by quality tier

1
primary-sec-filing
SEC filing

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Securities class action filed against CleanSpark alleging material misstatements about ATL Data Centers acquisition.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID d28df7de-82fe-4646-8e04-9d300968ccd8