The decentralized exchange YapeSwap has reportedly suffered a security exploit resulting in a loss of approximately $56,900. According to security monitoring data from SlowMist, the incident occurred on October 25, 2026, and was made possible by a critical vulnerability within the protocol's governance mechanism. The attacker successfully manipulated the system to gain administrative permissions, allowing for the unauthorized redirection of funds through malicious contract deployments.
Zero Quorum Vulnerability in WorkersUnion
The technical analysis reveals that the root cause of the breach was a logical flaw in the WorkersUnion governance mechanism. Specifically, the system operated with a zero quorum requirement, meaning there was no minimum threshold of participation required for a proposal to be considered valid and executable.
- The attacker initiated a governance proposal with a mere 0.000055 units of voting power.
- Due to the lack of quorum restrictions, the proposal was passed despite nearly non-existent community participation.
- The proposal successfully transferred the feeToSetter permission of the YapeFactory contract directly to the attacker.
Execution of the Malicious Registry Attack
Once the attacker gained administrative control over the YapeFactory, they moved to compromise the protocol's asset management layer. By deploying a malicious Registry contract, the exploiter was able to manipulate how the system identified legitimate storage locations for user funds.
While the vaults() function continued to list the authentic vault addresses, the attacker modified the latestVault() function to return a forged address under their control. This discrepancy caused YapePair to credit transferred deposits as farm assets without receiving the corresponding redeemable shares. The technical interaction between YapeFactory, YapePair, and YapeWrapp was central to the execution of this financial drain.
The YapeSwap incident highlights a growing trend of "governance attacks" in the DeFi ecosystem, where minor technical oversights in voting logic can lead to total protocol compromise. As of now, the affected funds remain linked to the attacker's address, and users are advised to exercise caution when interacting with the protocol's smart contracts until a formal patch or migration is confirmed by the development team.
Frequently Asked Questions
Quick answers to the most common questions about this topic.