Post-Mortem of the Venus THE Attack: How to Profit in a Fleeting Window?

marsbit2026-03-16 tarihinde yayınlandı2026-03-16 tarihinde güncellendi

Özet

Approximately two hours ago, Venus Protocol's THE token was exploited using a classic Mango Markets-style price manipulation attack. The attacker targeted THE, a low-liquidity collateral asset, by depositing it, borrowing other assets, and using those to buy more THE, artificially inflating its price. Once the time-weighted average oracle updated, the inflated price allowed further leveraged borrowing. To bypass THE's borrowing cap, the attacker performed a "donation attack" by transferring THE directly to the vTHE contract, increasing the recognized collateral value. After the first manipulation phase, THE's price stabilized around $0.50. The attacker attempted to further amplify gains by continuing to buy THE, but mounting sell pressure limited price increases and pushed their health factor near 1.0, risking liquidation. The collateral, nominally valued around $30M, had extremely low liquidity, making large-scale liquidation at inflated prices impossible. Recognizing the situation, the writer opened a short position on THE with high leverage, anticipating a price collapse due to overvaluation, illiquidity, and forced selling. After liquidation, THE price plummeted to ~$0.24, below its pre-attack level, resulting in a ~$15K profit for the writer. Venus Protocol was left with ~$2M in bad debt. The attacker likely gained little or lost funds, though may have profited from off-chain positions. The event highlights that nominal collateral value in DeFi does not equal realizabl...

Two hours ago, VenuV's THE token was hit with a classic Mango Markets-style price manipulation attack.

The attacker targeted the low-liquidity collateral THE:

· First, collateralized THE

· Borrowed other assets

· Used the borrowed assets to buy more THE

· Pushed THE price higher

· Waited for the time-weighted average oracle price to update, then obtained higher collateral value and continued the cycle of borrowing.

Due to THE's extremely poor on-chain liquidity, its price was driven from $0.27 to nearly $5. The oracle price subsequently updated to around $0.5 (time-weighted average), giving the attacker room to further amplify leverage.

More critically, THE itself has a supply cap.


Normally, this would limit the attacker's ability to expand their position. But they used a classic old trick to bypass it: the Compound fork donation attack. After depositing a large amount of THE, they directly transferred THE to the vTHE contract, "donating" to further inflate the collateral value recognized by the system and break through the cap.

Attack transaction: 0x4f477e941c12bbf32a58dc12db7bb0cb4d31d41ff25b2457e6af3c15d7f5663f

After the first wave of the attack, THE's price stabilized around $0.5.

At this point, the attacker could have walked away with the borrowed assets. But they clearly wanted to maximize profits, so they continued to use the borrowed assets to buy THE, attempting another pump.

The problem arose: Although the price was abnormally high, selling pressure from the market became extremely intense. The attacker kept buying but could barely push the price higher. Eventually, they almost exhausted their borrowing capacity, and their position's health factor dropped close to 1, nearing liquidation.

By then, the situation was very clear: The attacker's collateral, including their pre-prepared assets and THE bought during the attack, had a nominal value of about 30M. But the core issue with this collateral was—there was simply not enough liquidity to absorb it. Once liquidation began, this THE would be dumped onto the market. And no one in the market could possibly absorb such a large volume at these inflated prices.

So what did I do?

When liquidation started, I directly opened a short position on THE. And this was a position where relatively higher leverage could be applied.

The reason was simple: High valuation, low liquidity, massive passive selling pressure, no buyers.

The outcome was unsurprising: After the liquidation ended, THE's price fell all the way back to around $0.24, even lower than the pre-attack price, because original holders also sold during the process.

I closed my short position here, profiting about 15K.

In the end, Venus was left with about 2M in bad debt.

As for how much the attacker actually profited, I haven't done a complete analysis; but judging from the operations of some addresses, they likely made little to no profit, or even blew themselves up. However, the attacker might still have profited from off-chain perp positions (just like our operation).

Venus's ~2M bad debt address: https://debank.com/profile/0x1a35bd28efd46cfc46c2136f878777d69ae16231

This incident once again demonstrates:


In DeFi, "nominal collateral value" does not equal "liquidation value". When the collateral itself lacks liquidity, the system sees 30M, but the market might only be able to realize a fraction of that.

In 2023, I published a paper titled 'Unmasking Role-Play Attack Strategies in Exploiting Decentralized Finance (DeFi) Systems' which provides a detailed mathematical model of this type of attack. Interested readers can refer to: https://dl.acm.org/doi/10.1145/3605768.3623545

İlgili Sorular

QWhat was the core strategy used by the attacker in the Venus THE exploit?

