hack or exploit

Floki Takes Trading Bot Offline Amid Exploit Investigation

28Importance
no updates 6h+Status
2News media
3Pieces
Published
Updated
Since then
2 new reports

Floki took its Telegram-based trading bot offline after discovering an exploit affecting user wallets, and the project said it is investigating the incident. It also said affected users will be moved to new secure wallets while remaining balances are handled as part of the response.

Key claims & sources

✓
Floki said it discovered an exploit affecting its trading bot wallets and took the bot offline while it investigates the incident.
✓
The team said it is working to protect remaining user funds, identify affected users, and move them to new secure wallets.
✓
Floki has taken its Telegram-based trading bot offline after discovering an exploit affecting user wallets.
✓
Affected users will receive new secure wallets, and remaining balances will be transferred as part of the containment process.

What it means

Telegram-based trading bots became a popular way to trade tokens directly from chat starting in 2023, with projects like Unibot and Banana Gun pioneering the model of custodial wallets tied to a bot interface. Floki, the memecoin project, built its own version, giving users deposit-based wallets controlled by the service rather than self-custodied keys. That custodial design, convenient but centralized, is exactly what failed when the exploit hit early this morning.

Users who deposited funds into the bot cannot trade or withdraw until Floki migrates them to the newly issued secure wallets, and the team first has to identify which accounts and balances were exposed. New deposits into bot wallets are barred to stop further losses. Traders who relied on the bot for fast in-chat swaps lose that access entirely, while holders who never used the bot are unaffected, and trust shifts to Floki's internal response rather than on-chain custody. (per thecryptoguardian.com)

A bot marketed for convenience inside Telegram still required users to hand private keys to a single custodian, the same model that doomed Unibot's 2023 exploit. Whether Floki's fix restores confidence or exposes a wider pattern of custodial trading bots mismanaging keys is contested among traders who favor speed over self-custody. Tools built for convenience on top of blockchains often reintroduce the very central point of failure that cryptocurrencies were designed to remove. (per thedefiant.io)

Floki's promised forensic report will determine how many wallets and how much value the exploit touched, and whether the migration to new secure wallets makes affected users whole. That disclosure, not yet dated, will show whether the bot resumes service or is retired. The outcome will also signal whether traders keep using custodial Telegram bots or push projects toward non-custodial trading tools that never hold user keys.

Market reaction i

FLOKIFLOKI it is the asset of the company or protocol in the event
first headline
-3.0% 2 h before
+1.6% 4 h after
$0.000021price at publication
12data points

The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Nov 5 17:17
+19 h 20 m
Nov 6 12:37
The Cryptocurrency Post context
Its angle: investigates, statement, describes; with quotes
+21 h 47 m
Nov 6 15:04
The Crypto Guardian echo
No new facts: infrastructure, establishing, compromised; with quotes

Other recent incidents

WhenWhat happenedFigure
2 days ago Degen Coin Flip · Smart contract vulnerability incident $10k
3 days ago FLOKI Trading Bot incident no figure in dollars
3 days ago TENDRIL · Swap Logic Flaw incident $550k
3 days ago $TENDRIL · Smart contract vulnerability incident $555k
5 days ago InsurancePool/CoreVault · Flash loan attack incident $112.3k

4285 incidents stored