We manage your security to weather the AI storm →

← Resource Hub

The Delve Scandal: What Crypto Companies Should Do Now

By Owen ThurmPublished 7 min read

Part of our guide to crypto regulatory compliance

The Delve Scandal: What Crypto Companies Should Do Now

Quick answer. The Delve scandal: March 2026 allegations, denied by Delve, that its compliance platform pre-wrote auditor conclusions and fabricated evidence. If your SOC 2 or a vendor's used Delve, verify the auditor, scope and testing, and seek independent re-testing where provenance is unclear.

Watch: The Delve Scandal: What Crypto Companies Should Do Now 1:43
Video transcript

In March 2026, an anonymous former customer alleged that SOC 2 reports produced through Delve carried pre-written auditor conclusions. Delve denies it.

Delve says it is an automation platform and licensed auditors sign the opinions. It offered free re-audits and pentests, apologized on April 3, and blamed a suspected cyberattack, which is unverified.

The sources we reviewed record no final misconduct finding. The AICPA is looking into allegations about an unnamed vendor and has announced no findings.

Automation is not the problem. The risk is a tool that also drafts the auditor's conclusions, so the opinion rests on drafting, not evidence.

If your report came through Delve, do not assume it is invalid, or fine. Inventory reports, preserve evidence, confirm the CPA firm, read test results, and where provenance is unclear, commission a re-examination.

If a vendor used Delve, ask it and its auditor about independence, test period, scope and re-examination. Where answers are incomplete, require independent re-testing before renewal.

Crypto risk also sits in code, signing and custody. Keep evidence buyers can check without trusting your compliance tool: verifiable SOC 2 reports, audits tied to commit hashes, pentests with retests and key ceremony records.

Guardian does not issue SOC 2 opinions. A licensed CPA firm does. Read the full article, or talk to Guardian about assessing what your SOC 2 leaves out.

Why It Matters Now

Crypto companies lean on SOC 2 reports to open bank accounts, list on exchanges and pass vendor reviews. A report is only worth the testing behind it.

For what a SOC 2 tests in crypto at all, see what a SOC 2 covers and misses.

Where this article discusses regulation, it covers the technical and security side only. It is not legal advice; confirm how the rules apply to you with counsel.

What Happened and Delve's Response

DeepDelver, an anonymous former customer, says draft reports already contained auditor conclusions and control-test language. It also reported near-identical text across customers' reports, and evidence it called fabricated or incomplete.[1]

TechCrunch's account names two audit firms, Accorp and Gradient. Accorp says on LinkedIn that no report it issues is finalized without independent review of evidence; no Gradient response was found.[2, 3]

The sources reviewed here record no final misconduct finding. The AICPA says it is looking into anonymous allegations about an unnamed compliance vendor, and has announced no findings.[4]

Counts of affected reports come from the anonymous source and are unconfirmed, so we omit them.

Delve says it is an automation platform. It does not run audits or issue SOC 2 reports; independent licensed auditors test controls and sign the opinions.[5]

Customers can choose their own auditor or one from Delve's network, it says. Its templates are starting points that customers must review and finalize.

Delve cites more than 120 automated integrations. It says customers can see their evidence, integration test logs and control set directly.[6]

Its March 24 measures offered customers a free re-audit by an independent, peer-reviewed, AICPA-accredited SOC 2 auditor and a free grey-box pentest. Delve also offered engagement letters, direct auditor communication and template labels.

On April 3, Delve apologized, saying it fell short of its standards while scaling. It said it was rebuilding its auditor network and halting automation that interacts with audit workflows.[7]

Delve blamed the disclosures on a suspected coordinated cyberattack, and told TechCrunch an attacker exfiltrated an audit-tracking spreadsheet. That is Delve's explanation, not a verified finding.[8]

On April 21, a proposed class action over a Mercor data breach named Delve AI, Inc. and LiteLLM's operator among its defendants. It alleges Delve misrepresented whether clients met security standards.[9]

