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

Borrowable USDC Deposit, SiloId: 170

0x7786DbA2A1F7a4B0B7AbF0962C449154C4F2b8AcView on depeg monitor →

etherc4626 vault100 (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 risk100/100High risk

Top 3 risk drivers

  1. Protocol risk100 pts(+15.00 to score)
  2. Depeg90 pts(+4.50 to score)
  3. TVL outflow100 pts(+2.00 to score)

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

Score history (7d, 24 snapshots)+20 pts since 2026-03-25
80100050100

Alert History

Loading alert history…

✕ Do not list

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

TVL trend

TVL down 9870% 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%
$43Kscore 1

Source: inferred

Rating breakdown

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

Protocol risk100
TVL outflow100
Depeg95
Size50
Webacy code40
utilisation_risk40
looping30
oracle20
Maturity10
Volatility10
Asset5

Score 100 (CRITICAL). Primary drivers: external protocol risk, active depeg signal, tvl outflow. Active signals: prior exploit.

Risk flags

DepegExploit historyLow TVLLow utilisationsilo_loop

Exploit history

via DeFiLlama

Incidents

1

Total lost

$546K

Trading Strategy technical risk

From Trading Strategy's Vault Technical Risk Framework

Blacklisted

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
be9f9a36
b7aad80a
d89b536c
+1 more
external function
327811d1
de2aaa1e
(bool success, bytes memory returndata) = address(_token).call(data)
siloConfig.accrueInterestForBothSilos()