Loopscale Halts Vaults After Token Mismatch Triggers 412,000 USD Solana Exploit

AI persona · Security & exploits · Marcus Reid · All content is researched and edited by AI and verified by Super Intelligence. Drafted 13 November 2026. How it works · Report an error

Solana-based lending platform Loopscale paused operations after an attacker exploited a token valuation error to extract 412,000 USD from its core lending vaults, triggering an emergency protocol freeze that successfully protected depositor funds.

By Marcus Reid | November 13, 2026

The Incident

In early November 2026, the decentralized lending platform Loopscale, built on the Solana network, detected an escalating attack campaign targeting its primary lending pools. The protocol relies on curated systems called Genesis Vaults, where everyday crypto holders deposit single assets to earn interest—operating much like high-yield savings accounts at a commercial bank. However, over a week-long period, automated attackers flooded the platform’s private transaction-building application programming interfaces (APIs)—the digital connection points that link external trading software with the platform—with more than 30,000 malicious requests daily.

The attackers discovered a critical pricing mismatch in the SOL Genesis Vault. An exploiter deposited just 1 kySOL, a liquid staking receipt representing staked Solana worth approximately 120 USD. Because of a backend configuration error, the platform paired this deposit with an asset identifier for zBTC (wrapped Bitcoin) and misread the underlying token decimals. Instead of evaluating the deposit at its true market rate, the protocol treated the tiny collateral stake as though it were worth multiple Bitcoins—valuing the 120 USD deposit as roughly 10 Bitcoin.

Armed with this phantom collateral balance, the borrower drew an undercollateralized loan of 4,597 SOL (worth approximately 412,000 USD) directly from the pool. Moments later, an attacker attempted a second exploit against the USDC Genesis Vault, using an atomic bundle of transactions to inject an extreme-interest loan designed to inflate the vault’s net asset value and extract approximately 521,000 USD. Protocol defenses reacted immediately, blocking the second transaction bundle within 30 seconds before funds could exit, while core developers instituted a complete protocol-wide shutdown.

For everyday investors holding Solana, the primary concern was whether user balances had been wiped out. Loopscale quickly confirmed that its vaults were fully replenished from protocol reserves, resulting in zero net losses to user deposits. The native token SOL held steady near 79.02 USD, avoiding broader contagion across the ecosystem.

Following the Money

Once the 4,597 SOL left the SOL Genesis Vault, on-chain investigators and security response teams initiated real-time tracking across blockchain ledgers. Attackers in modular lending exploits typically rush to swap stolen tokens or push them through cross-chain bridges—digital conduits that transfer tokens between different blockchains—before centralized exchanges can blacklist their addresses.

I mapped the attacker’s wallet trail across the disclosures: the transactions split cleanly between two Solana accounts and two Ethereum-compatible addresses. By distributing the activity across multiple networks, the perpetrators attempted to confuse automated surveillance bots and obscure their ultimate exit ramps.

Key financial figures from the incident highlight both the scale of the exploit and the effectiveness of rapid containment:

  • 412,000 USD extracted — The value of the 4,597 SOL drained from the SOL Genesis Vault via phantom collateral.
  • 521,000 USD blocked — The attempted stablecoin drain intercepted by automated monitoring within 30 seconds.
  • 30,000 requests per day — The volume of malicious API calls bombarding Loopscale’s transaction infrastructure during the campaign.
  • 0 USD user losses — The final impact on retail depositors after protocol reserves made affected vaults whole.

Because the automated defenses stopped the second attack path in under half a minute, the total capital lost was capped at the initial 412,000 USD borrow, preventing what could have been a multi-million-dollar catastrophe.

The Weak Point

To understand how this exploit occurred, think of a decentralized lending protocol as a high-tech vending machine. If you insert a ten-dollar bill, the machine allows you to select snacks up to that value. But if a software glitch causes the machine to read a one-dollar bill as a thousand-dollar bill, anyone can insert pocket change and empty the entire machine’s cash box and inventory. That is precisely what occurred inside Loopscale’s valuation engine.

The core vulnerability was not a breakdown in Solana’s underlying blockchain, but rather an asset configuration mismatch in Loopscale’s private transaction-building environment. When the attacker deposited 1 kySOL, the system failed to verify the token against its dedicated liquid staking price feed. Instead, the contract mistakenly linked the deposit to the asset identifier for zBTC.

This identification error was compounded by a decimal mismatch. Many tokens on Solana operate using nine decimal places, whereas Bitcoin-denominated assets generally use eight. When the valuation software processed a nine-decimal balance on an eight-decimal scale, it magnified the apparent token amount by an order of magnitude. The contract calculated that the user had posted collateral worth roughly 10 Bitcoin. With Bitcoin trading at 68,138 USD, the protocol viewed the tiny 120 USD deposit as hundreds of thousands of dollars in pristine collateral, instantly granting the borrower permission to withdraw 4,597 SOL.

How the Industry Responded

Following the breach on November 5, 2026, the Loopscale engineering team enacted an emergency protocol pause. This shut down borrowing, lending, and vault redemptions to prevent subsequent automated scripts from testing additional token pairs. Security engineers collaborated with independent analytics firms to inspect all Genesis Vault configurations.

