Fit Crypto Explorer

Case File #88 examines exploits where funds moved despite private keys remaining secure across four crypto incidents.

19 min Listen to the original Episode page
Crypto SecurityWallet ExploitsBridge VulnerabilitiesSmart Contract RisksUser Education

Summary

Host US analyzes four security incidents—FluidKey, Gonka AI, LUKSO, and Optimizely—where attackers moved funds without stealing private keys. The episode highlights how compromised third-party tools, bridge authorization flaws, and backend service vulnerabilities enabled these exploits. Speakers emphasize that a valid cryptographic signature does not guarantee informed consent if users are tricked into signing malicious transactions. The discussion concludes with a reminder to review transaction details before signing and highlights HundredCoin's behavioral trading restrictions.

Key takeaways

  1. 1
    A valid signature is not always informed consent.

    US · 1:14

  2. 2
    100 coin on Avalanche C Chain. is built around a 100 hour holding restriction. Its public token description says buying 100 prevents selling or transferring those tokens during the holding window and describes similar restrictions around certain token interactions.

    US · 14:40

Episode sections

  1. 0:14 – 1:38

    Intro and Case File 88 Overview

    Host US introduces Crypto Weekly Recap Case File #88, focusing on security incidents where funds moved despite private keys remaining secure. The episode covers four cases: FluidKey, Gonka AI, LUKSO, and Optimizely, emphasizing that protecting keys is only the beginning of security.

  2. 1:38 – 4:26

    FluidKey Incident Analysis

    FluidKey, a privacy-focused self-custodial wallet, suffered an exploit on November 19th where attackers used a compromised third-party logging tool to prepare unauthorized transactions. At least $1.58 million was lost across six chains, though private keys never left user devices. FluidKey shut down services temporarily and released version 1.79.22 to block the vulnerability.

  3. 4:26 – 7:04

    Gonka Bridge Exploit and Recovery

    Gonka, a decentralized AI computing network, experienced a bridge exploit on November 18th where an attacker manipulated the signing key process to withdraw ~884,150 USDT, 648 USDC, and mint 22 million WGNK. Security researchers estimated ~$1.05 million in extraction. The attacker returned some funds, but the bridge remains shut down with no claims portal open.

  4. 7:04 – 9:58

    LUKSO Recovery Service Abuse

    LUKSO's email-based universal profile recovery service was exploited between November 17th and 18th, allowing an attacker to add unauthorized controllers to ~300 profiles. Approximately 1.4 million LYX were stolen and swapped for ~50 ETH (~$95,000). LUKSO disabled the vulnerable service and is working on reimbursement, stressing that the blockchain itself was not compromised.

  5. 9:58 – 12:22

    Optimizely Malicious Script Injection

    Attackers injected malicious JavaScript into Optimizely, a web experimentation service, affecting 178 organizations including Ledger's website. The code could replace crypto addresses and skimming payment cards. Report URI traced ~$7,000 to attacker wallets. Optimizely removed the code on November 16th, clarifying it was not an admin account takeover.

  6. 12:22 – 14:01

    Beginner's Corner: Prepare, Review, Sign

    The host explains the distinction between preparing a transaction (done by an app) and signing it (done by the user). A valid signature does not guarantee informed consent if the user is tricked into signing incorrect data. The key takeaway is to always review the destination, amount, network, and permissions before signing.

  7. 14:01 – 18:42

    HundredCoin Spotlight and Community Shout-outs

    The episode highlights HundredCoin on Avalanche C-Chain, which enforces a 100-hour holding restriction to discourage impulsive trading. The host notes this is not a cybersecurity shield but a behavioral tool. The segment concludes with community shout-outs to various creators, artists, and data providers like CoinMarketCap and CoinGecko.

Assets discussed

AssetKindStanceContext
USDCUSDCcryptoneutralThe attacker registered a new signing key on Ethereum, withdrew approximately 884,150 USDT and 648 USDC, and minted 22 million WGNK without corresponding backing.

“Stance” is how the speakers talked about the asset, not a recommendation.

Claims worth verifying

On November 19th, people using a self-custody wallet lost funds even though the private keys never left their devices.

US ·0:54

How to verify: Check FluidKey's official incident report or blog post published on November 20th detailing the Nov 19th event and key security status. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

At least $1.58 million reached wallets connected to the attacker during a roughly 36-minute period across six chains.

US ·2:17

How to verify: Review BitQuery on-chain research reports or public dashboards tracking the FluidKey exploit transactions. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

