UNCX Lockers

Fully decentralized multi-chain service provider since 2020. Creators of liquidity locking 🛡️

Making DeFi safer & easier. ➡️

[UNCX Lockers @UNCX_token]

@scheinerino As posted here, process in motion regarding the October incident.

Projects will update their respective communities in due time, no doubt there.

https://t.co/Ae5eETOHbp

[UNCX Lockers @UNCX_token]

Final Public Vesting Incident update

Following the October 14 Vesting V2 incident, we would like to share the following (positive) updates with our users:

1. Voluntary Recovery Program

The UNCX Foundation has stepped in and established a voluntary ex-gratia relief program aimed at providing affected projects with full recovery (subject to a maximum cap) of the realized proceeds from liquidated stolen assets.

This voluntary initiative is subject to legal, compliance, and eligibility reviews on a case-by-case basis.

Validation procedures, timelines, and next steps are currently being finalized and will be communicated directly to the affected projects.

2. Vesting Service

Our team is actively working on patching, strengthening, and enhancing our Vesting smart contracts in order to re-enable the service.

The service will be re-enabled once the necessary security improvements and validations have been completed and audited.

Existing users with vested positions can release their tokens as per their respective schedules.

As previously communicated, all LP Locker products and the remainder of the UNCX ecosystem continue operating as usual.

3. Security & Infrastructure Updates

Earlier today, our platform experienced a brief period of downtime as we deployed additional security updates addressing various externally disclosed vulnerabilities that have emerged over recent days and hours (independent from our incident or UNCX, but worth noting we made the necessary about external dependencies too).

4. Moving Forward

We remain fully committed to supporting our growing user base, continuously strengthening the products we build, and delivering reliable services to the ecosystem.

Our focus remains unchanged: security, resilience, transparency, and continuous improvement.

We appreciate the continued trust and patience of our community during the last week.

The UNCX Team

[UNCX Lockers @UNCX_token]

Quick PSA for UNCX users, we will be migrating our docs.

[GitBook @GitBookIO]

The GitBook app, the GitBook API, and published docs are available again. A few services may still be degraded as we finish restoring everything to full performance.

More information: https://t.co/XB0dpebJUo
Live updates: https://t.co/1HKKPqpkO8

[UNCX Lockers @UNCX_token]

@helloSQD 🤝

[UNCX Lockers @UNCX_token]

Just use @helloSQD

Besides the tech which we recommend to read about (case study, their docs, etc), the team and its support is outstanding.

We're happy to connect you with their team, feel free to let us know.

[sqd.ai @helloSQD]

.@UNCX_token rebuilt its data stack three times. Every reindex on The Graph took weeks.

Then they bought 1M $SQD on the open market, locked it, and spun up their own Portal.

This is what real utility looks like. https://t.co/q47rmg6tgm

[UNCX Lockers @UNCX_token]

Final Public Vesting Incident update

Following the October 14 Vesting V2 incident, we would like to share the following (positive) updates with our users:

1. Voluntary Recovery Program

The UNCX Foundation has stepped in and established a voluntary ex-gratia relief program aimed at providing affected projects with full recovery (subject to a maximum cap) of the realized proceeds from liquidated stolen assets.

This voluntary initiative is subject to legal, compliance, and eligibility reviews on a case-by-case basis.

Validation procedures, timelines, and next steps are currently being finalized and will be communicated directly to the affected projects.

2. Vesting Service

Our team is actively working on patching, strengthening, and enhancing our Vesting smart contracts in order to re-enable the service.

The service will be re-enabled once the necessary security improvements and validations have been completed and audited.

Existing users with vested positions can release their tokens as per their respective schedules.

As previously communicated, all LP Locker products and the remainder of the UNCX ecosystem continue operating as usual.

3. Security & Infrastructure Updates

Earlier today, our platform experienced a brief period of downtime as we deployed additional security updates addressing various externally disclosed vulnerabilities that have emerged over recent days and hours (independent from our incident or UNCX, but worth noting we made the necessary about external dependencies too).

4. Moving Forward

We remain fully committed to supporting our growing user base, continuously strengthening the products we build, and delivering reliable services to the ecosystem.

Our focus remains unchanged: security, resilience, transparency, and continuous improvement.

We appreciate the continued trust and patience of our community during the last week.

The UNCX Team

[UNCX Lockers @UNCX_token]

Affected teams have been in direct contact with us since October 14.

The UNCX Foundation has since established a voluntary ex-gratia payment program, offering 100% recovery of liquidated realized stolen proceeds to the affected ETH projects mentioned in your post, subject to legal, compliance, and eligibility checks (validation and timeline/next steps is being addressed as we speak).

We reject attempts to misrepresent our incident response or shift the narrative.

The voluntary recovery process is clear and will require KYC/KYB verification.

