Predict.fun Confirms 400k USDT Theft and Full User Refunds
Predict.fun just owned up to a 400,000 USDT drain that hit user wallets without warning.
The Details Behind the Unauthorized Transfers
The platform released its preliminary findings on Oct. 27 and traced the losses to what looks like a compromised third-party API documentation site. No core Predict.fun systems were directly named, yet the result was the same — tokens moved out fast and the users holding them got caught short.
That kind of third-party exposure has shown up in other incidents this year. Wallets linked to documentation or support portals often sit outside the main security perimeter, and attackers know it. Predict.fun’s statement made clear the investigation is still running, but the firm moved quickly to promise full refunds in USDT once the dust settles.
Why This Matters for Active Traders
Traders noticed immediately.
Anyone who had funds sitting on the platform now faces a wait while refunds are processed. Prediction-market volumes have grown fast in recent months, and liquidity on smaller venues can vanish quickly when confidence takes a hit. This episode will likely push more volume toward bigger, better-audited exchanges in the near term.
The timing adds another layer. October has already delivered several security alerts across DeFi and related services. When one platform flags an API-related breach, traders start asking the same questions about every other service they touch. That ripple effect is what turns a 400,000 USDT loss into broader market caution.
Numbers and Next Steps
Four hundred thousand USDT is not market-moving money on its own, yet the precedent matters. Predict.fun has committed to covering the full amount, which will test its treasury and any insurance it holds. Users will want clear timelines and on-chain proof once the reimbursements begin.
So far the firm has not released wallet addresses or a full incident report. That leaves room for speculation until more data arrives. Traders watching similar platforms are already tightening withdrawal checks and reviewing API permissions they granted months ago.
Anyone using these platforms should keep position sizes reasonable — hacks like this don’t come with warnings.