FluidKey exploited flaws in a third-party logging tool to obtain session data, which helped the attacker prepare unauthorized transfers.

US ·2:57

How to verify: Read FluidKey's critical explanation post-mortem published on November 20th identifying the specific third-party logging tool. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

Gonka's bridge accepted signatures from a manipulated signing key process, allowing withdrawal of ~884,150 USDT and 648 USDC.

US ·5:05

How to verify: Check Gonka's November 20th incident update and verify on-chain transactions on Ethereum for the specified stablecoin withdrawals. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

Primary source

The attacker minted 22 million WGNK without corresponding backing.

US ·5:25

How to verify: Verify the minting transaction on the Gonka blockchain or associated Ethereum contract records. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

Gonka reported the attacker returned 593.435 ETH to the Bridge Administration multi-signature wallet.

US ·5:45

How to verify: Check Gonka's incident update and verify the ETH transfer on Ethereum to the Bridge Admin multi-sig address. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

LUKSO reported the attacker added an attacker-controlled key as a controller on roughly 300 user profiles.

US ·7:24

How to verify: Review LUKSO's official post-mortem report detailing the scope of the recovery service compromise. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

Approximately 1.4 million LYX were taken from LUKO profiles and swapped for ~50 ETH valued at ~$95,000.

US ·7:59

How to verify: Check LUKSO's incident report for the stolen LYX amount and ETH value, and verify on-chain swap transactions. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

Optimizely attackers injected malicious JavaScript into 188 scripts associated with 178 organizations, including Ledger.

US ·10:26

How to verify: Review Report URI's incident report or Optimizely's official incident report listing affected organizations and script counts. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

Report URI traced about $7,000 to identified attacker crypto wallets on November 16th.

Unidentified speaker (UNKNOWN) ·11:26

How to verify: Check Report URI's documentation or public blockchain explorers for the traced transactions to attacker wallets. For recent events, verify 2026-08-21 through 2026-11-21. Use another period only when the speaker explicitly names it.

Primary source

Do your own research

  • Verify FluidKey's version 1.79.22 release notes and official statements regarding the November 19th exploit and third-party logging tool vulnerability.
  • Check Gonka AI's bridge documentation and official announcements for details on the BLS signing key manipulation and current status of the claims portal.
  • Review LUKSO's official communication regarding the email recovery service abuse, specifically the scope of the ~300 affected profiles and reimbursement plans.
  • Investigate Optimizely's incident report and Report URI data to confirm the extent of the JavaScript injection and its impact on affiliated organizations like Ledger.
  • Research BitQuery's on-chain analysis for the FluidKey incident to validate the $1.58 million loss estimate across the six affected chains.
  • Examine Gonka AI's on-chain transaction records to verify the reported return of 593.435 ETH and 12.9 million GNK and assess liquidity provider recovery.
  • Review HundredCoin's tokenomics and holding restriction mechanics on the Avalanche C-Chain to understand the behavioral trading limitations.
  • Confirm Ledger's official statement regarding the Optimizely script injection to verify if their admin accounts were compromised or if it was purely a frontend display issue.
Full transcriptexpand

0:14US: What's up family? Welcome back to Crypto Weekly Recap. I'm your host, US, your hard-working crypto sleuth, and this is where we break down the weekend crypto with a security first lens. Before we get into it, nothing on this podcast is financial advice. I'm not here to tell you what to buy, sell, or gamble with. This show is about education, security, market awareness, and survival. Crypto can change lives, but it can also punish carelessness fast. Do your own research, protect your wallets, slow down before signing anything, and never invest money you can't. afford to lose. We're opening case file number 88. The keys never left. So, how did the money move? Now, family, here's the detail that should make every crypto user pay attention. On November 19th, people using a self-custody wallet lost funds, even though, according to the wallet company, the private keys controlling their money never left their devices. Think about that for a second. A valid signature is not always informed consent. And that wasn't the only warning this week. A bridge accepted signatures it should never have trusted. A recovery service was used to add unauthorized controllers to hundreds of accounts, and a trusted website service

1:33delivered code that could swap a crypto address right in front of a visitor.

1:38Unidentified speaker (UNKNOWN): Our