AThe attacker used a price manipulation strategy similar to the Mango Markets attack. They deposited the low-liquidity collateral THE, borrowed other assets, used those assets to buy more THE to drive its price up, waited for the time-weighted average oracle price to update to reflect the inflated value, and then repeated the cycle to gain higher borrowing power.

QHow did the attacker bypass the supply cap limitation on THE?

AThe attacker used a 'donation attack' by directly transferring THE tokens to the vTHE contract after a large deposit. This 'donation' artificially increased the total supply recognized by the system, allowing them to further inflate the collateral value and bypass the supply cap.

QWhy did the author of the article decide to open a short position on THE?

AThe author opened a short position because the attacker's collateral (THE tokens) had an extremely high nominal value but very low liquidity. They anticipated that once liquidation began, the massive sell pressure from the forced selling of these tokens would cause the price to crash dramatically, as there would be no market to absorb such a large volume at the inflated price.

QWhat was the final outcome for the attacker and the Venus protocol?

AThe attacker likely made little to no profit and may have even lost money from their on-chain maneuvers, though they might have profited from off-chain perpetual positions. The Venus protocol was left with approximately $2 million in bad debt.

QWhat key DeFi concept does this event highlight according to the article?

AThe event highlights that 'nominal collateral value' is not the same as 'liquidation value.' When collateral itself lacks sufficient liquidity, the value the system calculates can be vastly higher than the amount the market can actually realize during a liquidation event.

İlgili Okumalar

GPT-5.6 Countdown: Abandon the Illusion of a Single API, Computational Iteration Can't Outpace a Single Page of Compliance

In mid-June, three seemingly independent industry events—the compliance-driven throttling of Fable 5, the open-sourcing of GLM-5.2, and the leaked release timeline for GPT-5.6—are pushing the global AI industry toward a watershed moment. These shifts signal a fundamental restructuring of the industry's underlying logic. First, **"usability" has substantially overtaken "advanced capabilities"** as the primary weight, pushing the global large language model (LLM) supply chain into a "dual-track" phase of controlled closed-source and local open-source coexistence. Second, **the competitive moats of closed-source giants are shifting**. Their technical focus is moving from "language intelligence" toward "spatial intelligence (world models)"—a domain heavily reliant on computing power. Third, faced with常态化 transnational compliance risks, **a "model-agnostic" decoupled design has become a survival necessity for application-layer developers to maintain business continuity.** The article details how Anthropic's Fable 5, despite its advanced engineering feats, was restricted for non-U.S. citizens within 72 hours of launch, highlighting how geopolitical compliance can instantly limit even the most advanced models. In response, the open-source camp, exemplified by Zhipu AI's MIT-licensed GLM-5.2, is gaining market share by offering stable performance improvements and significant cost advantages (up to 70% savings for enterprises), while achieving full adaptation with domestic semiconductor platforms. Meanwhile, closed-source leaders like OpenAI are pivoting. The anticipated GPT-5.6 reportedly shifts focus from language to spatial intelligence and world models, aiming to rebuild a generational gap in areas like 3D understanding, simulation, and industrial design that demand immense compute. The core conclusion is that the LLM supply chain's logic has changed. Enterprises must now evaluate infrastructure based on a composite of technical performance and policy compliance. For developers, complete reliance on a single closed-source API poses unacceptable risk. Implementing a truly model-agnostic architecture—enabling swift switches to compliant, locally deployable open-source alternatives—is no longer just good practice but a fundamental baseline for business continuity.

marsbit50 dk önce

GPT-5.6 Countdown: Abandon the Illusion of a Single API, Computational Iteration Can't Outpace a Single Page of Compliance

marsbit50 dk önce

Is the 'Token Subsidy War' Among AI Giants Almost Over?

The article discusses the ongoing "token subsidy war" among AI giants like OpenAI and Anthropic, questioning whether it's nearing its end. It reveals that current AI subscription prices are heavily subsidized, with some plans offering tokens at up to 70 times the actual cost to attract and retain heavy users, especially developers and enterprises. This strategy mirrors past internet-era subsidy battles, but with a key difference: AI tokens lack "lock-in" effects. Unlike ride-hailing or food delivery apps, users can easily switch between AI providers as APIs become standardized, making it difficult for companies to raise prices post-subsidy. The piece highlights a structural asymmetry in the competition. Giants like Google, with massive advertising revenue, can afford to subsidize tokens indefinitely, akin to using "tokens as a weapon." In contrast, venture-backed companies like OpenAI and Anthropic face pressure to become profitable, especially as they approach IPO. The article cites Google Ventures founder Bill Maris, who suggests Google could slash token prices by 80%, putting immense pressure on competitors. Two potential endgames are presented: the "internet service" model (subsidize, monopolize, then raise prices) and the "utility" model (tokens become a standardized, low-margin commodity like electricity). Given the low switching costs, the latter seems more likely. The competition may not have a single winner but could instead accelerate AI's evolution into a foundational, infrastructure-level technology, akin to a public utility. For now, users continue to benefit from heavily subsidized token costs.

