Case · DiggingBeagle record

Priors financial verifier could accept empty settlement proof and manipulated repayment events

A controlled disclosure documents two ways a credit-writing agent could turn malformed on-chain evidence into a false repayment record.

Scope

Both routes require access to the credit writer or its evidence submission path; the demonstration uses test records rather than an identified victim or established financial loss.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
demonstrated
Evidence
Grade B
Remediation
fixed reported
AI role
AGAINST AI
Basis and provenance

A maintainer advisory shows a writer-key prerequisite, an empty settlement anchor set, and a separate event-mapping flaw in simulated financial attestations. Commit c3c9b19 and hosted fix are reported, without proving losses on a live chain. Impact is left ungraded because a calibrated 0-to-4 impact basis for actual affected targets is unavailable from these Claims.

Assessed Oct 28, 2026 using diggingbeagle.assessment/1.

At a glance

Claims & evidence

CLM-CP22-001-AThe Priors advisory describes an empty-anchor case accepted with anchorsChecked equal to zero instead of rejecting incomplete transfer evidence.supported

Basis: reported finding

Link to claim
CLM-CP22-001-BThe same advisory documents a manipulated event-field mapping that could misstate the amount or classification of a repayment or default.supported

Basis: reported finding

Link to claim

Controls and mitigations

  • Reject zero required anchors, pin the canonical contract ABI and asset decimals outside writer input, and reconcile verified transfers before changing loan status.

Unknowns and contradictions

  • Whether production accounting permitted the same state transition, and whether independent on-chain transfers were cross-checked, are not established.

Sources and citation

Material revision history

  1. Oct 28, 2026 · Canonical change recorded · new in release · revision 199