1:38US: questions question this week is simple Who really controls a transaction? The person holding the key, the application preparing the request, or the permission that was granted long ago? Let's open the file. Our first story takes us to FluidKey, a privacy focused self custodial wallet service. The incident happened on November 19th. On November 20th, FluidKey published a critical explanation. of the failure and announced a new version of its app. FluidKey helps users receive money through fresh, privacy preserving addresses. Behind the scenes, it uses smart account technology and a service called a relayer to prepare and submit transactions. According to on chain research from BitQuery, at least $1.58 million reached wallets connected to the attacker during a roughly 36-minute period. The researchers tracked transfers across six chains. That is a researcher-attributed estimate, not a final audited loss number published by FluidKey. Here's what FluidKey itself said: The attacker exploited flaws in a third-party logging tool to obtain session data. That access helped the attacker prepare unauthorized transfers on FluidKey's Fluid Key's servers. When a user opened the application, those transfers could be signed. The company specifically stated that

2:57the private keys controlling user funds never left the device. The risk was in the transaction workflow, information collected by a supporting service, an application preparing actions, and the wallet signing something that did not reflect the user's intention. Fluid FluidKey Key shut down its service. services on the 19th and said there were no further unauthorized transactions after 1805 Coordinated Universal Time.

3:22Unidentified speaker (UNKNOWN): On

3:22US: November 20th, it brought its web, iOS, and Android services back online with version 1.79.22. It said older versions would remain offline and that the new release blocked the reported method. A full post mortem was still pending at our evidence cutoff. If you use FluidKey, don't follow a stranger's recovery link. Go through the project's verified official channel, confirm the updated version, review your transaction history, and contact legitimate support if anything looks wrong. FluidKey also warned that its team would not privately approach users on social media to fix their wallets. If you don't use FluidKey, Fluid Key, the lesson still applies. A self-custodial key can stay local while another layer of your security breaks down. Learn whether your wallet prepares transactions on your device or through a connected service. Check the actual recipient, amount, network, and permissions whenever your signing interface gives you that information. If the action looks unfamiliar, don't approve it.

4:25Unidentified speaker (UNKNOWN): Our

4:26US: second story is a bridge incident involving Gonka, a network associated with decentralized artificial intelligence computing and its connection to Ethereum. On November 18th, someone manipulated the bridge's signing key process. Normally, validators on Gonka produce a group signature to authorize releasing assets on Ethereum. The Ethereum bridge uses a mechanism called BLS and relies on the current group key to decide whether a withdrawal or minting request is valid. If an attacker can make the bridge trust the wrong key, the bridge may accept a forged story about what happened on the other chain. Gonka's November 20th incident update says the attacker manipulated the key generation process and obtained valid signatures outside the normal on-chain on chain signing workflow. The attacker registered a new signing key on Ethereum, withdrew approximately 884,150 USDT and 648 USDC, and minted 22 million WGNK without corresponding backing. Security researchers initially estimated about $1.05 million dollars was extracted across the incident. That estimate is not a second loss. to add to the stablecoin outflows. There is also an important recovery update. Gonka reported that the

5:45attacker returned 593.435 ETH to the Bridge Administration multi-signature wallet and more than 12.9 million native GNK to the community pool on November 19th. Those are reported return transfers, not proof that every affected user, liquidity provider, or market participant was made whole. And here's the part too many people miss. The bridge remained shut down. Gonka warned that the Ethereum contract itself could not be paused and might still be misused. The project told people not to use the bridge, buy or trade WGNK GNK or send assets to that contract. It also said there was no claims portal open. It was considering a replacement bridge and independent audit, with no relaunch date confirmed. So, what should a listener do? Before using a bridge, find out whether it is operating normally and who is responsible for authorizing withdrawals. If that bridge has an active incident warning, stop. If you were are exposed, preserve your transaction records, review official instructions, and be suspicious. of anybody claiming to offer an urgent refund or recovery portal. The big question is not just whether a contract has passed an audit. Ask who can change the keys and who validates the evidence a contract trusts. Because a

7:04smart contract can execute exactly as written and still accept bad authorization if the trusted signing process is compromised. Now let's move from bridge keys to recovery. permissions. Our third case involves Luxo and its email based universal profile recovery service. Between November 17th and 18th, an attacker exploited a weakness in the recovery service's back end. According to Luxo's own post mortem, the attacker gained control of recovery profiles and used use that position to add an attacker attacker-controlled controlled key as a controller on roughly 300 user profiles. A controller is a key or account that has specific authority over a smart contract-based profile. If those permissions include the ability to move assets, an unauthorized controller can cause real damage without ever knowing your original secret phrase. Luxo reported that about 1.4 million LYX were taken. The project said the tokens were bridged to Ethereum and swapped. producing approximately 50 ETH, valued in its report at around $95,000. That is the described disposition of the stolen tokens, not another loss to add to the LYX amount. Luxo also made several distinctions that matter.

