•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Huma Finance disclosed that a legacy V1 smart contract was exploited, leading to approximately 101,400 USDC in losses. The company said its current V2 system, which supports ongoing platform operations, was not affected by the incident.
According to Huma Finance, the attack targeted a legacy V1 contract—an earlier component of the protocol that predates the platform’s current infrastructure. The project did not confirm details on the attacker’s identity, the specific vulnerability exploited, or the method used to carry out the attack.
The approximate loss figure of 101,400 USDC was confirmed through Huma Finance’s own disclosure.
Huma Finance stated that its V2 system, which underpins current platform operations, was unaffected. The distinction between V1 and V2 reflects a migration to a newer contract architecture, leaving the older V1 contract as a separate, deprecated component.
Based on the project’s characterization, users interacting only with the current V2 contracts would not have been exposed to the vulnerability that resulted in the losses. However, the disclosure indicates that anyone with funds or token approvals tied to the legacy V1 contract may need to assess their exposure.
This “unaffected” status is based solely on Huma Finance’s statement. No independent audit or third-party confirmation of the V2 system’s security posture was referenced in the available disclosures.
The disclosed impact is described as limited to the legacy V1 contract. Users who have interacted only with the V2 platform would not have been directly affected, according to the information provided.
For participants who may have exposure to the V1 contract, the situation remains unclear. The available disclosure does not specify whether Huma Finance plans to reimburse affected users, pursue recovery of the stolen funds, or implement additional remediation steps.
Until further updates are released, the incident status is presented as provisional. The disclosure suggests that checking wallet approvals related to deprecated V1 contracts could be a precautionary step, though no specific guidance was issued.
The incident highlights a recurring decentralized finance risk: legacy smart contracts can remain active on-chain even after a protocol upgrades to a new version. Unlike traditional software, older deployed contracts generally cannot be taken offline unless they include explicit shutdown mechanisms.
This can leave residual risk if users have granted token approvals to a legacy contract that later proves vulnerable. In such cases, exploitation may occur long after the protocol’s development has moved to a newer version.
In this case, Huma Finance’s separation between V1 and V2 systems is presented as the factor that limited the damage, as reflected in the project’s documentation.
A legacy V1 smart contract was exploited. Huma Finance described it as an older version of the protocol’s infrastructure, not the current V2 system.
Approximately 101,400 USDC, according to Huma Finance’s disclosure.
No. Huma Finance stated that its V2 system was unaffected, and the claim had not been independently verified by a third-party audit at the time of reporting.
The available disclosure does not include information about reimbursement, fund recovery, or specific remediation plans. Users were advised to monitor Huma Finance’s official channels for updates.
Huma Finance did not issue specific guidance on this. However, revoking token approvals for deprecated contracts is generally considered a sound security practice in DeFi.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
Premium gym chains are entering a “golden era” that is ending or already in decline, as rising operating costs collide with shifting consumer preferences toward more flexible, community-based ways to exercise. Long-term memberships are shrinking, margins are pressured by higher rents and facility expenses, and competition from smaller, more personalized…
