I still remember the first time I heard someone call a crypto card platform “truly self-custodial.” It sounded almost too clean. You deposit your own assets, keep the keys, spend through a Visa line, and the company never touches the funds. Fast forward to late August 2026 and that promise is sitting under a microscope after more than a million dollars walked out of Avici user accounts in a matter of hours.
What Unfolded During The Avici Attack On Solana
On August 28 the numbers started climbing fast. One wallet that analysts tracked ended up holding just over ten thousand SOL plus roughly eleven thousand six hundred dollars in stablecoins. At the time of the checkpoint that stack of SOL was worth around one point zero seven million. The whole operation looked methodical rather than chaotic.
The address received its first funding through a bridge at 13:40 UTC. A modest 1.79 SOL arrived from another chain. Then silence for about three hours. At 16:49 the first interaction with Avici’s programs appeared. From that moment the pattern repeated across account after account.
The Three-Step Pattern That Emptied Collateral
Every successful drain followed the same sequence. First the attacker submitted signatures through Avici’s authorization program while also calling Solana’s Ed25519 verification routine. Next came a call to AddCollateralAdmin that registered a new administrator on the user’s collateral account. The final step was WithdrawCollateralAsset. That last instruction moved the actual funds to an address the attacker controlled.
In one example the withdrawal instruction alone pulled 2,346.77 USDT. Some of the collected stablecoins were swapped into SOL along the way. One of those swaps returned 209.76 SOL. By the time observers stopped counting, the wallet had signed more than fourteen thousand transactions. A little over two thousand of them failed, but the rest got the job done.
I’ve watched enough on-chain dramas to know that speed matters. During one eleven-minute window the attacker’s SOL balance jumped by roughly 2,595 tokens. That alone was worth close to two hundred seventy-seven thousand dollars at the prices of the moment. An anonymous tracker later listed one hundred twenty-five distinct sending accounts. Individual transfers ranged from a few dollars in USDC all the way past twenty-six thousand USDT.
Avici’s Official Response Stayed Carefully Limited
Almost two hours after the first on-chain activity, the project posted a short statement. They said they were aware of an issue affecting card balance withdrawals and were monitoring the situation. They added that they were working with partners and would share more information when it became available. That was it. No confirmation of the total loss. No admission that an exploit had occurred. No mention of how many users felt the impact.
We’re aware of an issue affecting card balance withdrawals and are closely monitoring the situation.
Users had already started posting about missing balances before the company spoke. One person wrote that their entire Avici balance disappeared while they waited for any official word. That kind of silence tends to fuel more worry than a quick, transparent update.
Several practical questions remain open. Has the activity actually stopped? Did the team pause the programs? Will affected users see any form of reimbursement? And the biggest one for many people: were any signing keys or administrative accounts compromised?
Self-Custody Claims Meet An Awkward Reality
Avici has always described its product as a self-custodial wallet linked to a secured Visa credit card. The App Store listing still says users remain in control and that the company never holds their funds. In practice customers deposit crypto into collateral accounts and receive a matching credit limit. When they spend, the available card balance drops and the collateral is later used for settlement.
The fact that an outside party could add an administrator and then withdraw unspent collateral raises an obvious tension with that marketing language. If the authorization system accepts signature submissions that allow a new admin to drain funds, then the control users thought they had is thinner than advertised.
In my view the most interesting part is not the dollar amount. It is the gap between the product description and the on-chain behavior. A technical post-mortem from the team or an independent firm will need to explain exactly why those signature submissions were accepted. Until then the self-custody claim sits in an uncomfortable gray zone.
Upgradeable Programs And Shared Authority
Both of the Avici programs involved in the incident were upgradeable. They also shared the same upgrade authority. Reports indicate that authority was a standard Solana account rather than a multisignature setup. No one has shown that the upgrade authority itself was used in the withdrawals, yet the single point of control still draws attention.
Security researchers have been saying for months that operational controls matter as much as code audits. Compromised keys, signers, and infrastructure accounted for the large majority of value stolen in the second quarter of 2026. Only a small fraction of projects combined formal audits, active bug bounties, and continuous third-party monitoring. Avici’s situation may eventually fit into that broader pattern, or it may turn out to be something else entirely.
Either way, the incident stayed inside Avici’s own programs. Nothing points to a flaw in the Solana base layer itself. That distinction is worth keeping clear when the conversation inevitably drifts toward “Solana security” headlines.
AVICI Token Reaction Was Immediate And Harsh
While the on-chain activity was still unfolding, the AVICI token began sliding. Within twenty-four hours it was down 49.4 percent and printed a new all-time low near 0.2175 dollars. Market capitalization shrank to roughly 2.84 million. Trading volume for the period reached about 656,543 dollars. Most of that volume moved through MetaDAO’s futarchy automated market maker, with smaller amounts on a handful of other venues.
The token had once reached 7.56 dollars back in November 2025. The new low left it almost 97 percent below that peak. For a project that raised money through a capped token sale only ten months earlier, the price action was a harsh reminder of how quickly sentiment can reverse when trust is questioned.
Avici Inc. is a United States company with a San Francisco address and Delaware incorporation. It offers separate card terms for American customers, which means eligible U.S. users have direct exposure to both the wallet and the secured card product. That geographic detail will matter if any regulatory or legal follow-up appears.
How The Token Sale Itself Looked
In October 2025 the project raised 3.5 million dollars through a capped MetaDAO sale. Contributors had pledged far more, around 34.23 million, but the cap forced the return of roughly 89.8 percent of the committed USDC. The offering priced AVICI at 0.35 dollars and implied a fully diluted valuation near 4.52 million. Ten million tokens were issued, representing about 77.5 percent of the total 12.9 million supply.
Those numbers feel distant now. A token that launched under a relatively tight valuation and then climbed hard has given back almost everything. Price alone never tells the full story of a product, yet it does reflect how the market is pricing the current uncertainty.
Why This Incident Feels Different From Typical Code Exploits
Most large DeFi losses still come from logic bugs or reentrancy paths that auditors somehow missed. This one looks more like an authorization problem. Someone was able to add administrators and then move collateral that users believed remained under their exclusive control. That shifts the conversation from “find the missing require statement” to “who actually controls the admin rights and how are signatures validated?”
I’ve found that the projects which survive these moments are usually the ones that publish a clear timeline, isolate the exact failure, and outline concrete steps for users. Silence or vague monitoring language tends to prolong the damage. Whether Avici chooses the first path or the second is still an open question at the time of writing.
Payment platforms that mix on-chain collateral with traditional card rails face a unique pressure. Users expect the convenience of Visa spending and the security language of self-custody at the same time. When the two promises collide, the marketing language gets tested in public.
Broader Context Around Crypto Card Security
Avici is not the only project trying to connect crypto balances to everyday spending. Other providers have floated similar models that keep funds on-chain until settlement. The shared challenge is making sure that “users remain in control” is more than a slogan. Authorization systems, upgrade paths, and key management all need to match the claim.
Recent industry data has shown that key compromise and infrastructure issues now dominate the loss statistics. Code audits still matter, but they are no longer the only line of defense. Continuous monitoring, bug bounties that actually pay, and multisignature controls for sensitive authorities have become table stakes rather than optional extras.
Perhaps the most practical takeaway for ordinary users is simple. Any platform that can unilaterally add an administrator to your collateral account is not delivering the pure self-custody experience many people assume they bought. Reading the fine print and watching on-chain behavior remains essential, even when the marketing looks polished.
What Users Can Do While Waiting For Clarity
If you still hold balances inside the platform, the first step is to watch official channels for any pause announcements or migration instructions. Moving remaining funds out, if the interface still allows it, is an obvious precaution. Documenting transaction histories and balances before further activity occurs can also help if any claims process appears later.
On the token side, the sharp price move already prices in a large amount of uncertainty. Whether that discount eventually proves temporary depends entirely on how thoroughly the team explains the root cause and restores confidence. Markets rarely wait patiently for incomplete answers.
For the wider Solana ecosystem the incident is a reminder rather than a systemic failure. The base layer performed as designed. The programs built on top of it are where the risk concentrated. That distinction will matter when the next round of security discussions begins.
Looking Ahead At Accountability And Recovery
Several outcomes remain possible. The team could release a detailed technical report that isolates a specific authorization flaw or compromised credential. They could announce a reimbursement plan funded by treasury or insurance. Or the investigation could stretch on while the token continues to trade at depressed levels. History shows that each path produces very different long-term results for both users and the project itself.
In my experience the projects that recover are the ones that treat transparency as an operational priority rather than a public-relations exercise. Publishing the exact sequence of calls, the affected program versions, and the corrective measures under review gives the community something concrete to evaluate. Vague monitoring language does not.
The Avici case also highlights a quiet shift in how attackers operate. Instead of hunting for obscure arithmetic bugs, some now focus on the edges of authorization and admin control. That approach can be quieter and, in the short term, more effective against systems that assume only the original user can ever act on a collateral account.
Key Lessons For Anyone Using Crypto Spending Products
- Self-custody language should be matched by on-chain behavior that actually prevents third parties from adding administrators.
- Upgradeable programs with single-key upgrade authorities introduce concentrated risk that users rarely see in marketing materials.
- Rapid token price reactions often reflect loss of trust faster than any official statement can address it.
- Operational security around keys and signers now accounts for a large share of industry losses.
- Waiting for complete information is reasonable, but leaving large balances inside an affected system while waiting carries its own cost.
None of these points are new. They simply become more urgent when more than a million dollars moves in a few hours and the token halves in price on the same day.
The story is still developing. On-chain trackers continue to monitor the attacker wallet. Users continue to post about missing balances. The project continues to say it is monitoring the situation. Until a fuller explanation appears, the gap between the self-custodial promise and the observed withdrawals remains the central unresolved tension.
For now the practical advice is the same as it has been after every similar incident: treat every new claim of pure self-custody with healthy skepticism, keep position sizes that you can afford to lose, and watch the actual transaction logs more closely than the press releases. The numbers that moved on August 28 already showed why that approach still makes sense.
Whether Avici ultimately rebuilds trust or becomes another case study in the limits of hybrid crypto-card designs will depend on the next set of disclosures. The on-chain evidence is already public. The explanation that matches that evidence is still missing. That is the part of the story that will matter most in the weeks ahead.
I’ve covered enough of these events to know that the first twenty-four hours rarely contain the full picture. Sometimes the root cause is a simple key compromise. Sometimes it is a more subtle interaction between signature verification and admin privileges. Until the team or an independent auditor publishes the details, every theory remains provisional. What is not provisional is the million-plus dollars that left user accounts and the nearly fifty-percent drop in the token. Those two facts are already settled.
In the meantime the broader conversation about how crypto spending products should handle authorization and collateral control is only getting louder. Projects that want to keep both the convenience of traditional cards and the security language of self-custody will need to demonstrate, not just declare, that the two can coexist. The Avici incident has made that demonstration more urgent for everyone watching.
One final observation. The attacker’s wallet showed a mix of successful and failed transactions. That pattern suggests the process was automated and running at scale rather than a series of carefully chosen manual drains. Automation of this kind is increasingly common and makes rapid response even more critical. The longer a vulnerable path remains open, the more accounts can be processed.
As of the latest available checkpoint the total still stood above one million dollars in SOL terms plus the stablecoin residual. Whether that number continues to climb or finally stops depends on actions that have not yet been publicly confirmed. Users, token holders, and outside observers are all waiting for the same thing: a clear technical account of how the administrator additions became possible and what has been done to close that path.
Until then the safest assumption is that any remaining collateral inside the affected programs carries elevated risk. That is not a prediction of further losses. It is simply the logical stance when the precise failure mode remains unpublished. Markets have already priced a large measure of that uncertainty into the token. The next meaningful move will likely arrive only after the missing explanation appears.
The Avici case will probably join a growing list of 2026 incidents that turned on authorization and operational controls rather than classic smart-contract bugs. Learning the specific details of each one still matters. Patterns only become visible when the individual stories are examined closely. This one is still incomplete, but the outline is already sharp enough to study.