8:18Unidentified speaker (UNKNOWN): It

8:18US: said the blockchain itself was not compromised. The universal profile smart contracts worked as designed.

8:25Unidentified speaker (UNKNOWN): The

8:25US: company reported new no exposure of users' private keys or recovery phrases. The failure was in the service and the authorization that service could exercise.

8:35Unidentified speaker (UNKNOWN): The

8:35US: team switched off the vulnerable email recovery system, stopped additional affected profiles from being created through that route, and began decommissioning the service. It said it was working toward a reimbursement solution. Here's an important action for anyone using that route. recovery method. Luxo's official incident instructions tell affected users to remove the attacker's controller key and remove the recovery service controller or its permission to add new permissions. The instructions also recommend making a secure profile backup. Use the official Luxo post mortem to reach the appropriate tools. Never enter a recovery phrase into a site sent by someone who. claims to be support. This case connects to the rise of AI agents, automated trading tools, and wallet assistance. But I want to be precise. This Luxo incident was not reported as an AI agent compromise. The connection is a security principle, not a shared attack method.

9:32Unidentified speaker (UNKNOWN): When

9:33US: you give an agent, bot, recovery provider, or automation tool permission to act, you are expected to

9:38Unidentified speaker (UNKNOWN): be able to be able to be

9:38US: able extending your trust beyond your own key. My rule is least privilege. Give a tool only the access it needs for only as long as it needs it. Review controllers, allowances, sessions, and API credentials according to the wallet or service you're using. And if you retire an automation, remove the access it no longer needs. Our fourth story is the one that makes the phrase. I checked the website, a lot less comforting.

10:06Unidentified speaker (UNKNOWN): On

10:06US: November 16th, attackers managed to place malicious JavaScript into a web experimentation service called Optimizely. That code was served through legitimate websites. Security researcher Scott Helm and the report URI team identified 188 affected scripts associated with 178 organizations. including the Ledger website. Now hold on to this distinction. The research does not mean Ledger's hardware wallet devices were hacked or that every visitor to every affected site lost money. It means malicious software was delivered through a third-party website component that legitimate sites were using.

10:46Unidentified speaker (UNKNOWN): In

10:46US: its own incident report, Optimizely said the attacker exploited a flaw in. the account signup flow to impersonate users and insert malicious project JavaScript. It said this was not an Optimizely administrator account takeover or evidence that customer passwords have been stolen through the incident. Optimizely also said the injected code was removed and its delivery blocked on November 16th. What could the malicious code do? Report URI documented cryptocurrency address replacement, payment card skimming, collection of accessible cookies and screenshots, and attempts to deliver exploit kits to certain iPhones and iPads.

11:26Unidentified speaker (UNKNOWN): The

11:26US: code could replace a wallet address displayed on a page, in a form, or even when copied and pasted. Report URI traced about $7,000 to identified attacker crypto wallets at one point. on November 16th. Not a complete final victim loss estimate. An attempted mobile exploit does not prove that every targeted phone was compromised.

11:48Unidentified speaker (UNKNOWN): The

11:48US: practical defense is to treat the payment details, not the website's reputation, as the last checkpoint. Use an address from a separately verified channel when possible. Compare the entire destination against a trusted source. not only the first four and last four characters. Check the network and amount. Use wallet or device transaction verification when available. And never let urgency talk you out of checking.

12:15Unidentified speaker (UNKNOWN): If

12:15US: you entered card data on a page that was affected during the exposure period, contact your card issuer for advice.

12:22Unidentified speaker (UNKNOWN): If

12:22US: you signed an unexpected wallet transaction, inspect it on a block explorer. and evaluate approvals or permissions relevant to that transaction. If you've simply visited an affected site, that alone does not establish that your wallet was drained. Keep your browser and operating system updated, especially if your device may have been exposed to a web exploit attempt. It's time for beginner's corner. Our topic is the difference between preparing a transaction and signing one. Let's make it simple. Suppose you walk into a store and tell the cashier you want to pay $20. The cashier fills out a payment form for you. You sign it. But imagine the form actually says $200 and you never look at the amount. Your signature may be valid even though the payment wasn't what you intended. A crypto wallet works with a similar distinction. An application may prepare the request, which chain, which token, which amount, which recipient, and which contract action. Your wallet then signs data that authorizes the transaction. On-chain systems can verify that a signature is valid. They cannot automatically know whether the application tricked you or whether you misunderstood what you approved. Remember these three words: prepare, review, sign. Somebody prepares the transaction. You