Those are plaintiffs' allegations, not findings. The July 20, 2026 order staying the consolidated Mercor cases for mediation names Mercor as the only defendant; we could not confirm whether Delve remains a party.[10]

  • March 19: DeepDelver published its allegations on Substack.
  • March 20 and 22: Delve published its response; TechCrunch reported the allegations and denial.
  • April 4: TechCrunch reported that Delve and Y Combinator had parted ways.
  • April 13: AICPA ethics staff published guidance on auditors' business arrangements with SOC tool providers.[11]
  • April 21: A proposed class action over the Mercor breach named Delve AI, Inc. as a defendant.
  • April 23: TechCrunch reported Context AI moved to Vanta and engaged Insight Assurance for new examinations.[12]
  • May 14: AICPA's peer review director described a reviewer alert on SOC 2 risks.[13]
  • September 11: AICPA dated TQA Section 9561, on AI in SOC examinations.[14]

Why AI-Generated Evidence Worries Buyers

A SOC 2 Type 2 has distinct parts. Management gives the system description and its assertion; the service auditor gives the opinion, the control tests and the results.[15]

Buyers trust the results because someone independent of management produced them. If results exist before testing, the opinion rests on drafting, not evidence.

Automation is not the problem. Delve described AI that matches screenshots to controls, daily testing that catches drift, and human review before the auditor starts.[16]

AICPA's TQA Section 9561, dated September 11, 2026, addresses how a service organization's use of AI affects SOC 1 and SOC 2 examinations.[14]

TQAs are nonauthoritative guidance, not new standards.[17]

The risk is a tool that collects evidence and also drafts what the auditor concludes. Shared templates save time; identical conclusions across companies suggest the testing was not tailored to each one.

GAO's June 2026 Financial Audit Manual gives federal auditors a Type 2 report assessment tool. It checks the service auditor's independence and competence, the period, scope, exceptions and whether evidence is sufficient.[18]

Buyers can borrow the same checks.

The AICPA's April 2026 ethics staff guidance warns that auditor deals with SOC tool providers can create undue influence and self-interest threats. It is nonauthoritative; the Code still governs.[11, 19]

It flags reciprocal or exclusive referrals, provider participation in examinations, and provider deadlines that override auditor judgment. If a third party sets the examination fee, independence is impaired.

An AICPA peer review alert issued in May 2026 directs reviewers to examine platform relationships, engagement timelines and client-specific tailoring. It flags identical risk assessments, control designs, sample sizes and test procedures across clients.[13]

If Your SOC 2 Used Delve

Do not assume your report is invalid, or that it is fine. Establish what was tested, by whom, and over which period.

One route is Delve's re-audit offer, still shown on its March 24 and April 3 pages on November 21; confirm eligibility with Delve in writing.[6, 7]

Context AI's move to a new platform and a new audit firm is another.[12]

A Type 2 tests controls over a period, so a replacement report takes time.

For fees by line item, see what a SOC 2 costs for a crypto company.

  • List every report issued through the platform: framework, type, period and the audit firm named.
  • Preserve the signed report, engagement letter, evidence exports and auditor messages before you change platforms.
  • Confirm the CPA firm yourself: its license, and that it signed your report.
  • Compare the system description with what you run today, including signing, custody and deployment systems.
  • Read the test results. Were exceptions found, and do the tests name your actual tools?
  • Rewrite any template policy you never reviewed or do not follow.
  • Where testing or provenance is unclear, commission a re-examination by a firm you select and contract directly.
  • Tell customers what you checked, what you found and when the new report is due.

If a Vendor Used Delve

Put the checks below to the vendor and its auditor. Where answers are incomplete, require independent re-testing before renewal.

For a crypto vendor, add key and contract questions from our vendor due diligence questionnaire. For tiers and contract terms, use our third-party risk playbook.

CheckEvidence to ask forRed flag
AuditorEngagement letter and direct contact at the CPA firmVendor cannot connect you to the auditor
IndependenceWho selected the audit firm and who set its feePlatform set the fee or the deadlines
PeriodType 2 dates and a bridge letterType 1 only, or an old period with no bridge
ScopeSystem description naming the services you useYour product, signing or custody systems missing
Tests and exceptionsTest procedures and results for each controlGeneric tests that never name the vendor's tools
Complementary controlsUser and subservice controls, and providers' own reportsWallet or cloud provider carved out with no report
Re-examinationNew report, or the engaged firm and expected dateRe-audit promised with no firm or date

What Durable Evidence Looks Like

Durable evidence outlives any vendor: signed by a named party, dated, scoped and traceable to its system.