Something in the above hints you won't be eager to show faces.

[UNCX Lockers @UNCX_token]

Comments have been turned off for this post on purpose to avoid misinformation, phishing attempts, and other types of 'AI slop' responses which do not provide added value.

Our team remains available using direct channels.

Thank you for understanding.

[UNCX Lockers @UNCX_token]

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: https://t.co/9BlSWtZKi0

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 Lockers @UNCX_token]

UNCX Vesting V2 - Base chain Update

We can confirm that the funds affected on Base have been fully returned to the $IMO project (@IMO__Invest)

The address specifically involved on the Base chain was operated by white-hat c0ffeebabe.eth. The return was completed following coordination/verification with both parties.

Thanks to @seal_911 for their swift action and coordination throughout this recovery.

Our post-mortem analysis, and communications with the remaining addresses are ongoing within the 48-hour window. No further updates for now.

Recovery transaction:
https://t.co/X4W6EgV3Jg

[UNCX Lockers @UNCX_token]

UNCX Vesting V2 - Update

We have contacted two addresses directly on-chain, offering a 10% white-hat bounty in exchange for the return of the remaining 90% of the funds obtained through the exploit.

A third address has been contacted directly via Blockscan Chat, and we are coordinating with @SEAL_911 regarding another address currently holding funds.

We have established a dedicated recovery email address, [email protected], and a recovery multisig to facilitate the secure return of funds within the next 48 hours.

We are continuing to consolidate transaction data, assess the full impact, and verify figures before publishing a comprehensive incident report. We appreciate your patience as this process continues.

Please rely exclusively on this account for official, verified updates.

For parties holding affected funds, and to verify the authenticity of our on-chain recovery messages, our designated recovery multisig address is:

0x32f0eB068fD804195629A2CBEE30A7e9CE58c4cb

We will share further updates as verified information becomes ready to be published.

[UNCX Lockers @UNCX_token]

UNCX Vesting V2 - Update

We have contacted two addresses directly on-chain, offering a 10% white-hat bounty in exchange for the return of the remaining 90% of the funds obtained through the exploit.

A third address has been contacted directly via Blockscan Chat, and we are coordinating with @SEAL_911 regarding another address currently holding funds.

We have established a dedicated recovery email address, [email protected], and a recovery multisig to facilitate the secure return of funds within the next 48 hours.

We are continuing to consolidate transaction data, assess the full impact, and verify figures before publishing a comprehensive incident report. We appreciate your patience as this process continues.

Please rely exclusively on this account for official, verified updates.

For parties holding affected funds, and to verify the authenticity of our on-chain recovery messages, our designated recovery multisig address is:

0x32f0eB068fD804195629A2CBEE30A7e9CE58c4cb

We will share further updates as verified information becomes ready to be published.

[UNCX Lockers @UNCX_token]

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

[UNCX Lockers @UNCX_token]

@0xBudderr We will be in touch with on-chain addresses holding funds, and ideally will establish contact prior to our next report.

Thank you for the post, and patience

[UNCX Lockers @UNCX_token]

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

[UNCX Lockers @UNCX_token]

Incident noticed.

As an immediate first measure we're currently preventing further vesting positions to hit the contract which shall allow us to review the transactions and next steps for impacted users.

Flat fees on all vesting contracts have been put to 100 ETH or equivalent.

Will update shortly.

[Blockaid @blockaid_]

🚨 Blockaid detected an ongoing exploit on @UNCX_token on ethereum.

~$86k drained from the shared vesting pool so far across 1 drain tx. Attack still ongoing. 🧵

[UNCX Lockers @UNCX_token]

We will show you this month. Real Markets.

[Chav @Chav_UNCX]

Our take: you can not try to fight the AMM literally every step of the way.

The only way to truly innovate and 'invent something new', is to remove the AMM as we know it entirely. And.. that's precisely what we have done.

whether you give us the mic or not, we'll show you

[UNCX Lockers @UNCX_token]

@moonbag New primitive will change the game. Mark these words Ray!

[UNCX Lockers @UNCX_token]

Max pain is when you take the trade. Anything that happens after that is a net positive.

Max pain on the primary market is 2%. I would take that trade every single day.

[Chav @Chav_UNCX]

Max pain is when you take the trade. Anything that happens after that is a net positive.

Max pain on the primary market is 2%. I would take that trade every single day.

[UNCX Lockers @UNCX_token]

@MessierM87 Just lock it. Oh wait, you did already 🔒🔒🔒

[Chav @Chav_UNCX]

those who know us definitely also know we have skin in the game and do not value vaporware

very promising so far.

[UNCX Lockers @UNCX_token]

Good morning to the UNCX userbase. We have good news.

@arc > we have just rolled out our smart vesting suite on the chain.

Teams can now vest, lock, distribute, stream, airdrop directly on Arc.