13:41review what you're actually authorizing. Then and only then you sign. Here's your one action for today. Before your next crypto transaction, deliberately check the destination address, the amount, the network, and whether you're sending assets or granting permission. If your wallet cannot make the request understandable, cancel and investigate. before proceeding. A signature proves that an authorized key signed some data. It does not prove that the human owner understood that data. And now, family, let's bring this week's lesson home with the 100 coin spotlight. We've talked about how a few seconds of misplaced trust can turn into a permanent transaction. That's why I keep coming back to patience. 100 coin on Avalanche C Chain. is built around a 100 hour holding restriction. Its public token description says buying 100 prevents selling or transferring those tokens during the holding window and describes similar restrictions around certain token interactions. The idea is to interrupt impulsive activity and encourage people to think beyond the next candle. Here's the connection I want you to make. A restriction on moving a particular token can change the pace of trading that token, but it's not a universal cybersecurity shield. It does not stop somebody from stealing your wallet's seed phrase. It

15:00does not make other assets in your wallet immune to theft. It does not automatically fix a compromised website, a malicious approval, or an unsafe bridge. And, because it restricts transfers, it may also limit how quickly you can be. move 100 during an emergency. Know the contract rules and the implications before using it. What you can take from that mechanic, whether or not you hold the token, is a habit. Give yourself a security review window. Verify the token contract from a reliable project source. Confirm the network. Understand the approvals you're about to grant. Keep a clean backup and know what you would. do if the app you use suddenly posted an incident warning.

15:42Unidentified speaker (UNKNOWN): If

15:42US: you want to learn about the project, hundredcoin.io is the starting point. My challenge to the family this week: before your next wallet connection, take 100 seconds to verify what you're doing. Security is utility, patience is a practice. Keep it 100. Before we wrap up this week's episode, I want to tell you take a moment to recognize the people and communities who make this journey worthwhile. First, a huge thank you to BSG the Millionaire Maker for continuing to build a community centered around education, patience, and long term thinking. Thanks as well to CryptoWalk and CryptoKato for consistently creating content that helps people learn and stay engaged. A special shout out goes to everyone helping keep the 100 coin community welcoming and informed, including Base Steve, Love Hundred, Admin, Void Warlocker, Bad Bunny, Missionary, Satoshi's Brother, Q Crypto Money, Boss Lady, Garfield, Richard, JC, iBoost Morale, Montrell, Rookie, Vladdy, Uptown Sigma, Jason, Steve, Lisa, Sibia. Sarah, Enrico, Arjun, Etienne, Stewart, Keisha, AP, Corey, Alice, and Gabriel. I'd also like to recognize the incredible

17:02artists and creators behind the art team, whose work helps bring our community to life every single week. Outside the 100 Hundredcoin coin ecosystem, thank you to the teams at CoinMarketCap and CoinGecko for providing market data and educational resources that millions of crypto users rely on every day. A big shout out as well to the R Weave community for continuing to push decentralized permanent storage forward. And to the wallet teams behind MetaMask, On-Chain Wallet, and Trust Wallet for continuing to improve self-custody tools for everyday users. And finally, thank you to everyone listening to Crypto Weekly Recap. Whether you've been here since episode one or this is your very first episode, I appreciate you spending part of your week with me. Every download, every comment, every review, every share, and every conversation helps grow this community and spreads one simple message: security comes before hype. If you'd like to learn more about 100Coin, visit 100coin.io. Join the community. ask questions, and participate in the conversations. There's always room for one more person who's willing to learn. Until next week, keep it 100. That's the recap for this week, family. Remember, crypto security is operational security. Protect your keys, your validators, your bridges, and

18:21your AI agents. Slow down before you trust. Slow down before you sign. Slow down before you automate. Stay patient. Stay disciplined. Stay dangerous to scammers. Keep it 100. If you enjoyed this episode, subscribe, share, and leave a review. It helps more people learn how to stay safe.

This page was produced automatically: the audio was transcribed with nvidia/parakeet-tdt-0.6b-v3+sortformer-v2.1 and interpreted by Qwen3.6-35B-A3B-UD-IQ3_S.gguf. Transcription and interpretation can contain errors; always confirm against the original episode. Nothing here is investment advice.
All insights