hack or exploit

Loopscale pauses operations after sustained attack on its Genesis Vaults

47Importance
updatingStatus
4News media
4Pieces
Published
Updated
Since then
3 new reports
Also mentions
SOLUSDC

Loopscale suspended parts of its Solana lending service after sustained attacks on its Genesis Vaults and a week-long run of malicious API traffic. The team later said some loan functions were restored, while withdrawals stayed frozen for USDC Genesis-funded loans.

Key claims & sources

✓
The platform said the attack traffic reached more than 30,000 malicious requests per day during the campaign.
✓
Loopscale temporarily halted all operations on November 5 after detecting a coordinated campaign of API attacks against its SOL and USDC Genesis Vaults.
✓
Loopscale later partly restored loan functions but kept vault withdrawals frozen for USDC Genesis-funded loans.
✓
Loopscale said repayments and collateral withdrawals stayed disabled for USDC Genesis-funded loans while it described two attack paths.

What it means

Loopscale built its Genesis Vaults as a Solana lending product that routes SOL and USDC deposits into yield strategies, a model common since Solend and other Solana lenders popularized vault-based lending after 2021. Unlike a smart-contract exploit draining funds directly, this incident targeted the API layer that vaults depend on for off-chain coordination, a less-discussed attack surface than the audited contracts themselves.

Borrowers and depositors in USDC Genesis-funded loans cannot repay loans or withdraw collateral while the freeze holds, even though other loan functions have returned. Users with SOL-side exposure appear to have regained more normal access, creating a two-tier situation where capital sits locked depending on which vault funded the position. Anyone relying on Loopscale for active credit lines must wait on the protocol's own timeline rather than execute standard DeFi actions.

A protocol can pass contract audits and still fail at the infrastructure layer that handles request traffic, and 30,000 malicious requests a day shows attackers probing exactly that gap rather than the blockchain logic. This complicates the usual DeFi security narrative, which focuses almost entirely on code audits and bug bounties. Whether Loopscale's API defenses get hardened before relaunch, or whether this becomes another case of off-chain plumbing undermining on-chain guarantees, is the real test here.

Loopscale's own disclosure of 'two attack paths' against the Genesis Vaults is the detail to track: a full technical post-mortem naming both vectors would clarify whether the fix is a patch or a redesign. Until USDC Genesis-funded loan withdrawals reopen, the protocol's claim that deposits remain unharmed stays only partially tested. The next statement on when repayments and collateral withdrawals resume will show whether this was contained in days or stretches into a longer rebuild.

Market reaction i

Total crypto marketall crypto assets combined no single asset in the event: read against the whole market
first headline
0.0% 2 h before
-2.3% 4 h after
$2.7Tmarket cap at publication
12data points

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Nov 5 11:37
+2 h 22 m
Nov 5 13:59
crypto.news context
Its angle: statement, deposits, although; with quotes
+8 h 20 m
Nov 5 19:57
Crypto Economy context
Its angle: infrastructure, decentralized, specifically
+13 h 4 m
Nov 6 00:42
The Defiant context
Its angle: withdrawals, collateral, repayments

Other recent incidents

WhenWhat happenedFigure
1 days ago Loopscale Lending · Unknown incident no figure in dollars
1 days ago TENDRIL · Swap Logic Flaw incident $550k
1 days ago $TENDRIL · Smart contract vulnerability incident $555k
3 days ago InsurancePool/CoreVault · Flash loan attack incident $112.3k
4 days ago Solana MEV Bot King · Hot wallet key compromise incident $856k

4280 incidents stored