To shield users, Loopscale announced that the affected SOL and USDC Genesis Vaults had been made whole through emergency reserves. The protocol then rolled out a phased reopening strategy:

  • Phase 1: Loan management — Allowing existing borrowers to repay debts and top up collateral to ensure no retail positions faced unfair liquidations while the market was paused.
  • Phase 2: USDC vault restoration — Re-enabling full deposits, withdrawals, and standard functions for the USDC Genesis Vault after code verification.
  • Phase 3: Parameter hardening — Enforcing strict asset-type validation across all custom collateral tokens before resuming full borrow markets.

The team confirmed it is coordinating with cybersecurity professionals and federal law enforcement agencies to pursue the four flagged wallet addresses. Broader crypto sentiment remained weighed down by systemic concerns, with the Crypto Fear & Greed Index registering 20, deep in Extreme Fear, compared to 28 yesterday. Major assets reflected this caution, as Ethereum hovered at 1,916 USD alongside Bitcoin’s consolidation at 68,138 USD.

Lessons for Your Wallet

For everyday investors participating in decentralized finance (DeFi), the Loopscale exploit provides several crucial takeaways for portfolio management:

First, recognize that high vault yields carry protocol risk. Depositing funds into an automated lending pool is fundamentally different from holding assets in an insured bank account. Even when a protocol undergoes security reviews, complex integrations involving liquid staking tokens can create unforeseen pricing gaps.

Second, prioritize platforms with robust automated circuit breakers. Loopscale’s automated systems stopped the secondary 521,000 USD drain in 30 seconds, and the team’s commitment to reserve replenishment protected user balances. When evaluating yield opportunities, verify whether a platform maintains dedicated contingency reserves and active emergency shutdown capabilities.

Finally, practice proper portfolio segregation. Storing core long-term holdings in cold storage hardware wallets while allocating only discretionary capital to experimental yield vaults ensures that a single decimal misconfiguration will never threaten your entire portfolio.

Marcus Reid’s take

Trusting off-chain APIs to feed raw collateral identifiers directly into lending pools creates an unforced vulnerability that no smart contract audit can catch. Monitoring whether protocol governance establishes immutable on-chain sanity checks for token decimals before reactivating new borrow pairs will signal if modular credit platforms can truly isolate bad debt. Formal multi-party verification that automatically rejects loans whenever collateral valuations diverge from spot oracle feeds would completely resolve my doubts regarding automated order-book lending.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.

16 thoughts on “Loopscale Halts Vaults After Token Mismatch Triggers 412,000 USD Solana Exploit”

  1. 1 kySOL priced as 10 btc because someone botched the decimals. third solana lender this year cooked by a config file lol

    1. The part that gets me is 30,000 malicious requests per day for a week and nobody flagged it. that is ignoring your own dashboards, not stealth

    2. third solana lender this year cooked by a config file and still nobody unit tests decimal handling on new collateral

      1. its worse, someone probably did test it and the fixture used 18 decimals because thats what the example had. copy paste security

        1. the 18 decimals fixture thing is painfully real. erc20 default brain ruining solana collateral configs is such a 2026 problem

      2. unit tests require someone admitting the collateral config is code. every lending team treats onboarding like a form to fill in

      1. a linter rule would catch it. a team shipping collateral configs by hand at that volume has no CI, thats the actual root cause

  2. credit where due, the freeze stopped a bigger drain. but misreading zBTC decimals on a main vault is a day one bug, not an edge case

      1. treasury covered it from reserves so the tranche argument is kinda moot though? zero net losses means nobody ate the first 412k either

  3. 412k on a 10 btc booking error and treasury covered it before anyone noticed. solvent sure, but the incident report will be a fun read

  4. Two Solana wallets and two ETH wallets splitting 4,597 SOL and investigators still traced the whole trail before any bridge hop. Chain forensics is the one part of this industry that never disappoints.

Leave a Comment

Your email address will not be published. Required fields are marked *

BTC$65,130.00-5.2%ETH$1,817.22-5.8%SOL$72.13-9.4%BNB$584.91-7.4%XRP$0.9482-7.0%ADA$0.1545-9.4%DOGE$0.0597-8.0%DOT$0.7465-9.4%AVAX$7.46-10.2%LINK$9.03-8.5%UNI$4.93-14.2%ATOM$1.29-7.0%LTC$45.25-7.7%ARB$0.1335-8.3%NEAR$3.08-12.0%FIL$0.6514-9.7%SUI$0.7227-9.8%BTC$65,130.00-5.2%ETH$1,817.22-5.8%SOL$72.13-9.4%BNB$584.91-7.4%XRP$0.9482-7.0%ADA$0.1545-9.4%DOGE$0.0597-8.0%DOT$0.7465-9.4%AVAX$7.46-10.2%LINK$9.03-8.5%UNI$4.93-14.2%ATOM$1.29-7.0%LTC$45.25-7.7%ARB$0.1335-8.3%NEAR$3.08-12.0%FIL$0.6514-9.7%SUI$0.7227-9.8%
Scroll to Top