$EDGEN is now live Welcome to the People-backed internet. Details of the claim & staking below

UNCX Vesting V2 Incident: Recap & Update On October 14, 2026, attackers exploited an accounting vulnerability in Smart Token Vesting V2 contracts deployed on four networks. The attacks involved a sequence of publicly accessible contract actions that caused discrepancies between pooled token balances and recorded shares, allowing attacker-controlled vesting positions to withdraw assets beyond their intended allocations. We have published a detailed incident report covering the technical sequence, affected tokens, confirmed on-chain movements, liquidation paths, and amounts associated with each impacted community. 🔗 Full incident report: uncx.network/vesting-inciden… We encourage affected users and anyone seeking a precise understanding of the incident to consult this report directly. 1. Confirmed Financial Overview Following our review of the available on-chain evidence, the figures identified to date are as follows: > Approximately $807,000 USD in total assets extracted and subsequently liquidated, either immediately or over time, based on the combined ETH and USDT proceeds. > Approximately $58,000 USD in ETH returned through the intervention of whitehat c0ffeebabe.eth and MEV operator Yoink, who successfully front-ran certain attacker transactions. The recovered funds relate specifically to $IMO on Base and $X on Ethereum Mainnet. We extend our appreciation to those who intervened and helped recover these assets. We have also seen a number of figures circulating online that do not align with the verified on-chain movements documented in our investigation. Some reports appear to repeat previously published estimates without independently validating the underlying transactions. For clarity, the figures above reflect the liquidation proceeds identified so far, rather than speculative valuations of the tokens involved. The full report provides a breakdown by token and network. 2. Investigation & Recovery Efforts The 48-hour window communicated to the remaining attackers has not yet expired at the time of this update. So far, we have received no response from them. The investigation remains ongoing. Relevant parties (which we will not mention as the investigation continues for confidentiality) have been made aware of the incident. We can also confirm that an affected protocol has independently filed a formal complaint with law enforcement. We will respect their privacy and will not disclose their identity. UNCX continues to review technical evidence, asset movements, returned funds, and potential next steps alongside legal counsel and other relevant advisers. 3. Current Contract Security Status The affected Smart Token Vesting V2 contracts do not use upgradeable proxies. As a result, the deployed contracts cannot be modified to re-enable vesting creation, and no new vesting positions will be ever accepted. The attack vectors used on October 14 can therefore no longer be reproduced through the creation of new vesting positions. Existing, unaffected vesting positions remain accessible, and tokens can continue to be withdrawn according to their scheduled releases. Importantly, LP lockers are entirely unaffected. Liquidity locking contracts across all supported protocols and networks were not impacted by this incident and continue to operate normally. 4. What Happens Next? Our immediate priorities remain the continued investigation of the incident, tracking the relevant on-chain movements and evaluating the available next steps with the appropriate parties. This process requires care and time. We ask affected users and the wider community for patience and understanding while this work continues. Verified updates will be shared through official UNCX communication channels whenever there are meaningful developments to report. At this stage, no individual outcome or specific timeline can be confirmed. We recognize the impact this incident has had on affected communities and remain committed to providing clear, factual, and transparent information throughout the process. The UNCX team.

UNCX Vesting V2: Security Incident Update Following the security incident affecting our Vesting V2 contracts across several chains earlier today, we want to share an update on the measures taken, the affected tokens, and what comes next. 1. Security measures and containment We have implemented several measures to prevent further exploitation of the affected contracts: > Introduced substantial flat fees exceeding 1,000 ETH per lock. > Removed all clients and contract interactions that previously allowed these fees to be bypassed. > Increased token fees to the maximum permitted by the Vesting V2 contracts (5%), making repeated vesting top-ups economically unviable. These measures are designed to prevent further exploitation through the identified methods. While our investigation and monitoring remain ongoing, we firmly believe we have taken the necessary steps available to us to contain the incident. 2. Scope of the incident As previously communicated, all LP lockers remain unaffected, across every protocol and chain supported by UNCX. The incident is isolated to UNCX Vesting V2. Our legacy vesting contracts are also unaffected and have undergone additional checks and review. The incident currently involves 10 tokens across 4 chains: Ethereum (6): $pepecoin, $EDGEN, $ZC, $X, $LO0P, $PAAL Base (1): $IMO BNB Chain (1): $BTCLE Robinhood Chain (2): $CASHCAT, $RKST 3. Next steps for affected projects and communities We are already in contact with most of the affected teams, communities or individuals impacted. We expect to share further guidance and next steps with affected teams this week. We will also publish a comprehensive incident report covering the technical findings, financials, and the details of our proposed recovery plan. Important: For all impacted tokens, we strongly advise against trading in the affected pools until further guidance is provided by the respective token teams. We will be coordinating directly with those teams over the coming days. 4. Investigation and recovery efforts Our investigation remains active, and we are coordinating with law enforcement and @seal911. To date, no funds have been returned by the attackers (primary and copycats) on any affected chain. We strongly encourage the responsible party to contact us directly to discuss a resolution. We understand the seriousness of this incident for affected projects, holders, and communities. Our immediate priorities remain preventing further exploitation, establishing the full extent of the impact, and working closely with affected teams toward a recovery plan. We will continue to communicate when any meaningful updates become available. Thank you for your patience. The UNCX Team