Ajna vulnerability: DeFi loan agreement stolen $775,400 without pause button

If you have funds in the DeFi Loan Agreement Ajna v2, please withdraw immediately

The development team itself issued a clear call at 04:58 UTC on August 29, 2026: withdraw all quote tokens, repay outstanding loans, and stop any further interactions with the agreement. Between August 28 and 29, a total of approximately US$775,400 flowed out from seven funds pools on the Ethereum blockchain. In terms of the amount, this is just a small incident; but in terms of the way it reveals the specific DeFi protocol is built, it is one of the most enlightening cases this summer.

The reason lies in its architectural design. Ajna v2 is built as an immutable protocol: there is no governance body, no upgrade path, and no administrator key that can suspend contracts. Therefore, making security updates while the protocol is running is technically excluded. The only way to prevent the outflow of funds is for users to withdraw capital themselves. Therefore, the development team's call is not one of many preventive measures, but the only feasible response.

Overview of Ajna attack incidents: Ethereum lost US$775,400 in seven capital pools

The DeFi lending protocol is a set of smart contracts through which users can lend out cryptographic assets and borrow money with collateral without the need for bank or company intervention. In Ajna, lent funds are held in individual pools, each pool bringing together a mortgage asset and a loan asset.

Security company Defimon released a breakdown by fund pool at 09:29 UTC on August 29. According to the report, the loss distribution is as follows: the syrupUSDC pool had the largest loss, approximately US$173,700; the wstETH pool was approximately US$159,800; the rETH pool had two transactions totaling approximately US$143,000; the cbETH pool was also divided into two transactions, approximately US$136,900; the WBTC pool was approximately US$101,800; the WETH/USDC pool was approximately US$42,000; and the sDAI pool was approximately US$18,000. The total is US$775,400 mentioned above. Another media quoted a figure of approximately US$775,000. The difference stems from the affected token pricing method and has no material impact on the evaluation results.

The timeline is very tight. At 15:16 UTC on August 28, attack contracts were deployed on Ethereum. About an hour later, at 16:19 UTC, the first withdrawal of funds was completed through the cbETH pool and was recorded in block 25854888. The development team's public statement was not released until the next morning. During this period, capital outflows continued.

This left a clear mark on the size of the agreement. After the incident, the total lock-up value of the agreement (i.e., the total amount of all assets deposited into the agreement) was approximately US$246.88 million. In the past thirty days, this equates to a decline of 71.3%. Ajna was a small protocol before the attack, but now it has become very small.

Clearing mathematics rather than oracle: How the attack works

According to industry analysis, this was a manipulation of clearing bookkeeping mechanisms, not an attack on price sources. This difference is at the heart of the case and requires a brief definition of two concepts.

The role of oracle machines in lending agreements

The oracle is a service that provides a smart contract with external world prices, such as the current exchange rate of Ethereum to the U.S. dollar. Almost all lending agreements require a similar mechanism to determine whether a position is undercollateralized. This is the oracle's favored target: Anyone who can briefly distort the price offered can have a healthy position liquidated or pass worthless collateral off as a valuable asset.

Ajna deliberately does not rely on oracle. Asset valuations are based entirely on bids from lenders in the pool. This design eliminates the most common type of attack, and it has stood the test in this regard. The attacker had to find another path.

Why liquidation mathematics becomes an attack point

Liquidation is the process by which an agreement realizes collateral for a borrower's position exceeding an allowable limit. During this process, the contract calculates how much collateral is used to pay off how much debt, and what to do with the rest. In every loan agreement, this calculation is the most challenging part of the code because it must simultaneously deal with interest, fees, partial clearing, and rounding issues.

This is the entry point for the attack. The attacker triggered liquidation and used the remaining amount generated during the protocol accounting process to allocate more value to himself than he deserved. Repeating this operation across seven pools yielded the observed totals. It is worth noting that this attack did not involve any key theft or infrastructure breach. The contract performs exactly what its code specifies.

It is also worth noting that Ajna v2 was audited. Therefore, this case confirms an observation CoinGecko recorded in its 2026 State of Cryptography Security Report: Of the 245 incidents recorded between January 2025 and July 2026 (with a total loss of $3.63 billion), 147 occurred on audited agreements, which accounted for 88.44% of stolen capital. Passing an audit is a signal of quality, but not a guarantee.

Missing emergency stop button: Who will stop the outflow of funds?

Immutable protocols without governance: Why there is no pause button

Immutable smart contracts are contracts whose code cannot be changed after deployment. No addresses are allowed to push new logic, and no functions can pause operations. In some parts of the DeFi landscape, this architecture is a clear ideal because it makes trust in the team unnecessary. No one can change the rules for their own benefit after the fact, including developers.

This cost becomes apparent when damage occurs. For a scalable agreement, the team could have taken the affected pool offline and fixed the vulnerability around 16:30 UTC on August 28. But in Ajna v2, this path will not work. The analysis pointed out that patching code during operation is not a common response, and users themselves assume the function of the pause button. This is not team negligence, but the result of deliberate design decisions.

As investors, this raises a question that takes precedence over return: Who can suspend the agreement in an emergency, and how quickly? Answers vary by provider and are rarely shown on the front page. Our comparison of crypto lending providers shows which models have custody and emergency mechanisms, and which models allow you to be entirely on your own.

Defimon issued an hour's warning: What does the timeline say

Security company Defimon claimed that its surveillance detected a prepared attack contract more than an hour before the first withdrawal of funds and notified the Ajna team through its Discord channel, but received no response. This claim comes from a provider that markets such early detection services and has not been independently confirmed. The Ajna team made no public statement on this.