A SOC 2 tests controls against the AICPA's Trust Services Criteria: security, availability, processing integrity, confidentiality and privacy.[20]

Crypto risk also sits in contract code, signing and custody, privileged roles, upgrade paths and incident response. A platform dashboard or a report title does not establish any of them.[21]

Keep evidence a counterparty can check without trusting your compliance tool:

  • SOC 2 reports whose CPA firm you can contact and verify.
  • Smart contract audit reports tied to commit hashes, with fix reviews.
  • Application, API and infrastructure pentest reports with retest results.
  • Key ceremony records and a dated recovery test.
  • A map of privileged roles, signer thresholds and upgrade paths.
  • Incident exercise results, with follow-up actions closed.

Show Buyers the Evidence

Publish it through a security trust center that dates each item and states its scope.

Guardian's regulatory compliance assessments map requirements to controls, test applications and infrastructure, review custody and key management, and run incident exercises.[21]

The output is an indexed evidence pack with retest results for regulators, assessors and partners.

Guardian does not issue SOC 2 opinions; a licensed CPA firm does.

To see where SOC 2 sits beside ISO 27001, NIST CSF 2.0 and CCSS, use our security standards comparison.

Need evidence your buyers can test?

Scope a Guardian compliance assessment of the systems your SOC 2 leaves out.

Frequently Asked Questions

Did a compliance platform cause any customer's security incident?

TechCrunch reported malware in LiteLLM, a Delve customer, and an incident at Context AI, another customer, that reached Vercel. Delve said customers build and manage their own code, infrastructure and day-to-day security operations.[8, 12]

Should we move from Delve to Vanta or another platform?

Switching platforms does not replace a new examination by an independent auditor. LiteLLM, which TechCrunch named as a Delve customer, said in September 2026 that its updated SOC 2 Type 2 ran with Vanta and was validated by an independent auditor.[8, 22]

Sources

  1. DeepDelver (Substack): Delve - Fake Compliance as a Service - Part I
  2. TechCrunch: Delve accused of misleading customers with ‘fake compliance’
  3. Accorp Partners via LinkedIn: Accorp Partners Denies Misleading Audit Reports
  4. AICPA & CIMA: System and Organization Controls: SOC Suite of Services
  5. Delve: Response to Misleading Claims
  6. Delve: Delve Announces Changes and New Customer Support Measures
  7. Delve: Delve sets the record straight on anonymous attacks
  8. TechCrunch: Embattled startup Delve has ‘parted ways’ with Y Combinator
  9. U.S. District Court, Northern District of California; copy hosted by Hall Attorneys: Ananthula et al. v. Mercor.io Corporation et al., Class Action Complaint
  10. U.S. District Court, Northern District of California; CourtListener RECAP copy: In re Mercor.io Corporation Data Breach Litigation: Stipulation and Order Staying Proceedings
  11. AICPA & CIMA: Ethics Staff Insights: Business arrangements with SOC tool providers
  12. TechCrunch: Another customer of troubled startup Delve suffered a big security incident
  13. Journal of Accountancy: AICPA guides peer reviewers to address SOC 2 risks
  14. AICPA & CIMA: TQA Section 9561: Effect of the Service Organization's Use of AI on SOC 1 and SOC 2 Examinations
  15. AICPA & CIMA: Illustrative SOC 2 Report with Illustrative System Description
  16. Delve: Inside Delve's Trusted Compliance Process
  17. AICPA & CIMA: Preparation, Compilation, and Review Standards
  18. U.S. Government Accountability Office: Financial Audit Manual, Volume 2
  19. AICPA Professional Ethics Division: Ethics Staff Insights: Business arrangements with SOC tool providers
  20. AICPA & CIMA: 2017 Trust Services Criteria (With Revised Points of Focus – 2022)
  21. Guardian Security: Regulatory compliance assessments
  22. LiteLLM: Our Updated SOC 2 Type 2 Report Is Available
  23. Delve: Delve automated compliance
  24. DeepDelver: Archive - DeepDelver
  25. Delve: Delve Blog
  26. Journal of Accountancy: SOC engagements: Ethics risks with tool providers
  27. PacerMonitor: Ananthula et al. v. Mercor.io Corporation et al., No. 3:26-cv-03362