marsbit1 saat önce

Is the 'Token Subsidy War' Among AI Giants Almost Over?

marsbit1 saat önce

Beyond the Stadium: The Profitable Games Surrounding the World Cup

"Beyond the Pitch: The Profit Game Around the World Cup" The FIFA World Cup transcends being a sporting spectacle, evolving into a massive global arena for speculation and profit-seeking. The 2026 tournament has amplified this dynamic, creating a multi-layered ecosystem of financial opportunism alongside the football. **Prediction markets** have surged into the mainstream. Platforms like Polymarket and Kalshi saw trading volumes for World Cup contracts soar, attracting new users with their financial trading model and high-profile, chain-based wealth stories that overshadow traditional sports betting in terms of growth and narrative. However, **traditional sportsbooks** remain the dominant force, leveraging established user habits, legal markets, and comprehensive product offerings to handle the vast majority of speculative wagers, with projections suggesting record-breaking betting volumes. Capital markets also react. **"Concept stocks"** in countries like South Korea and Japan experience volatile price swings based on team performance and anticipated fan spending on items like chicken, beer, and viewing parties, effectively becoming a stock market reflecting fan sentiment. The **ticket resale market** has become a sophisticated arena for arbitrage. Prices fluctuate wildly based on team draws and star power, with sellers sometimes listing tickets they don't yet own in a practice akin to short-selling, while FIFA's own "Right to Buy" tokens add another layer of speculative trading. **Collectibles and merchandise** offer another avenue. Panini sticker albums, with their inherent scarcity and nostalgic value, can become high-value collectibles. Limited-edition or locally themed jerseys command significant premiums on secondary markets, and even counterfeit vendors profit from fans' desire for affordable match-day identity. The **cryptocurrency** space has seen a frenzy of speculative, unauthorized World Cup-themed meme coins on chains like Solana. These tokens, often exploiting team names and player imagery, experience extreme pump-and-dump cycles, creating stories of massive gains for a few early entrants and steep losses for many others. Finally, an entire industry thrives on **providing information and tools** to other speculators. Developers create platforms like SeatSidekick to track ticket inventory and prices, while paid Telegram groups and subscriptions sell betting tips and predictions, monetizing the widespread desire for an informational edge. In essence, the World Cup has become a compressed, global laboratory for speculation. While the games determine champions on the field, a parallel, complex network of financial transactions—spanning prediction contracts, bets, stocks, tickets, collectibles, crypto, and information services—settles its own scores in the global market.

marsbit1 saat önce

Beyond the Stadium: The Profitable Games Surrounding the World Cup

marsbit1 saat önce

How Does Codex Use a Computer? Three Entry Points and Permission Boundaries

This article explains the three primary methods for Codex to interact with a computer, each with distinct use cases, permission boundaries, and trust levels. **1. Computer Use:** This offers the broadest access, allowing Codex to visually control and interact with the graphical user interface of authorized macOS/Windows apps, system settings, and even iOS simulators. It's ideal for tasks lacking APIs or structured tools, such as operating legacy software or multi-app workflows. However, it's the slowest method and has the widest permission scope, requiring careful supervision for sensitive actions. **2. Chrome Extension:** This grants Codex access to the user's logged-in Chrome browser state, including cookies, profiles, and open tabs. It's best for tasks requiring user identity across websites like Gmail, LinkedIn, Salesforce, or internal dashboards. Its key advantage is multi-tab control for complex workflows. While more powerful for browser-based tasks than Computer Use, it carries higher sensitivity as actions are performed under the user's identity. **3. In-App Browser:** This is a browser isolated within the Codex thread, separate from the user's personal browsing data. It excels in web development and debugging scenarios—previewing local servers, testing responsive layouts, or annotating designs directly on the page. Its isolation is a strength for development but a limitation for tasks requiring login sessions. The core principle is to choose the narrowest, safest, and most structured interface for the task. Use plugins or MCPs first, resort to visual control (Computer Use) only for GUI-dependent tasks, employ the Chrome extension for identity-reliant browser work, and prefer the In-App Browser for isolated development. **Appshots** are clarified as a fourth, complementary tool for *inputting* context—capturing a screenshot of a window to point Codex to something—rather than a method for Codex to *act*. Together, this layered approach highlights a key to AI agent productization: not granting unlimited permissions, but constraining them within clear boundaries for specific tasks while preserving user oversight.

marsbit3 saat önce

How Does Codex Use a Computer? Three Entry Points and Permission Boundaries

marsbit3 saat önce

İşlemler

Spot
Futures
活动图片