Even if the description is completely accurate in detail, decisive limitations remain. Warnings are only helpful if the recipient is able to take action. For cases where contracts are immutable and there is no governance mechanism, even if the team responds immediately, no functionality can be turned off. They can only issue warnings earlier, and users must withdraw funds earlier. Under this construction principle, the end of the warning chain is always you.

This makes this case different from those events where the network can be stopped centrally. For example, in a Maya protocol attack, operations were suspended to prevent further damage. This option is not everywhere and is controversial in itself because it presupposes that someone has the power to stop an open system.

What Ajna users must do now

The development team's instructions are short and clear, contain three actions in no arbitrary order.

First: Withdraw quote tokens. Quotation token is Ajna's term for assets being lent in the pool, i.e., the party the lender provides capital. As a lender of one of the pools, you should close the position. This clearly applies to pools of funds that do not appear in the Defimon detail: the detail records where the funds have flowed out, not where the funds are safely stored.

Second: Repay outstanding loans. As a borrower, a person who provides collateral can only get the collateral back through repayment. As long as the debt is outstanding, the collateral remains in the contract, thus within a system whose liquidation mathematics has been proven to be assailable.

Third: No new interactions occur. Don't make new loans, don't make new deposits, and don't adjust existing offers. Each further transaction again exposes capital to known loopholes.

When performing these actions, the same principles apply as for any emergency action in DeFi: only call addresses from your own bookmarks, and never use search results or unsolicited messages. After an attack is exposed, the number of fake rescue pages usually rises because fraudsters take advantage of the sense of urgency created.

How to check whether your loan agreement has an emergency exit mechanism

Once you know what to look for, the pause button issue can be resolved in a matter of minutes. Three points are sufficient for a preliminary assessment.

Three questions asked to the document

First: Is there a pause function and who can trigger it? Documentation typically lists it under headings such as "Emergency Suspend,""Guardians" or "Circuit Breaker." If there is no mention, an immutable design is assumed.

Second: Is the contract upgradable and who holds the key? The upgrade path means that the vulnerability can be fixed. This also means that when your money is placed in a contract, someone can change the rules. The two complement each other, not a contradiction, but a trade-off you should make carefully.

Third: How can the warning be conveyed to you? If the only reporting channel is the Discord channel that you won't read, then it doesn't actually exist for you. Setting notification services for your own addresses costs zero, but it can give you a valuable time advantage at critical moments.

Anyone unwilling to conduct this inspection can find a simpler answer from a regulated provider: There, companies are regulated and held accountable, and responding to incidents is part of the business model. This path reduces rewards and lets you lose control, but also saves you from the responsibility of acting as an emergency switch at 16:19 UTC.

Ajna's background: A summer full of small events

The Ajna attack did not occur in isolation. One day earlier, on August 28, 2026, Solana-based card application Avici lost a card balance of $500,85,922 million, affecting 1685 users. Preliminary estimates were above $600,000 to $1 million, with a lower amount confirmed after review. According to card partner Rain, the reason is that some other programs also use the wrong version of card contracts. Avici has committed to fully compensate all affected card balances.

The difference between these two cases lies precisely at the core of this question. At Avici, there is one company that can make commitments, and its partners point out the vulnerabilities. In Ajna, there is only one running contract and one team that requires users to withdraw funds. In an agreement without a pool of funds or governance mechanisms, compensation is not taken into account.

To understand magnitude, statistics are helpful. The above-mentioned CoinGecko report counted 245 incidents from January 2025 to July 2026, with a total loss of US$3.63 billion. Using this as a standard,$775,400 is just a footnote. For those affected, this amount is the total loss, and its importance is determined not by its proportion in the annual statistics, but by its proportion in their own investment portfolio.

Taxation and Evidence: What should investors record after an attack

Losses caused by an attack are not simple and straightforward in terms of tax treatment, and this article does not constitute tax advice. In any case, what is worth doing immediately is to preserve the evidence while the data is still available.

Save transaction hashes for your deposits and withdrawals, account balances for affected positions before August 28, 2026, a public statement of the agreement with date and time, and proof of the outflow of funds from the blockchain browser. If subsequent claims, settlement or tax processing are involved, you will need these documents. Anyone who waits until then to collect will be faced with deleted web interfaces and archived Discord channels.

It is important to distinguish between two events: funds flowing out through an attack and the subsequent sale of salvaged positions, which are two different things in tax terms. Record both separately, including date, quantity, and value in your reporting currency.

Enlightenment from the Ajna attack: What to remember

If you invest in Ajna v2, take action now. Withdraw quote tokens, repay loan, and stop interaction in order. As for where to place funds and under what conditions, please see our comparison of crypto lending.

Resolve urgent issues for each agreement before depositing funds. Pause functions, upgrade paths, reporting channels. Anyone who is unwilling to conduct this check on their own is better off choosing a regulated provider; please refer to our overview of regulated cryptocurrency exchanges for which platforms are licensed.

Separate trading balances from positions. Funds that you have not proactively deployed should not be stored in smart contracts, but should be kept by yourself. For which devices are suitable and what's the difference, see Hardware Wallet Comparison.

The details and timeline by fund pool are from the analysis as of August 29, 2026. The project issued an appeal to users on its X platform account at 04:58 UTC on the same day.

(As of August 29, 2026. This article does not constitute investment advice. Price and fee structure subject to change; check terms with provider before purchase.)