WebacyStablecoin Universe
OverviewAlertsBackingYieldUpcomingEventsVault IncidentsGraveyardSupply FlowsFreeze IntelligenceModelDocsVault UniverseEcosystemVault StatsProtocolsAbout
← Back to vaultsDocumentation

Borrowable USDC Deposit, SiloId: 168

0x0D495B6EEFf58fBb7eeF9303ac4D7306d47e6d9bView on depeg monitor →

etherc4626 vault82.6 (critical)Needs attention⚠ Exit Recommended
⚠
Exit Recommended
This vault holds a depegged underlying asset. The depeg risk score and current pricing indicate the underlying has lost significant peg stability. Consider exiting or reducing exposure.
Low risk82.6/100High risk

Top 3 risk drivers

  1. Depeg90 pts(+4.50 to score)
  2. utilization39.8 pts(+3.98 to score)
  3. Protocol risk20 pts(+3.00 to score)

Share price: $0.0010(below peg — drives Depeg flag)

Score history (7d, 25 snapshots)+34 pts since 2026-03-25
4883050100

Alert History

Loading alert history…

✕ Do not list

Critical risk score or blocking flags (redemptions closed, dormant, unverified).

TVL trend

TVL down 9980% in 30 days— outflow risk

What's in this vault

Deposits

USDC

What this vault is exposed to

You deposit USDC. Here's what backs your position.

USDC
100.0%
$8Kscore 1

Source: inferred

Rating breakdown

Sub-scores sorted by contribution. Each bar is relative to the top contributor.

TVL outflow100
Depeg95
Size50
Volatility50
Webacy code40
Inactivity40
utilization39.8
looping30
Protocol risk20
oracle20
Maturity10
Asset5

Score 83 (CRITICAL). Primary drivers: active depeg signal, high utilization, external protocol risk. Active signals: prior exploit.

Risk flags

DepegExploit historyInactiveLow TVLsilo_loop

Exploit history

via DeFiLlama

Incidents

1

Total lost

$546K

Trading Strategy technical risk

From Trading Strategy's Vault Technical Risk Framework

Low

Funding regime

Perp funding rate data (healthy vs compressed/inverted) will indicate when vault yield is from stable vs stressed conditions. Coming soon.

Webacy code analysis (2 findings)

Security findings from static analysis. Critical issues (reentrancy, unchecked calls, etc.) may require attention.

assembly
52cb5036
be9f9a36
b7aad80a
+1 more
external function
327811d1
de2aaa1e
(bool success, bytes memory returndata) = address(_token).call(data)
siloConfig.accrueInterestForBothSilos()