<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Onchain Diary</title>
        <link>https://paragraph.com/@onchaindiary</link>
        <description>Real-time risk scoring for any wallet address or token. Detect scams, honeypots, and malicious contracts across 10+ chains — powered by GoPlus, Etherscan, and OKX.</description>
        <lastBuildDate>Fri, 20 Nov 2026 21:19:05 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Electrum's Server Swapped the Transaction, Then the Fee Bump Made You Sign It]]></title>
            <link>https://paragraph.com/@onchaindiary/electrum-server-swapped-transaction-fee-bump</link>
            <guid>xDvtjzSrRbBEoKMmQtLw</guid>
            <pubDate>Mon, 26 Oct 2026 17:41:35 GMT</pubDate>
            <description><![CDATA[On October 24, 2026, Electrum shipped version 4.8.3. The release notes are short, the version number is unremarkable, and the reason it exists is one of the more uncomfortable failure modes in self-custody: a wallet that never leaked a private key still paid an attacker, because the owner signed a transaction the wallet had been tricked into displaying. Electrum published a security advisory the same day, GHSA-6jp4-8v48-cc5v, rated High, with no CVE assigned. Affected versions are everything ...]]></description>
            <content:encoded><![CDATA[<p>On October 24, 2026, Electrum shipped version 4.8.3. The release notes are short, the version number is unremarkable, and the reason it exists is one of the more uncomfortable failure modes in self-custody: a wallet that never leaked a private key still paid an attacker, because the owner signed a transaction the wallet had been tricked into displaying.</p><p>Electrum published a security advisory the same day, GHSA-6jp4-8v48-cc5v, rated High, with no CVE assigned. Affected versions are everything before 4.8.3. Two users had already reported it privately, and one of them lost money.</p><h2 level="2" textAlign="left" id="h-what-actually-happened">What actually happened</h2><p>Electrum is a light client. It does not download the whole Bitcoin blockchain. It asks a server for balances, history, fee estimates and mempool contents, then verifies only what it can verify cheaply. Confirmed transactions get SPV-checked against block headers. Unconfirmed transactions, by design, are taken on trust. The Electrum documentation has said so for years.</p><p>An attacker took that documented trust and turned it into a trap. The sequence, as described in the advisory:</p><ol><li><p>You broadcast a normal payment, call it tx1.</p></li><li><p>The malicious server swallows it and does not relay it to the network.</p></li><li><p>The server updates your wallet history with a different transaction, tx2, whose outputs point to an address the attacker controls.</p></li><li><p>tx2 has invalid signatures. Your wallet does not check signatures on unconfirmed transactions from the server, so it displays tx2 as a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/pending-transaction/">pending transaction</a>.</p></li><li><p>You see a stuck payment and decide to bump the fee. Electrum&apos;s fee bump signs the transaction it believes is pending, which is tx2.</p></li><li><p>Your wallet signs tx2 properly, with a higher fee. The network accepts it. The attacker gets paid.</p></li></ol><p>The signature is valid. The transaction is real. It just is not the transaction you thought you were approving.</p><h2 level="2" textAlign="left" id="h-the-four-character-trick">The four-character trick</h2><p>The advisory records a detail that makes this far more practical than it sounds. In both reported cases, the attacker&apos;s address was ground so that its last four characters matched the last four characters of the legitimate recipient address. Short address comparisons, the kind people do when a payment is already late, stop working.</p><p>In the second report, the substituted transaction paid zero fee. That is not an accident. A zero-fee transaction sits in the mempool looking stuck, which is exactly the condition that makes a user reach for the fee bump button. The trap was built around the user&apos;s next click.</p><h2 level="2" textAlign="left" id="h-timeline">Timeline</h2><p>The advisory lists it plainly:</p><ul><li><p>October 11, 2026: the first user reports a transaction replacement privately, without realising the fee-bump path.</p></li><li><p>October 18, 2026: a second user, Raju-K12, reports losing money after approving a fee bump.</p></li><li><p>October 23, 2026: version 4.8.3 is tagged with the fix.</p></li><li><p>October 24, 2026: binaries are released and the advisory goes public.</p></li></ul><p>The stolen amount has not been disclosed. The first reporter noticed the swap before signing anything; the second did not.</p><h2 level="2" textAlign="left" id="h-what-483-changes-and-what-it-does-not">What 4.8.3 changes, and what it does not</h2><p>The fix is commit <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/spesmilo/electrum/commit/90fe30822561e515a9d2d6e5a352cc07780999eb">90fe308</a>. Electrum now verifies signatures on the inputs that spend the wallet&apos;s own coins before accepting an unconfirmed transaction into its local history. If the parent transaction is already known, the fake transaction is rejected with <code>InvalidTxSignature</code> before it can replace anything. If the parent arrives later, the spending transaction is removed. The commit also handles a subtler point: a txid does not commit to witness data, the same quirk behind <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/transaction-malleability/">transaction malleability</a>.</p><p>That closes the path used here. It does not turn Electrum into a full node. The client still validates only <code>is_mine</code> inputs, meaning transactions paying into your wallet from elsewhere are still not script-verified. The advisory says covering those inputs would require recursively validating unconfirmed parents until reaching mined transactions, which is a consensus engine&apos;s job, not a light client&apos;s.</p><p>So the boundary has moved, not disappeared. Your wallet now refuses to build a fee bump on top of a fake spend of your own coins. It still trusts a server for a good deal of what it shows you.</p><h2 level="2" textAlign="left" id="h-what-to-do">What to do</h2><p>Upgrade to 4.8.3, from electrum.org, and verify the GPG signatures. Then change two habits.</p><p>First, treat every signature as a fresh decision. A fee bump is not a maintenance action. It is a new transaction spending the same coins, and it deserves the same address check as the original payment. Open the details, read the outputs, compare the full address, not the first and last four characters.</p><p>Second, if you hold meaningful amounts, run your own Electrum server. The attack requires a server that lies. A server you control, reached over Tor or a private link, removes that capability from a third party. This is the same lesson as the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-mediamarkt-implant-europe/">Ledger supply-chain mess</a>: the weakest point in self-custody is rarely the key storage, it is the path between what the device signs and what you believe you asked for.</p><p>Hardware wallets remain a real defense here, and for a specific reason. When Electrum hands a transaction to a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/hardware-wallet/">hardware wallet</a>, the device displays the recipient and amount on its own screen. A swapped output address, including the four-character lookalike, has to survive that screen too. Users who blind-sign whatever the host sends lose that check, which is why <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/blind-signing-explained/">blind signing</a> keeps showing up in these incidents.</p><h2 level="2" textAlign="left" id="h-the-uncomfortable-part">The uncomfortable part</h2><p>Electrum did not have a bug in the usual sense. It had a trust assumption, documented, known, and load-bearing for millions of users. The attacker did not break cryptography. They read the manual and built a user interface that lied at exactly the moment the user was paying attention to fees instead of addresses.</p><p>That is the pattern worth carrying away. In <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/address-poisoning-attacks-explained/">address poisoning</a>, the attacker poisons your history so the wrong address looks familiar. Here, the attacker poisons your pending list so the wrong transaction looks like yours. Both are <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/phishing-attack/">phishing</a> aimed at the same human shortcut: we verify once, then trust the screen.</p><p>Electrum 4.8.3 makes the screen slightly more honest. It cannot make the habit for you.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/electrum-server-swapped-transaction-fee-bump/"><em>https://theonchaindiary.com/articles/electrum-server-swapped-transaction-fee-bump/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/544d514778ab6f8b1b41b8bc910c79087b90fb0b8398320bd8c73043cfafd4cb.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[A Sui Bridge Claim Bot Just Paid the Cetus Hacker — 17 Months After the Freeze]]></title>
            <link>https://paragraph.com/@onchaindiary/sui-bridge-claim-bot-cetus-hacker</link>
            <guid>UjG86Sn7xrfxZPJ8KNOL</guid>
            <pubDate>Tue, 20 Oct 2026 08:00:56 GMT</pubDate>
            <description><![CDATA[At 04:39:35 UTC on October 16, 2026, Ethereum block 26,202,756 processed a Multicall3 bundle that finalized fifteen stale positions in one transaction. Most belonged to ordinary users who had forgotten to claim bridge withdrawals months earlier. Five of them did not. Three transactions later, 86 ETH, 109,000 USDT and 0.9 WBTC had been delivered to 0x89012a55cd6b88e407c9d4ae9b3425f55924919b — the Ethereum address that public incident analyses have attributed to the Cetus attacker since May 202...]]></description>
            <content:encoded><![CDATA[<p>At 04:39:35 UTC on October 16, 2026, Ethereum block 26,202,756 processed a Multicall3 bundle that finalized fifteen stale positions in one transaction. Most belonged to ordinary users who had forgotten to claim bridge withdrawals months earlier. Five of them did not.</p><p>Three transactions later, 86 ETH, 109,000 USDT and 0.9 WBTC had been delivered to <code>0x89012a55cd6b88e407c9d4ae9b3425f55924919b</code> — the Ethereum address that public incident analyses have attributed to the Cetus attacker since May 2025. The submitter was not the hacker. It was an automated &quot;unclaimed funds&quot; bot run under the ENS name <strong>lostandfound.eth</strong>, whose stated business is finishing other people&apos;s stuck withdrawals and asking for a 5–10% tip.</p><p>The incident was first reconstructed in detail by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://sigintzero.com/blog/sui-bridge-392k-stale-withdrawal-claim-bot">SigIntZero</a> and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://dev.to/pandasecurity/sui-bridge-claim-bot-sent-392k-to-the-cetus-attacker-1ikb">PandaSecurity</a>, and we independently re-verified every transaction, amount and the wallet&apos;s current state on Etherscan before writing this. Here is what happened, why the freeze never covered this money, and what it says about how bridges handle the aftermath of an exploit.</p><h2 level="2" textAlign="left" id="h-what-the-sui-bridge-claim-bot-actually-did">What the Sui Bridge Claim Bot Actually Did</h2><p>The bot&apos;s externally owned account, <code>0x7f2ee458d58e61345ad61a70e8072511bf9f6671</code>, submitted three Multicall3 bundles between 04:39:35 and 04:40:11 UTC. Decoding the bridge&apos;s <code>TokensClaimed</code> events — both research teams did this, and the raw transfers confirm it — the attacker-linked deliveries were:</p><table class="paragraph-table"><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Transaction</p></th><th colspan="1" rowspan="1"><p>Time (UTC)</p></th><th colspan="1" rowspan="1"><p>Assets delivered</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>0x89ca33…dde89</code></p></td><td colspan="1" rowspan="1"><p>04:39:35</p></td><td colspan="1" rowspan="1"><p>84 ETH (3 × 28) + 93,000 USDT + 0.9 WBTC</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>0xce494e…36ac</code></p></td><td colspan="1" rowspan="1"><p>04:39:59</p></td><td colspan="1" rowspan="1"><p>16,000 USDT (2 × 8,000)</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>0xe63cb0…1fc8</code></p></td><td colspan="1" rowspan="1"><p>04:40:11</p></td><td colspan="1" rowspan="1"><p>2 ETH</p></td></tr></tbody></table><p>Every <code>TokensClaimed</code> event carries the same 32-byte sender — the attacker&apos;s Sui address <code>0xe28b50cef1d633ea43d3296a3f6b67ff0312a5f1a99f0af753c85b8b5de8ff06</code> — and the same recipient on Ethereum. The two signals that would have identified these claims as attacker funds were sitting in the event data the whole time. Nobody looked.</p><p>The same bundles also settled legitimate stale withdrawals for unrelated users, including a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/smart-contract/">WithdrawQueue</a> position that burned ezETH and an Optimism portal withdrawal. That is the point: this was a general-purpose &quot;finish what others left unfinished&quot; bot, and the attacker&apos;s messages simply looked like more stale funds — same shape, same vault, no face.</p><p>The $392K figure deserves a caveat both write-ups also make: it comes from the operator&apos;s own on-chain message, which priced each asset at claim time. The token amounts are on-chain fact; the dollar total is an estimate.</p><h2 level="2" textAlign="left" id="h-sixty-seconds-on-the-cetus-hack">Sixty Seconds on the Cetus Hack</h2><p>On May 22, 2025, Cetus — then the largest concentrated-liquidity DEX on Sui — was <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cointelegraph.com/news/cetus-dex-sui-exploit-200m-loss">drained of roughly $220 million</a> through an arithmetic overflow in its liquidity math (the same class of bug we cover in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/integer-overflow-attacks-explained/">integer overflow attacks</a>). <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://slowmist.medium.com/slowmist-analysis-of-the-230-million-cetus-hack-ee569af040f2">SlowMist&apos;s teardown</a> put the haul at over $230M across pools; other tallies landed between $220M and $223M.</p><p>Within hours, Sui validators took the extraordinary step of freezing the attacker&apos;s on-chain accounts — about $162M <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.dlnews.com/articles/defi/sui-validators-votes-hack-the-cetus-hacker-and-return-160m/">by DL News&apos; accounting</a> — and the community later <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.sui.io/blog/cetus-incident-response-onchain-community-vote">voted through a protocol upgrade</a> that moved the frozen funds into a recovery multisig without the hacker&apos;s signature. Victims were eventually made close to whole.</p><p>That response is remembered as a success. It is. But it had a blind spot, and this month the bill for that blind spot came due.</p><h2 level="2" textAlign="left" id="h-ten-bridge-deposits-one-claim-and-a-nine-message-time-bomb">Ten Bridge Deposits, One Claim, and a Nine-Message Time Bomb</h2><p>Here is the part that matters for bridge security, and the reason this story is about architecture rather than one careless operator.</p><p>On the day of the exploit, the attacker bridged funds off Sui toward Ethereum. SigIntZero&apos;s query of the bridge&apos;s deposit events shows <strong>ten transfers, all made on May 22, 2025</strong>, all naming the attacker&apos;s own Ethereum address as recipient — nonces 7020 through 7034.</p><p>At 11:12 UTC, the attacker claimed exactly one of them: 3,000 USDT, nonce 7034 (we confirmed the inbound transfer and the outbound move eight minutes later on Etherscan). Then it stopped. The <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/cross-chain-bridge/">bridge committee</a> paused the Ethereum contract at 12:52 UTC and unpaused it at 22:13 the same night.</p><p>Why the attacker took one small transfer and left nine larger ones on the table is not in the public record — rate limits, the pause, or simple distraction are all plausible, and SigIntZero rightly refuses to guess. What is on record is the result: once the bridge reopened, nine approved messages remained valid claims on the vault, payable to the attacker, executable by anyone, forever.</p><h2 level="2" textAlign="left" id="h-how-the-claim-works-a-bearer-instrument-with-the-payee-written-on-it">How the Claim Works: A Bearer Instrument With the Payee Written On It</h2><p>The Ethereum side of Sui Bridge finalizes a Sui-to-Ethereum transfer through <code>transferBridgedTokensWithSignatures()</code>: anyone can submit a message plus enough committee signatures, and the contract pays the <strong>recipient encoded in the message</strong> — never the submitter. PandaSecurity&apos;s write-up walks the code path in detail.</p><p>Think of an approved bridge message as a bearer instrument with the payee already written on it. Whoever walks up to the counter with a valid note gets it processed, and the vault pays the name on the note. That design is sound and common — it is what makes <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/bridge/">bridge</a> claims censorship-resistant and keeps users&apos; funds from being stranded if a relayer dies. The <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/nonce/">nonce</a> prevents replay; each message settles exactly once.</p><p>The catch is that &quot;safe for the user&quot; assumes the recipient <em>should</em> be paid. When the recipient is an exploiter, a permissionless claim is a one-way valve that anyone in the world can open — a rescue bot, an <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/mev-bot/">MEV bot</a> hunting gas refunds, or a script run by anyone at all. The Sui validator freeze could not touch these messages: claiming them requires nothing from the frozen Sui address, because the committee&apos;s signatures had already left Sui attached to the message.</p><h2 level="2" textAlign="left" id="h-the-bot-even-asked-the-hacker-for-a-tip">The Bot Even Asked the Hacker for a Tip</h2><p>The detail that turns this from an accident into an absurdist artifact: at 04:42 UTC, under three minutes after the last claim, the bot did what it does for every wallet it &quot;helps.&quot; It sent an on-chain message to the attacker listing the eight unclaimed amounts, describing them as bridge transfers &quot;that were approved but never claimed,&quot; and suggesting an optional tip of 5% to 10% — somewhere between $19,598 and $39,196 by the bot&apos;s own arithmetic, requested from an address that had been publicly identified as the Cetus attacker for 17 months.</p><p>Then it added, of the funds: &quot;The funds are already in your wallet; there is nothing to approve.&quot;</p><h2 level="2" textAlign="left" id="h-youre-right-our-mistake">&quot;You&apos;re Right, Our Mistake&quot;</h2><p>The first person to notice was not the operator, Cetus, Sui, or Tether. It was a stranger. At 05:08 UTC, an address signing as <strong>tanuki42</strong> messaged the bot on-chain that its claims had sent roughly $390K of stale Sui Bridge withdrawals to &quot;an address publicly associated with the Cetus exploit.&quot;</p><p>Thirty minutes later the operator replied on-chain: &quot;you&apos;re right, our mistake.&quot; The reply acknowledged the operator had not known the recipient was the Cetus attacker, noted nothing had moved yet, asked for help routing the case to Tether and Cetus so the USDT could be frozen, and said the bot now screens every recipient against known exploit and sanctioned addresses.</p><p>To the operator&apos;s credit, the response was fast, public, and on-chain. But the ordering is the story: the screening existed only after a random bystander supplied it.</p><h2 level="2" textAlign="left" id="h-we-checked-the-chain-ourselves-including-an-update-neither-write-up-has">We Checked the Chain Ourselves — Including an Update Neither Write-up Has</h2><p>Per our own verification standard for on-chain forensics, we re-ran the numbers on Etherscan before publishing:</p><ul><li><p>All three claim transactions exist at the stated times, sent by the bot EOA via Multicall3, delivering exactly 86 ETH, 109,000 USDT and 0.9 WBTC to <code>0x89012a55…919b</code> — matching both write-ups to the token.</p></li><li><p>The May 22, 2025 self-claim of 3,000 USDT (nonce 7034) is visible in the wallet&apos;s token-transfer history.</p></li><li><p><strong>New as of October 20:</strong> both published analyses (October 16–19) reported the address <em>not yet</em> on Tether&apos;s on-chain blacklist. Our direct contract call to USDT&apos;s <code>getBlackListStatus()</code> today returns <strong>true</strong> — Tether has since blacklisted the address. The 109,000 USDT (still in the wallet, per its balance) is now frozen in place, which is the freeze the bot operator asked for on October 16. The 0.9 WBTC also remains in the wallet; native ETH, of course, cannot be blacklisted by anyone.</p></li></ul><p>In other words: the one asset here with an issuer-level kill switch is now contained. The rest is not, and never can be.</p><h2 level="2" textAlign="left" id="h-the-delivery-nobody-noticed">The Delivery Nobody Noticed</h2><p>SigIntZero&apos;s reconstruction surfaced something neither the operator nor the bystanders caught: this was actually the <em>second</em> time someone delivered the attacker&apos;s stale claims.</p><p>Of the ten May 2025 bridge messages, the bot settled eight in October 2026. The tenth — nonce 7029, 1 LBTC — was claimed back on August 31, 2025, paid to the attacker&apos;s Ethereum address, by a submitter (<code>0xCa8d0B47…839B</code>) whose transaction history mixes committee-signed pause operations with many claim submissions. SigIntZero reads it as a relay account; whether that August delivery was deliberate or one more unscreened item in a queue is not public. Either way, someone other than the attacker moved Cetus proceeds out of the bridge 14 months before anyone flagged it.</p><p>With all ten messages now settled, nothing from that Sui address is left to claim. The time bomb has fully detonated.</p><h2 level="2" textAlign="left" id="h-why-dormant-is-not-safe">Why Dormant Is Not Safe</h2><p>It is tempting to file this under &quot;operator error&quot; and move on. Three broader lessons say otherwise, and they apply far beyond this bridge.</p><p><strong>1. Dormant is not the same as safe.</strong> After an exploit, incident response chases funds that are moving. Signed-but-unexecuted messages get none of that attention, yet they are live liabilities — anyone, at any time, can turn them into spendable assets. The same holds for queued withdrawals, pending governance actions, and approvals that never expire. PandaSecurity drew the parallel to the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/near-intents-hack-explained/">NEAR Intents hack</a>, where balances that looked inert turned out to be withdrawable through the same &quot;nobody checked whose money this was&quot; pattern.</p><p><strong>2. Permissionless relaying moves the screening burden off-chain.</strong> When a protocol lets anyone finalize anything, the protocol does no screening — so whatever screening exists lives in the relayers. A careful relayer can be undone by a careless one. &quot;Nobody will bother&quot; is not a control.</p><p><strong>3. Recovery tooling is security-sensitive software.</strong> Read-only &quot;what can I claim?&quot; checkers are harmless. A bot that <em>executes</em> claims on others&apos; behalf is a payment system with no compliance checks, and it deserves the same threat model as any contract that moves value.</p><h2 level="2" textAlign="left" id="h-what-bridge-teams-and-relayer-operators-should-do">What Bridge Teams and Relayer Operators Should Do</h2><p>For protocol and bridge teams, the concrete additions to an incident-response runbook:</p><ol><li><p><strong>Enumerate attacker-linked pending messages as part of the freeze.</strong> When you pause and freeze after an exploit, list every signed-but-unexecuted outbound message from attacker addresses and decide its fate — committee hold, coordinated issuer freeze at the destination, or explicit burn — before an outside bot decides for you.</p></li><li><p><strong>Consider a delay-list on the claim path.</strong> A narrowly scoped, governance-controlled list that <em>delays</em> (rather than permanently blocks) claims involving known exploit addresses preserves permissionless relaying for everyone else. It trades against censorship resistance, so it must be governed transparently — but &quot;no check at all&quot; is what just paid a hacker $392K.</p></li><li><p><strong>Expose message provenance clearly.</strong> The source-chain sender and recipient were in the claim events all along. Make them impossible to miss in explorer views, so relayers and monitors can screen.</p></li></ol><p>For anyone running a relayer or recovery bot: screen both ends of every transfer, cap what can be claimed without human review, and fail closed when your screening source is unavailable. The check is one API call. The October 16 incident is what skipping it looks like.</p><h2 level="2" textAlign="left" id="h-timeline">Timeline</h2><table class="paragraph-table"><colgroup><col><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>#</p></th><th colspan="1" rowspan="1"><p>When (UTC)</p></th><th colspan="1" rowspan="1"><p>Actor</p></th><th colspan="1" rowspan="1"><p>What happened</p></th></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>2025-05-22, morning</p></td><td colspan="1" rowspan="1"><p>Cetus attacker</p></td><td colspan="1" rowspan="1"><p>Drains Cetus pools (~$220M), starts moving proceeds off Sui</p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>2025-05-22, before 11:12</p></td><td colspan="1" rowspan="1"><p>Cetus attacker</p></td><td colspan="1" rowspan="1"><p>Locks 10 transfers in Sui Bridge (nonces 7020–7034), self as recipient</p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>2025-05-22, 11:12</p></td><td colspan="1" rowspan="1"><p>Cetus attacker</p></td><td colspan="1" rowspan="1"><p>Claims one message (3,000 USDT, nonce 7034), leaves nine</p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>2025-05-22, 12:52</p></td><td colspan="1" rowspan="1"><p>Bridge committee</p></td><td colspan="1" rowspan="1"><p>Emergency pause on the Ethereum contract</p></td></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>2025-05-22</p></td><td colspan="1" rowspan="1"><p>Sui validators</p></td><td colspan="1" rowspan="1"><p>Freeze ~$162M on Sui; already-signed bridge messages untouched</p></td></tr><tr><td colspan="1" rowspan="1"><p>6</p></td><td colspan="1" rowspan="1"><p>2025-05-22, 22:13</p></td><td colspan="1" rowspan="1"><p>Bridge committee</p></td><td colspan="1" rowspan="1"><p>Unpause; the nine unclaimed messages are claimable by anyone</p></td></tr><tr><td colspan="1" rowspan="1"><p>7</p></td><td colspan="1" rowspan="1"><p>2025-08-31</p></td><td colspan="1" rowspan="1"><p>Relay account</p></td><td colspan="1" rowspan="1"><p>Claims nonce 7029 (1 LBTC) to the attacker&apos;s address</p></td></tr><tr><td colspan="1" rowspan="1"><p>8</p></td><td colspan="1" rowspan="1"><p>2026-10-16, 04:39–04:40</p></td><td colspan="1" rowspan="1"><p>lostandfound.eth bot</p></td><td colspan="1" rowspan="1"><p>Submits the remaining eight in three multicalls, no recipient check</p></td></tr><tr><td colspan="1" rowspan="1"><p>9</p></td><td colspan="1" rowspan="1"><p>2026-10-16, 04:42</p></td><td colspan="1" rowspan="1"><p>Bot</p></td><td colspan="1" rowspan="1"><p>On-chain note to the attacker suggesting a 5–10% tip</p></td></tr><tr><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>2026-10-16, 05:08</p></td><td colspan="1" rowspan="1"><p>tanuki42</p></td><td colspan="1" rowspan="1"><p>Flags the recipient as the Cetus exploiter</p></td></tr><tr><td colspan="1" rowspan="1"><p>11</p></td><td colspan="1" rowspan="1"><p>2026-10-16, 05:38</p></td><td colspan="1" rowspan="1"><p>Bot operator</p></td><td colspan="1" rowspan="1"><p>&quot;Our mistake&quot; — adds recipient screening, asks for a USDT freeze</p></td></tr><tr><td colspan="1" rowspan="1"><p>12</p></td><td colspan="1" rowspan="1"><p>by 2026-10-20</p></td><td colspan="1" rowspan="1"><p>Tether</p></td><td colspan="1" rowspan="1"><p>Blacklists the address; 109,000 USDT frozen in place (our on-chain check)</p></td></tr></tbody></table><h2 level="2" textAlign="left" id="h-the-bottom-line">The Bottom Line</h2><p>Nobody hacked anything on October 16. A contract executed valid messages, exactly as written, and paid a sanctioned-in-spirit recipient because the only party positioned to notice — an automated middleman — had no idea whose money it was moving, and even the &quot;rescue&quot; tip request went to the hacker.</p><p>The uncomfortable takeaway for every chain that has ever frozen attacker funds: a freeze covers what attackers still control. It says nothing about claims attackers have already signed and abandoned. Those are open valves on the other side of the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/cross-chain-bridge/">cross-chain bridge</a>, waiting for the first bot — helpful or otherwise — to turn them. If your incident response ended at the freeze, it ended too early.</p><p>For users, the practical echo is the same one from our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/bridge-security-explained/">bridge security guide</a>: abandoned claims are valuable, and tooling around them will find them before you do. If you have old, unclaimed bridge transfers anywhere, claim them or cancel them — because someone else eventually will.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/sui-bridge-claim-bot-cetus-hacker/"><em>https://theonchaindiary.com/articles/sui-bridge-claim-bot-cetus-hacker/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/6a1999518bed3664f450603f74e2b6d9f72ef3a6c529347ee75a1b88ef07a345.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[The Task Scammer Who Lost 60 BTC to a Tampered Ledger Wallet]]></title>
            <link>https://paragraph.com/@onchaindiary/ledger-task-scammer-loses-60-btc</link>
            <guid>PtdVUhjHg576zdQJo6Us</guid>
            <pubDate>Tue, 20 Oct 2026 08:00:49 GMT</pubDate>
            <description><![CDATA[The most quoted line of the Ledger investigation didn't come from Ledger. It came from Chainalysis, on October 15: "One of the biggest victims of the Ledger theft was a scammer themselves. They lost more than 60 BTC, about $4.8M. The funds were from a task scam." — Chainalysis It's a satisfying twist, and the internet enjoyed it. But the details Chainalysis attached to that line matter more than the irony, because they sit right at the intersection of two crime streams — and they quietly cont...]]></description>
            <content:encoded><![CDATA[<p>The most quoted line of the Ledger investigation didn&apos;t come from Ledger. It came from Chainalysis, on October 15:</p><blockquote><p>&quot;One of the biggest victims of the Ledger theft was a scammer themselves. They lost more than 60 BTC, about $4.8M. The funds were from a task scam.&quot; — <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/chainalysis/status/2110748973971468382">Chainalysis</a></p></blockquote><p>It&apos;s a satisfying twist, and the internet enjoyed it. But the details Chainalysis attached to that line matter more than the irony, because they sit right at the intersection of two crime streams — and they quietly contaminate every clean-sounding loss estimate you&apos;ve read about this incident.</p><h2 level="2" textAlign="left" id="h-seventeen-days-between-deposit-and-drain">Seventeen days between deposit and drain</h2><p>Per Chainalysis&apos;s disclosure, the transaction pattern reads like this:</p><ul><li><p><strong>The money&apos;s origin:</strong> a task scam. People were recruited to fake sales and reviews of real products, paid small real amounts at first. Then a &quot;negative balance&quot; appeared in their accounts, and they were told to add their own money to unlock the earnings they thought they had built up. That&apos;s the deposit phase — the phase where the scam actually earns. (We broke down the full mechanics, including the money-mule variant, in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-task-scam-money-mule/">Crypto Task Scams Explained</a>.)</p></li><li><p><strong>September 22:</strong> the operator moved the accumulated proceeds through a consolidation wallet and into three separate Ledger addresses — roughly $1.64M each, per the flow chart Chainalysis shared (via <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://decrypt.co/381141/scammer-lost-4-8m-in-bitcoin-to-tampered-ledger-wallets-chainalysis">Decrypt</a>).</p></li><li><p><strong>October 9:</strong> thieves emptied all three addresses — one transfer each, into the same receiving wallet, which Chainalysis notes is already reported as holding stolen funds. The same morning, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-cryptobilis-supply-chain-hack/">hundreds of other wallets were swept</a> in a coordinated burst.</p></li></ul><p>Put differently: the scammer did everything a cautious holder is told to do. Moved significant value into <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/hardware-wallet/">hardware wallets</a>, split across three addresses, and then waited. It didn&apos;t matter. If the devices themselves were implanted before they reached the buyer, the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/seed-phrase/">seed phrase</a> was likely harvested during setup — 24 words read off the screen and transmitted over a mobile network, per Ledger&apos;s security lab — and no amount of address-splitting protects keys the attacker already has.</p><p>One caveat worth keeping precise: Ledger has said all <em>confirmed</em> losses trace to devices sold through Southeast Asian reseller CryptoBilis, but <strong>Chainalysis did not say where this operator bought the devices</strong>. The channel attribution for this particular victim is inference from the pattern, not a stated fact.</p><h2 level="2" textAlign="left" id="h-the-contaminated-loss-estimate">The contaminated loss estimate</h2><p>Here is the part that outlives the schadenfreude.</p><p>The Ledger incident&apos;s total estimated losses run from about $86M (onchain investigator Specter — a figure Ledger explicitly has not verified) to $93M–$102M across roughly 324 wallets and six chains (Bitquery&apos;s tally). Those numbers get repeated as &quot;stolen from users.&quot;</p><p>The 60 BTC case proves the pool is not that simple. Some of the &quot;user funds&quot; in those wallets were themselves scam proceeds — money that already belonged to task-scam victims before the Ledger thieves took it from the scammer. Chainalysis made the point directly: the trace doesn&apos;t stop at the victim wallet; it continues upstream to whoever ran the fake-review payout loop.</p><p>Three practical consequences fall out of that:</p><ol><li><p><strong>Recovery math gets murky.</strong> If law enforcement claws back funds from the attacker&apos;s collection addresses, some of the recovered value arguably belongs to task-scam victims two hops upstream — people who may never file a claim, because task-scam victims often don&apos;t realize (or won&apos;t admit) they were scammed.</p></li><li><p><strong>Screening contamination spreads downstream.</strong> Any address that later receives a hop of that 60 BTC inherits a taint flag. As Chainalysis&apos;s thread notes, legitimate users who unknowingly receive a downstream fragment get a hit on screening tools they didn&apos;t earn.</p></li><li><p><strong>Headline totals need an asterisk.</strong> &quot;Stolen from victims&quot; and &quot;stolen from criminals&quot; are mixed in the same estimate. That doesn&apos;t make the theft smaller — it makes the victimology mixed, which is exactly the kind of detail that gets lost when a number becomes a headline.</p></li></ol><h2 level="2" textAlign="left" id="h-two-crime-economies-one-supply-chain">Two crime economies, one supply chain</h2><p>The case is a neat demonstration that the crypto underground isn&apos;t one industry — it&apos;s at least two, and they eat each other.</p><p>The task-scam economy runs on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/social-engineering/">social engineering</a>: recruit, pay small, freeze, extract deposits. The supply-chain implant economy runs on hardware trust: buy a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/supply-chain-attack/">legitimate distribution channel</a>, modify genuine devices so they pass authenticity checks, harvest seed phrases at scale, and wait for balances to build before a coordinated sweep.</p><p>The scammer&apos;s 60 BTC sat in those three wallets for 17 days. That&apos;s not a smash-and-grab on a hot wallet — it&apos;s patient infrastructure that treats every victim equally, whether the funds are life savings or laundered scam revenue. For anyone keeping score at home: the thieves who built the implant operation out-executed the scammer who ran the task funnel, and both out-executed the people who thought a hardware wallet was the last security decision they had to make.</p><p>Hardware wallets remain a good idea. The lesson of this incident — as with the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-drain-address-poisoning/">address-poisoning cases</a> we&apos;ve documented from the same investigation — is that the device is one link in a chain that includes every hand it passed through between the factory and your desk. Buy from the manufacturer directly. Verify the reseller is actually the reseller. And treat any device that arrived through an unfamiliar channel as untrusted until proven otherwise.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-task-scammer-loses-60-btc/"><em>https://theonchaindiary.com/articles/ledger-task-scammer-loses-60-btc/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/51541feb7ce5344ed93411731b777671c5b6477a94429efa144c9d824497d386.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Ledger Implants Reach European Retail: Two MediaMarkt Devices, One 'Eurasian Version' Antenna]]></title>
            <link>https://paragraph.com/@onchaindiary/ledger-mediamarkt-implant-europe</link>
            <guid>faX5QClHE4d9O2iAkzuJ</guid>
            <pubDate>Tue, 20 Oct 2026 08:00:41 GMT</pubDate>
            <description><![CDATA[The scariest supply-chain attack of 2026 just crossed a border it wasn't supposed to cross. On October 9, wallets drained through devices sold by CryptoBilis, an authorized Ledger reseller in Southeast Asia — a case we traced in depth after Malaysian corporate records showed the reseller had been quietly acquired in March. That story had a shape: buy a trusted distributor, implant its stock, harvest seeds for months, sweep in one night. Ugly, but containable. One reseller, one region, one pla...]]></description>
            <content:encoded><![CDATA[<p>The scariest supply-chain attack of 2026 just crossed a border it wasn&apos;t supposed to cross.</p><p>On October 9, wallets drained through devices sold by CryptoBilis, an authorized Ledger reseller in Southeast Asia — a case we traced in depth after Malaysian corporate records showed the reseller had been quietly acquired in March. That story had a shape: buy a trusted distributor, implant its stock, harvest seeds for months, sweep in one night. Ugly, but containable. One reseller, one region, one playbook.</p><p>Then Europe answered.</p><h2 level="2" textAlign="left" id="h-update-october-13-15-donjon-explains-the-mechanism-and-it-is-screen-interception">Update, October 13-15: Donjon explains the mechanism, and it is screen interception</h2><p>Ledger&apos;s own security team broke its silence. In an update on X, Ledger Donjon described how the CryptoBilis implants actually work: an added microcontroller watches the display when the device generates or shows the 24-word recovery phrase, recognizes the words in real time as they appear on screen, and sends them out through an embedded LTE module with its own eSIM (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/Ledger/status/2109896739985453358">Ledger on X</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.coindesk.com/tech/2026/10/13/ledger-says-spy-chip-inside-cryptobilis-ledger-devices-transmitted-wallet-keys-over-mobile-network">CoinDesk</a>). The implant is independent hardware: it never touches the Secure Element, never modifies firmware, never participates in signing — which is exactly why Ledger&apos;s Genuine Check and integrity self-tests see nothing wrong. The most sensitive component stays cryptographically intact while the most human moment of setup, the words on the screen, is where the theft happens.</p><p>German tech publisher Heise, drawing on teardown analysis by Tibane Labs, gave the technique its proper name: an <strong>embedded TEMPEST</strong> attack — intercepting the signals that travel to the screen, in the classic TEMPEST tradition, except soldered inside the device instead of picked up from outside (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.heise.de/en/news/Crypto-thieves-sell-hardware-wallets-with-secret-eSIM-11485188.html">Heise</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.tibane.net/research/ledger-nano-x-implant">Tibane Labs</a>). Tibane Labs also catalogued three implant generations: a hand-modified first generation presented by Joe Grand in May (smaller replacement battery, conspicuous wiring), a more professional second generation that still swapped the battery, and a third built with series-production precision cuts that keeps the original battery — with the extra hardware hidden in space created by scratching away the foam that shields the screen from below. Open the case and it looks like an untouched Nano X, apart from one thin antenna wire.</p><p>Two practical consequences. First, Ledger&apos;s own advice for CryptoBilis buyers in the last three months: do not use the wallet, move holdings to a trusted device. Second, the detection lesson generalizes: software checks cannot see added hardware. If your threat model includes a tampered supply chain, the countermeasure is buying from the manufacturer directly — not running a check on the device itself.</p><h2 level="2" textAlign="left" id="h-update-october-16-the-warnings-came-before-the-crisis">Update, October 16: the warnings came before the crisis</h2><p>The part of the timeline that matters most for accountability arrived via <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cointelegraph.com/news/ledger-early-implant-warnings-mark-karpeles">Cointelegraph on October 16</a>: Ledger was hearing about implanted devices privately long before October 9. Mark Karpelès told the outlet he is aware of at least two people who contacted the company about tampered devices as far back as <strong>December 2025</strong> — one of them Vietnamese crypto educator Tai Zen — and that he has not seen any public warning Ledger issued in response.</p><p>Joe Grand — the same researcher whose teardown of the hand-modified first-generation implant anchors the lineage table above — told Cointelegraph he alerted Ledger on <strong>March 4, 2026</strong> about a malicious implant in a Nano X traced to a Lazada Thailand marketplace seller (&quot;LedgerXXX&quot;) that is not on Ledger&apos;s authorized reseller list; the device had been purchased in August 2025. Grand says Ledger acknowledged his findings and said it was investigating internally — but no customer-facing warning followed. Asked how it handled Grand&apos;s disclosure, Ledger declined to comment and referred Cointelegraph to its public statements on X.</p><p>Karpelès put the criticism plainly. Not responding to a single implant found on a device &quot;purchased from a shady dealer&quot; may be normal, he told the outlet — but &quot;the increasing number of reports they must have received, and the increasing quality/technology used should have alerted them enough to act, and at least remind customers to be careful.&quot;</p><p>For the version archaeology above, this raises the stakes twice over. An implant flowing through an unauthorized marketplace listing in August 2025 means tampered devices were in circulation before the CryptoBilis acquisition closed — and the increasing &quot;quality&quot; Karpelès references is exactly the prototype-to-gen-3 progression Tibane documented. The question Ledger now faces is no longer only where its supply chain broke, but what it did between the first private warnings in December 2025 and the October crisis.</p><h2 level="2" textAlign="left" id="h-two-stores-two-implants">Two stores, two implants</h2><p>On October 11, an X user posting as Johannes reported that a Ledger Nano X bought weeks earlier at a MediaMarkt — the German electronics chain, an authorized Ledger reseller per the company&apos;s own directory — contained additional wiring that a genuine device should not have. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://news.bitcoin.com/security/user-exposes-hidden-hardware-implant-in-european-ledger-wallet/">Mark Karpelès reviewed the teardown photos</a> and identified the modification as another spy implant, notably an <em>earlier</em> generation than the designs he had examined from Malaysia: less concealed, with the giveaway antenna not yet hidden away.</p><p>He also spotted a detail that reframes the whole operation. The antenna, he said, carried a printed marking: <strong>&quot;Eurasian version.&quot;</strong> His read: the implant operation built variants tuned to the mobile frequencies of each target region. A device that exfiltrates seed phrases over LTE needs its radio to work where it ships — and labeling the build suggests inventory management, not one-off tinkering.</p><p>The next day, October 12, it got worse. Johannes bought a second Nano X at a <em>different</em> MediaMarkt store, recorded the unboxing, and found <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.tomshardware.com/tech-industry/cryptocurrency/store-bought-hardware-crypto-wallets-had-secret-chips-installed-that-enabled-stealing-crypto-recovery-phrases-usd93-million-and-counting-stolen-thanks-to-implanted-esim-and-lte-modules-in-ledger-wallets">the same modifications — extra cables and an LTE module</a>. Two stores, two devices, matching hardware. Neither of his wallets had been drained — &quot;either the device didn&apos;t work, or they were waiting for more widespread usage,&quot; he speculated, echoing what investigators keep saying about this attack class: a holder of harvested seeds can simply wait.</p><p>A MediaMarkt employee, per Johannes&apos;s account, said the unit was not a customer return (returned Ledgers go back to the manufacturer), and store records identified the stock source as <strong>Aqipa GmbH</strong> — a Europe-wide electronics distributor. The first device has been mailed to Karpelès and the second to Ledger for forensic examination. None of this is yet independently verified: it is one buyer&apos;s account, a researcher&apos;s assessment of photographs, and a paper trail that raises questions faster than anyone can answer them.</p><h2 level="2" textAlign="left" id="h-the-version-archaeology">The version archaeology</h2><p>The &quot;Eurasian version&quot; label lands on top of what researchers already knew: this implant has generations.</p><p>The technical deep-dive comes from <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.tibane.net/research/ledger-nano-x-implant">Tibane Labs</a>, which obtained two implanted Nano X units through Japanese marketplaces and documented the lineage:</p><table class="paragraph-table"><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Generation</p></th><th colspan="1" rowspan="1"><p>Where found</p></th><th colspan="1" rowspan="1"><p>What changed</p></th></tr><tr><td colspan="1" rowspan="1"><p>Prototype (2025)</p></td><td colspan="1" rowspan="1"><p>Surfaced via a Reddit warning; torn down by Joe Grand</p></td><td colspan="1" rowspan="1"><p>Hand-soldered enamel wires from the OLED&apos;s SPI lines to an add-on board — a one-off</p></td></tr><tr><td colspan="1" rowspan="1"><p>Gen 2</p></td><td colspan="1" rowspan="1"><p>Yahoo! Auctions Japan</p></td><td colspan="1" rowspan="1"><p>Custom Kapton flex circuit with proper silkscreen; factory-test-pad landing; implant replaces part of the battery</p></td></tr><tr><td colspan="1" rowspan="1"><p>Gen 3</p></td><td colspan="1" rowspan="1"><p>Amazon Japan, China-based seller, shipped from Malaysia</p></td><td colspan="1" rowspan="1"><p>Color-matched black coating; Nordic nRF9151 LTE module; eSIM; custom antenna at its second revision (<code>AC-A2016-NANO-V1.1</code>); footprint cut to key into the Ledger&apos;s own parts — drop-in installation, optimized for a production line</p></td></tr><tr><td colspan="1" rowspan="1"><p>&quot;Earlier version&quot;</p></td><td colspan="1" rowspan="1"><p>MediaMarkt, Europe</p></td><td colspan="1" rowspan="1"><p>Per Karpelès&apos;s photo assessment: visible antenna, implant not hidden under the screen — the design predates the Malaysia specimens</p></td></tr></tbody></table><p>The <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.bleepingcomputer.com/news/security/ledger-confirms-hardware-wallet-spy-implant-behind-crypto-thefts/">BleepingComputer writeup</a> adds the market signal: researchers had been showing Ledger X implants since September 16, with tampered devices circulating at nearly half the official price — the classic discount of gray-market tampered stock. And Karpelès notes the newer builds show signs of being <em>manufactured to order</em> rather than hand-modified. Panelized flex PCBs from a board house, a custom antenna already at revision two, keying that lets an unskilled worker drop the implant into place: this is what an assembly line looks like before you call it one.</p><p>Which makes the European find genuinely strange. The devices on German shelves are the <em>older</em>, less concealed design. The plausible readings: early-production implanted units have been sitting in European distribution for a long time; or different batches seeded different regions at different times. Either way, &quot;Eurasian version&quot; now reads less like a curiosity and more like a product SKU.</p><h2 level="2" textAlign="left" id="h-why-the-cryptobilis-playbook-doesnt-explain-this">Why the CryptoBilis playbook doesn&apos;t explain this</h2><p>Here is the part investigators cannot yet close. The Malaysia case had a mechanism: the reseller changed owners in secret, and the tampering maps onto the new regime. Europe has no such story. Aqipa GmbH is a long-standing pan-European distributor; MediaMarkt and Saturn (its sister chain, ~1,070 stores across 11 countries in the group) are authorized retail, not a shell anyone bought last spring. Nobody has alleged the distributor or the retailers did anything wrong — and nothing in the public record suggests they did.</p><p>That leaves open the uncomfortable possibilities: tampering further upstream in logistics, in transit, in warehousing — at some point where sealed boxes passed through hands nobody was watching. A tamper operation that can reach a mainstream European retail chain&apos;s shrink-wrapped stock is a different class of problem than one that bought a reseller in Kuala Lumpur. It is also, so far, exactly two devices. The honest position is: two confirmed-by-photographs European reports, zero confirmed-by-Ledger European cases, and a supply chain nobody has yet mapped.</p><p>Ledger&apos;s October 11 statement held the earlier line: all confirmed cases tied to the October 9 drains involve CryptoBilis devices, direct sales are unaffected, and the company is working with authorities and the SEAL 911 response group. The European units were still in the mail to their examiners at that point. By October 14, on-chain analytics firm <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bitquery.io/investigations/ledger-cryptobilis-hack">Bitquery</a> counted <strong>$102.0 million taken from 324 wallets across six blockchains</strong> — the operator pushed roughly 6,680 ETH through Tornado Cash and moved most of the exit funds on to Zcash, a trail first spotted by YFarmX. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/tanuki42_/status/2108594910752542741">Tether has frozen $10 million</a> in USDT tied to the investigation. Ledger&apos;s own position is unchanged: it has confirmed neither the number of victims nor the amount lost, and every circulating figure is a third-party estimate.</p><h2 level="2" textAlign="left" id="h-the-response-wave">The response wave</h2><p>Within 48 hours of the second MediaMarkt find, the industry started quarantining itself.</p><p><strong>MediaMarktSaturn delisted Ledger group-wide.</strong> The retail group behind roughly 1,070 MediaMarkt and Saturn stores removed Ledger products from shelves and websites &quot;internationally in all of our countries,&quot; calling it a precautionary measure. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/Ledger/status/2109984923343782374">Ledger said</a> the suspension came with its agreement, after a single customer report, and that no loss of funds had been reported through that channel.</p><p><strong>Ledger asked Southeast Asia and Hong Kong to stop selling.</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/Ledger/status/2110129361382994076">On October 13</a>, the company asked resellers and distributors across the region to suspend sales — while repeating that confirmed cases remain limited to devices sold in Southeast Asia, and that it has not verified a drain linked to a device bought elsewhere.</p><p><strong>Ledger&apos;s own lab explained the implant.</strong> The Donjon, Ledger&apos;s security team, published its first technical account: the implant sits inside the enclosure, reads what the screen displays, decodes the 24-word recovery phrase during setup, and transmits it over LTE through a provisioned eSIM. It does not touch the secure element, the operating system, or transaction signing — which is exactly why the genuine-device check cannot see it. CEO Pascal Gauthier said the company still does not know <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/_pgauthier/status/2109898470383329321">where in the distribution chain</a> devices were tampered, and is reviewing controls over both direct sales and resellers.</p><p><strong>Singapore airport joined the map.</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/MagicalTux/status/2109916873689280900">Karpelès confirmed</a> that a Ledger Flex bought in June at Changi Airport — from a store called Metapod, never initialized by its buyer Ben Yorke — contains a spy implant. That verification is his; Ledger has not said it examined the unit.</p><p><strong>Rivals tightened their channels.</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/Trezor/status/2110000774314873020">Trezor said</a> it is reducing the number of resellers it works with so it can vet those that remain, stressing there is no evidence any Trezor device was compromised. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://onekey.so/blog/zh-CN/updates/cryptobilis-incident-free-onekey-replacement-and-reseller-review">OneKey</a> went further: it terminated CryptoBilis&apos;s authorization, stopped onboarding new resellers, put every existing one under review, and is offering free replacements for OneKey devices bought through CryptoBilis since March 1 — apply by December 31.</p><h2 level="2" textAlign="left" id="h-what-actually-protects-you">What actually protects you</h2><p>The defenses are the ones we laid out when this story broke in Southeast Asia, now with wider blast radius — see our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-cryptobilis-supply-chain-hack/">CryptoBilis case study</a> for the acquisition trail and the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-drain-address-poisoning/">address-level tracing piece</a> for where the money went:</p><ul><li><p><strong>Buy from the manufacturer directly.</strong> Every confirmed compromised device so far moved through a reseller channel. &quot;Authorized&quot; now means &quot;authorized as of the last ownership change you didn&apos;t hear about&quot; — and possibly less than that, if the European trail holds.</p></li><li><p><strong>Software checks cannot clear hardware.</strong> Ledger&apos;s genuine check verifies the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/seed-phrase/">seed phrase</a>-guarding secure element; an implant that taps the display sits outside its view. A passing check means the chip is genuine, not that the device is clean.</p></li><li><p><strong>Sealed packaging proves nothing.</strong> At least one examined implant device arrived in factory-intact shrink wrap.</p></li><li><p><strong>A device that has been set up through an untrusted channel should be treated as burned.</strong> The fix is a new seed on trusted hardware, then transfer — not inspection, not reassurance, not waiting. Johannes&apos;s devices hadn&apos;t drained <em>yet</em>; &quot;yet&quot; is the operative word in this attack class.</p></li><li><p><strong>The old pre-filled-seed scams were the warm-up.</strong> Our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/hardware-wallet-scams-explained/">hardware wallet scam taxonomy</a> covers the classic version of this attack; the implant era is its industrial upgrade.</p></li></ul><h2 level="2" textAlign="left" id="h-what-to-watch">What to watch</h2><p>Four checkpoints will decide whether Europe is a footnote or a second front: (1) Ledger&apos;s forensic read on the second MediaMarkt device — same implant family or not; (2) Aqipa&apos;s stock records, if published or subpoenaed, showing whether the two units share a batch; (3) whether other European buyers open their devices and what they find; (4) whether Ledger publicly addresses the disclosure clock now on record — early reports from December 2025 and March 2026, and the silence in between. Add the questions Gauthier&apos;s statement left open — where in the chain the tampering happened, and whether Ledger ever verifies the airport Flex. Johannes has called for a recall; the retail group&apos;s answer was a group-wide delisting. If you hold a reseller-bought Ledger in Europe, the calculus is simple: the cost of re-seeding on a factory-direct device is an hour; the cost of being wrong about a &quot;Eurasian version&quot; antenna is everything on the keys.</p><p>We will update this page as forensic results land.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-mediamarkt-implant-europe/"><em>https://theonchaindiary.com/articles/ledger-mediamarkt-implant-europe/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/39f4c7c33a2d35f7adf2edb33981c574773dd18073c85e8f8bd713d64565bd50.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Fake Crypto Exchange Scams: Why the Balance Grows but the Withdrawal Never Comes]]></title>
            <link>https://paragraph.com/@onchaindiary/fake-crypto-exchange-withdrawal-scam</link>
            <guid>VsRw7CutFp8vUUG0Z00b</guid>
            <pubDate>Tue, 20 Oct 2026 08:00:35 GMT</pubDate>
            <description><![CDATA[The dashboard says you are up $40,000. The withdrawal button says your account is frozen. That gap — between a balance that keeps climbing and a withdrawal that never clears — is the entire product. Everything else, the professional interface, the candlestick charts, the "mentor" who messages you every morning, exists to keep you believing the first number while you keep feeding the second. This guide is about fake crypto exchanges: standalone fraud platforms dressed as trading venues, how th...]]></description>
            <content:encoded><![CDATA[<p>The dashboard says you are up $40,000. The withdrawal button says your account is frozen.</p><p>That gap — between a balance that keeps climbing and a withdrawal that never clears — is the entire product. Everything else, the professional interface, the candlestick charts, the &quot;mentor&quot; who messages you every morning, exists to keep you believing the first number while you keep feeding the second.</p><p>This guide is about fake crypto exchanges: standalone fraud platforms dressed as trading venues, how their fake profit mechanics work, the extraction ladder that follows a frozen withdrawal, and the one on-chain check that exposes most of them before you send a cent. It sits inside our victim-journey series — if you arrived here from a romance funnel, also read <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/pig-butchering-scams-explained/">how pig-butchering platforms trap their victims</a>, and if your funds are already gone, start with <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/stolen-crypto-first-24-hours/">the first 24 hours after theft</a>.</p><h2 level="2" textAlign="left" id="h-the-one-sentence-test">The One-Sentence Test</h2><p>A platform that demands payment to release your own money is not having a problem. The platform <strong>is</strong> the problem.</p><p>Real exchanges charge fees by deducting them — from a trade, from a withdrawal, from your balance. No legitimate venue anywhere asks you to send <em>additional</em> funds to &quot;activate&quot;, &quot;unfreeze&quot;, &quot;verify&quot;, or &quot;tax&quot; a withdrawal. The moment that request appears, you are not talking to an exchange. You are talking to the fraud operator whose database row you have been reading as a bank account.</p><p>Consumer-fraud agencies have a name for the shape of this: advance-fee fraud. The FBI&apos;s Internet Crime Complaint Center documents the same escalation loop — deposit, freeze, pay-to-unlock, bigger freeze — across its scam categories, including the &quot;<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ic3.gov/AnnualReport/Reports/2024_IC3Report.pdf">task scamming</a>&quot; scheme it flagged in its 2024 annual report, where &quot;boosted tasks&quot; on a platform&apos;s own crypto site lock withdrawals behind escalating fees. The fake exchange is the same machine wearing a trading-terminal skin.</p><h2 level="2" textAlign="left" id="h-what-a-fake-exchange-actually-is">What a Fake Exchange Actually Is</h2><p>Three shells cover most of the market:</p><p><strong>The clone.</strong> A pixel-level copy of a real exchange&apos;s frontend on a lookalike domain — one character off, or on a regional TLD, or reached through a sponsored search ad that outbids the real thing. You log in with credentials harvested from a phishing page; sometimes the clone proxies the real exchange&apos;s API so prices move correctly while your deposits go elsewhere. If you arrived at an exchange through a search ad, close the tab and type the domain yourself.</p><p><strong>The invented brand.</strong> A platform that never existed as a real venue: &quot;proprietary AI trading terminal&quot;, &quot;institutional liquidity desk&quot;, a slick app in a regional app store. These are built for funnels — romance victims, task-scam graduates, &quot;trading groups&quot; run by a mentor who shows screenshots of daily profits. The brand often borrows credibility: an address in Singapore or London on the contact page, a fake regulation number, a &quot;sponsorship&quot; logo wall.</p><p><strong>The mini-app.</strong> A Telegram bot or in-chat mini-app &quot;exchange&quot; where a support account handles deposits manually. No custody infrastructure at all — just an address, a chat, and a spreadsheet.</p><p>In all three, your balance after deposit is a field in their database. Nothing backs it.</p><h2 level="2" textAlign="left" id="h-the-fake-profit-machine">The Fake Profit Machine</h2><p>The trick that keeps victims depositing is that the losses are hidden behind gains that look realized.</p><p>The platform&apos;s charts are real market data. Your positions appear to trade at market prices. The &quot;mentor&quot; — often an operator with a script, increasingly an AI chatbot handling dozens of victims at once — teaches you to take profit at the right moments, and the profit lands in your platform balance. Early on, a small withdrawal may even clear, funded from the deposits of victims who arrived before you. That payout is a customer-acquisition cost, exactly like the first real commissions in a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-task-scam-money-mule/">task scam</a>. It exists to convert you from a skeptic into an evangelist.</p><p>None of the trading is real. There is no order book, no counterparty, no custody. The day you attempt a withdrawal large enough to matter, the database row stops pretending: account frozen, risk-control flag, compliance review.</p><h2 level="2" textAlign="left" id="h-the-extraction-ladder">The Extraction Ladder</h2><p>Once the withdrawal freezes, the script is remarkably consistent across cases:</p><ol><li><p><strong>The fee.</strong> A &quot;withdrawal tax&quot;, &quot;processing fee&quot;, or &quot;gas top-up&quot; — a modest amount relative to the balance, framed as a formality.</p></li><li><p><strong>The partial release.</strong> Sometimes a fraction of the withdrawal clears after payment, proving the system &quot;works&quot;. This is the most expensive lie in the sequence.</p></li><li><p><strong>The escalation.</strong> A &quot;risk-control violation&quot; or &quot;data mismatch&quot; — your account triggered anti-money-laundering rules, and a larger payment is required to unfreeze it. The demanded amounts scale with what you have already paid, not with your balance.</p></li><li><p><strong>The shared burden.</strong> Support suggests family members or group members &quot;pool&quot; to unfreeze the account. Group chats of victims coordinating payments — all talking to the same operator behind different accounts — are common in the later stages.</p></li><li><p><strong>The disappear.</strong> Eventually the domain goes dark, the app vanishes from the store, and the mentor&apos;s account is deleted.</p></li></ol><p>Every payment at every rung goes to the same place: the operators. The balance never existed. The ladder is the business model — the platform&apos;s entire revenue is the fees victims pay to unlock money that was never there.</p><h2 level="2" textAlign="left" id="h-where-the-money-actually-goes">Where the Money Actually Goes</h2><p>The most complete public map of this pipeline is the Justice Department&apos;s case against Daren Li and Yicheng Zhang. Thousands of victims — many recruited through romance and task funnels — deposited into a fraudulent crypto investment platform. The proceeds moved through shell company bank accounts in the US, layered between banks, sent to Deltec Bank in the Bahamas, converted to USDT, and consolidated: one wallet associated with the network received <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.justice.gov/opa/pr/two-foreign-nationals-arrested-laundering-least-73m-through-shell-companies-tied">over $341 million</a>. Li was <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.justice.gov/opa/pr/man-sentenced-20-years-prison-role-73-million-global-cryptocurrency-investment-scam">sentenced to 20 years in prison</a> in absentia in February 2026 after pleading guilty and fleeing before sentencing.</p><p>The lesson from the on-chain side of that case: the deposit you sent was gone within days, long before the platform told you anything was wrong. We traced the full four-stage pipeline — deposit rails, bank layering, USDT conversion, cash-out — in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/pig-butchering-crypto-tracing/">where pig-butchering money actually goes</a>. For you as a victim, the practical consequence is about expectations: the dashboard balance is not escrowed, and no amount of compliance theater on the platform&apos;s side will &quot;release&quot; it.</p><h2 level="2" textAlign="left" id="h-the-deposit-address-test">The Deposit-Address Test</h2><p>This is the check that exposes most fake exchanges before you send anything, and almost nobody knows to run it.</p><p><strong>How real exchanges handle deposits.</strong> A genuine exchange gives your account a deposit address per asset that is <em>persistent</em> — you can reuse it for months — and <em>attributable</em>. Paste that address into a block explorer like Etherscan or Tronscan and you will typically see structured behavior: deposits from many users sweeping in batches into hot wallets that analytics firms and explorers publicly label as belonging to that exchange. The address lives inside a real custody operation.</p><p><strong>How fake platforms handle deposits.</strong> A fraud platform needs to avoid attribution, so it generates a <em>fresh address for every deposit</em> — often created the moment you click &quot;deposit&quot;, with zero prior history. Check it on-chain and you see nothing: no inflows, no label, no relationship to any custody wallet. Send to it, and within hours the funds fan out — split, forwarded through a chain, or consolidated with transfers from dozens of other victims into an address that leads to an exchange cash-out. That fan-in-pass-through shape is what investigators look for, and it is visible to you too, for free, before you deposit. We cover the labeling side of this in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/wallet-labels/">how wallet labels expose tainted funds</a> — the same mechanism that later flags a scam address is available to you <em>before</em> you send.</p><p>Three red flags on the deposit screen alone:</p><ul><li><p>The address is new for each deposit and the old ones are &quot;expired&quot;</p></li><li><p>The platform insists on a specific chain that differs from its branding (a &quot;US exchange&quot; collecting only TRC-20 USDT)</p></li><li><p>Deposit instructions arrive through a chat or &quot;account manager&quot; rather than the platform&apos;s own deposit page</p></li></ul><p>A <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/stablecoin/">stablecoin</a> deposit to a fresh address is a wire transfer to a stranger with no recourse. Treat it that way.</p><h2 level="2" textAlign="left" id="h-red-flag-checklist">Red-Flag Checklist</h2><ul><li><p>You were introduced to the platform by a stranger, a romantic interest, a task-scam group, or a &quot;trading mentor&quot; — not by finding a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/cex/">licensed exchange</a> yourself</p></li><li><p>The domain is one character off a major brand, or you reached it through a sponsored ad</p></li><li><p>Profits are shown daily and steadily, with a mentor who times the market suspiciously well</p></li><li><p>A small test withdrawal cleared, but the larger one is frozen</p></li><li><p>Any request to pay a fee, tax, margin, or &quot;verification&quot; to withdraw</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/kyc/">KYC</a> documents were collected early — they feed identity-theft and mule-account <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/phishing-attack/">phishing</a> later</p></li><li><p>Support pressures you to deposit more to &quot;fix&quot; the account</p></li></ul><p>Any single one of these is disqualifying. The platform does not need to be investigated further; it needs to be reported.</p><h2 level="2" textAlign="left" id="h-if-you-are-trapped-right-now">If You Are Trapped Right Now</h2><p><strong>Stop paying.</strong> The hardest instruction to follow, because the balance is an emotional hostage. Every payment — fee, tax, margin — funds the operation and triggers the next demand. There is no rung of the ladder where paying works.</p><p><strong>Do not delete anything.</strong> The app, the chats, the mentor&apos;s handles, the platform URL, the deposit addresses, the transaction hashes, the bank transfer records — this is your evidence package. Screenshots with visible timestamps. Export what the app allows.</p><p><strong>Dispute the bank leg.</strong> If any deposit left your bank account as a wire, ACH, or card payment to a &quot;merchant&quot; or personal account, call your bank now, state that you believe you were defrauded, and ask about a recall or dispute. Bank rails are the recoverable edge of this crime; the blockchain leg is not reversible. The fiat component is also what makes your report join-able to investigations like the Li case, which was built on shell-company banking records.</p><p><strong>Report.</strong> File with <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-report-crypto-scam/">IC3</a> in the US, or your national cybercrime channel elsewhere. Include every deposit address and hash. Aggregated reports are how these platforms get mapped — a single victim&apos;s addresses often connect to hundreds of others&apos; in the fan-in pattern.</p><p><strong>Expect the second act.</strong> Days or weeks after you report, messages will arrive: &quot;I&apos;m from a fund-recovery firm&quot;, &quot;I recovered funds for another victim of this platform&quot;, &quot;Pay a retainer and we&apos;ll trace your USDT&quot;. These are the same operators or their affiliates, buying victim lists. Read <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-recovery-scams-explained/">how crypto recovery scams work</a> before answering anyone. And for the realistic picture of what recovery looks like — freezes, seizures, restitution years later — read <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-stolen-crypto-is-recovered/">how stolen crypto is actually recovered</a>.</p><h2 level="2" textAlign="left" id="h-why-smart-people-keep-paying">Why Smart People Keep Paying</h2><p>The mechanism is sunk cost dressed as strategy. Once the first fee is paid, refusing the second feels like wasting the first. The platform prices each rung to feel almost-reasonable against the balance on screen — $2,000 to unlock $180,000 reads as arithmetic, not fraud. And the group chat of fellow &quot;investors&quot; — all operator sock-puppets or fellow victims coordinating payments into the same wallet — normalizes every step.</p><p>The exit from the ladder is not a smarter payment. It is refusing the premise: the balance was never yours because it was never real. The money you can still protect is whatever you have not yet sent. Guard that, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-report-crypto-scam/">follow the reporting path</a>, and if you found this page before depositing — run the deposit-address test and walk away.</p><h2 level="2" textAlign="left" id="h-related-reading">Related Reading</h2><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-detect-nft-wash-trading/">How to Detect NFT Wash Trading</a> — fake volume is to market data what fake balances are to trading platforms</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/telegram-airdrop-bot-scams/">Telegram Airdrop Bot Scams</a> — the mini-app shell without the exchange costume</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/pig-butchering-crypto-tracing/">Pig Butchering Money Tracing</a> — the full $73M pipeline from deposit rails to USDT cash-out</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/airdrop-safety-checklist/">Airdrop Safety Checklist</a> — verify before you connect a wallet anywhere</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/fake-customer-support-scams/">Fake Customer Support Scams</a> — the &quot;verification&quot; follow-up that targets fraud victims twice</p></li></ul><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/fake-crypto-exchange-withdrawal-scam/"><em>https://theonchaindiary.com/articles/fake-crypto-exchange-withdrawal-scam/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/095de93f810827a15d9a5f4f9de9afe0017f02c4187ee711157a09393bcb92fd.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Denmark CPR Breach: 8.8M Identities Sat Behind a '123456' Password]]></title>
            <link>https://paragraph.com/@onchaindiary/denmark-cpr-breach-123456</link>
            <guid>7cEiXz3fDSWxaUgEcAI5</guid>
            <pubDate>Tue, 20 Oct 2026 08:00:27 GMT</pubDate>
            <description><![CDATA[The strangest detail in Denmark's biggest data breach is not the password. It is that the password worked exactly as designed. On October 5, 2026, the Danish government confirmed that unauthorized parties had accessed personal records belonging to about 8.8 million people in the Central Person Register, the CPR system that anchors Danish civic life (The Hacker News). The register holds roughly 11 million records in total, including deceased and emigrated persons, which is how a country of abo...]]></description>
            <content:encoded><![CDATA[<p>The strangest detail in Denmark&apos;s biggest data breach is not the password. It is that the password worked exactly as designed.</p><p>On October 5, 2026, the Danish government confirmed that unauthorized parties had accessed personal records belonging to about 8.8 million people in the Central Person Register, the CPR system that anchors Danish civic life (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://thehackernews.com/2026/10/denmark-says-attackers-accessed-cpr.html">The Hacker News</a>). The register holds roughly 11 million records in total, including deceased and emigrated persons, which is how a country of about 5.9 million can produce an 8.8-million-person breach (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.theregister.com/security/2026/10/13/123456-password-linked-to-denmark-data-breach-affecting-88m-people/5302726">The Register</a>). The compromised fields were names, street addresses, and CPR numbers. The CPR number encodes your birth date, so the leak is a full identity kit minus the email.</p><h2 level="2" textAlign="left" id="h-ten-days-fourteen-million-queries-one-invoice">Ten days, fourteen million queries, one invoice</h2><p>Documents obtained by Danish broadcaster TV 2 put the intrusion on September 10, 2026. From that day until September 20, the attacker ran about 14 million automated searches against the register (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://nyheder.tv2.dk/business/2026-10-09-nye-detaljer-om-cpr-skandale-hacker-var-over-alle-bjerge">TV 2</a>). Nobody noticed the traffic itself. What broke the case, according to Mikkel Leihardt, a ministry director who spoke at the government&apos;s press conference, was a staffer picking up an invoice that showed unusually high activity from a private company&apos;s account (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.theregister.com/security/2026/10/13/123456-password-linked-to-denmark-data-breach-affecting-88m-people/5302726">The Register</a>).</p><p>The timeline that matters for defenders:</p><ul><li><p><strong>September 10</strong>: attacker gains access through the legal channel</p></li><li><p><strong>September 10-20</strong>: ~14 million automated queries run</p></li><li><p><strong>October 2</strong>: intrusion detected, triggered by an invoice anomaly, 12 days after the last query</p></li><li><p><strong>October 4</strong>: the Danish data protection authority, Datatilsynet, is notified</p></li><li><p><strong>October 5</strong>: public disclosure</p></li></ul><p>Fourteen million queries in ten days is not stealth. It went undetected because it arrived through a door that was supposed to be open.</p><h2 level="2" textAlign="left" id="h-the-way-in-a-vendor-with-123456">The way in: a vendor with &apos;123456&apos;</h2><p>The company at the center is Pays ApS, a small IT and data services firm on the island of Funen. It held authorized access to the CPR system to provide services like validating business customers&apos; records. The government did not name the firm, but Pays&apos; managing director Sophie Laursen confirmed on October 9 that the company&apos;s access had been exploited; the firm&apos;s website has since gone offline (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.theregister.com/security/2026/10/13/123456-password-linked-to-denmark-data-breach-affecting-88m-people/5302726">The Register</a>).</p><p>On October 13, Politiken reported the person claiming responsibility said the entry point was an account protected by the password &quot;123456,&quot; and that at least three of the company&apos;s profiles, including an administrator account, shared that password. The same person told the paper they had no intention of selling or leaking the data (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://politiken.dk/danmark/art11016363/%C2%BBOh-my-god%C2%AB-Fynsk-virksomhed-havde-mindst-tre-profiler-med-adgangskoden-123456">Politiken</a>). Whether that holds is beside the point. The data left the building.</p><p>Read this next to our coverage of the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-cryptobilis-supply-chain-hack/">Ledger supply-chain compromise</a> and the pattern is identical: the core system was never broken, because a trusted edge was. Ledger&apos;s firmware did not fail, a retail channel did. Denmark&apos;s register did not fail, a vendor&apos;s credential hygiene did. In both cases the blast radius was set not by the strength of the crown jewels but by how loosely the keys to them were copies. This is the working definition of a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/supply-chain-attack/">supply chain attack</a>: you inherit someone else&apos;s security budget.</p><h2 level="2" textAlign="left" id="h-why-identity-data-is-crypto-scam-ammunition">Why identity data is crypto scam ammunition</h2><p>Nothing in this breach touches a blockchain, an exchange hot wallet, or a seed phrase. So why write about it here? Because <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/phishing-attack/">phishing attacks</a> convert identity data into stolen crypto, and the conversion rate rises with the quality of the data.</p><p>A scam email that opens with &quot;Dear user&quot; is noise. A message that has your legal name, your street address, and a number that encodes your birth date can pass the first filter every victim applies: <em>do they seem to know me?</em> That is the entire mechanic of <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/social-engineering/">social engineering</a>, and it is the same whether the target is a bank login or a seed phrase.</p><p>Concretely, for readers holding crypto in Denmark or anywhere this data circulates:</p><ul><li><p><strong>MitID phishing</strong>: Denmark&apos;s national digital identity gates banking and exchange logins. Security outlets covering the breach note that while MitID makes wholesale impersonation harder, real CPR data makes the surrounding lures far more convincing (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cybernews.com/security/denmark-cpr-data-breach-weak-password/">Cybernews</a>). Expect &quot;verify your MitID&quot; waves referencing your actual details.</p></li><li><p><strong>Exchange support impersonation</strong>: &quot;We noticed unusual activity, confirm your withdrawal address&quot; hits differently when the caller opens with your name, address, and birth date.</p></li><li><p><strong>Fake KYC pressure</strong>: a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/kyc/">KYC</a> pretext is a natural fit, since the scammer can claim your &quot;registry record needs updating&quot; using real registry-shaped data.</p></li><li><p><strong>SIM swap pre-staging</strong>: identity data smooths the carrier social-engineering step that precedes many <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/sim-swap-attacks-explained/">SIM swap attacks</a>.</p></li></ul><p>The person behind this intrusion says they will not sell. History says data like this surfaces eventually, and the buyers are not curious.</p><h2 level="2" textAlign="left" id="h-the-detection-lesson-invoices-before-monitoring">The detection lesson: invoices before monitoring</h2><p>For an operation that runs on automation, the most uncomfortable fact is that 14 million queries sailed through for ten days and the alarm was a human reading a bill. There is a crypto-side mirror here. Most wallet victims discover Drain activity not from an alert but from a balance that no longer matches expectation, days or weeks after a forgotten approval was exercised. If you hold crypto, the equivalent of the unread invoice is the approval list you have not audited: run through the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-audit-your-wallet-activity/">wallet activity audit workflow</a> before someone else generates the anomaly for you.</p><h2 level="2" textAlign="left" id="h-what-to-actually-do">What to actually do</h2><p>If you are in the affected population, or you assume your identity data is loose somewhere like everyone else should:</p><ol><li><p><strong>Treat inbound contact as hostile by default.</strong> Anyone who contacts you first and already knows your name, address, or birth date has proven nothing except access to a database. Verify through the official app or a number you look up yourself. This is the core habit in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-avoid-crypto-phishing-scams/">avoiding crypto phishing scams</a>.</p></li><li><p><strong>Never move assets because of a message.</strong> No exchange, no registry, no bank moves your funds because you failed to click something in time. Deadlines in unsolicited messages are the tell.</p></li><li><p><strong>Harden the recovery path.</strong> The seed phrase on paper in a drawer is untouched by this breach. What identity data attacks is the account-recovery layer around your exchange and email accounts. Hardware-key 2FA where offered, carrier port-freeze where available.</p></li><li><p><strong>For operators and teams</strong>: if a vendor can read your crown jewels with one shared password, you do not have a password problem, you have an access-architecture problem. Denmark just demonstrated the cost curve at national scale.</p></li></ol><p>The breach will be remembered for &quot;123456.&quot; The number that should stick is fourteen million, times ten days, times zero alerts, until someone read an invoice.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/denmark-cpr-breach-123456/"><em>https://theonchaindiary.com/articles/denmark-cpr-breach-123456/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/75f12874807542b51870d82a3e3fbfedaedf2eba72fc5acac809d5cd3d10b47b.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Bitcoin Blackmail Emails Explained: The Password Is Real, the Video Is Not]]></title>
            <link>https://paragraph.com/@onchaindiary/bitcoin-blackmail-email-scam</link>
            <guid>qYhrvCRi47ULtRYKf7bk</guid>
            <pubDate>Tue, 20 Oct 2026 08:00:20 GMT</pubDate>
            <description><![CDATA[The email that knows your password It usually arrives with no greeting. The subject line is an old password — one you actually recognize, maybe from a job you left years ago. The body claims the sender installed spyware on your device, recorded you through your webcam, compiled a video spliced with the sites you visited, and will send it to your contacts unless a Bitcoin payment lands at the pasted address within 48 hours. Some versions add a sample of the password history, a fake "mail was s...]]></description>
            <content:encoded><![CDATA[<h2 level="2" textAlign="left" id="h-the-email-that-knows-your-password">The email that knows your password</h2><p>It usually arrives with no greeting. The subject line is an old password — one you actually recognize, maybe from a job you left years ago. The body claims the sender installed spyware on your device, recorded you through your webcam, compiled a video spliced with the sites you visited, and will send it to your contacts unless a Bitcoin payment lands at the pasted address within 48 hours. Some versions add a sample of the password history, a fake &quot;mail was sent from your own account&quot; header, or a link labeled &quot;view what I have on you.&quot;</p><p>Two things in that email are real. Your email address is real, and the password is real — or was, once. Everything else is a template.</p><p>The video does not exist. There is no spyware, no recording, no contact list loaded and ready. What you are holding is a mass-mail blast sent to millions of addresses at once, personalized with exactly one data point — a username-and-password pair out of an old breach dump. Researchers at the University of Montreal and Université de Montréal who studied these campaigns in 2019 found the first sextortion emails demanding cryptocurrency appeared in July 2018, and that the waves were pushed out through rented spam botnets such as Necurs and Cutwail — the same industrial mailing infrastructure that ships diet-pill spam (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://arxiv.org/abs/1908.01051">Paquet-Clouston et al., &quot;Spams meet Cryptocurrencies: Sextortion in the Bitcoin Ecosystem&quot;</a>, covered by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.technologyreview.com/2019/08/19/133654/the-anatomy-of-a-sextortion-spam-campaign/">MIT Technology Review</a>).</p><p>That single fact should recalibrate your fear. You are not being watched. You are on a mailing list.</p><h2 level="2" textAlign="left" id="h-where-the-password-actually-came-from">Where the password actually came from</h2><p>The password in the subject line is the hook, and its history explains the whole trick. Services get breached, credential dumps get aggregated, and those dumps get sold and resold among criminals for years. When a blackmail wave goes out, the sender buys a dump, pairs each row&apos;s password with its email address, and mails millions of messages where the only &quot;proof of hacking&quot; is data the victim themselves typed into some other website a decade ago.</p><p>That is why the password is so often stale. Many recipients report seeing passwords from accounts they closed years before. It is also why the tactic works: at two in the morning, &quot;they know my password&quot; short-circuits the question of <em>how</em> they know it.</p><p>If you want to see your own exposure, free breach-lookup services like Have I Been Pwned will list which known breaches contained your email address. The result usually explains the email you just received with surgical precision — a 2016 forum breach, a 2019 meal-delivery leak, and there is your subject line.</p><p>The malware channel exists too, separately. Infostealer malware genuinely harvests saved passwords and browser sessions from infected machines, and its logs feed the same criminal marketplaces. But an infostealer infection produces a rich, current profile — and the blackmail email needs only one old password, which is the signature of a purchased dump, not a live implant. If you want to audit the real risks of that other channel, we cover the infostealer kill chain separately.</p><h2 level="2" textAlign="left" id="h-what-the-blockchain-says-about-the-senders">What the blockchain says about the senders</h2><p>Here is the part most victims never do, and it is quietly reassuring: check the Bitcoin address.</p><p>Paste the address from the email into any block explorer. Mass-mail sextortion wallets have a recognizable shape — they run for weeks or months, collecting a long tail of small payments, many of them below the demanded amount, because a fraction of terrified recipients negotiate against a script that was never about them specifically. Cisco Talos, dissecting one campaign, found the payment wallets held far less than the campaign&apos;s minimum demand implied it should, and that the same wallets were reused across different attack waves — one collection jar, many letters.</p><p>The 2019 academic study went further and followed the money at scale. By clustering the addresses used across campaigns and tracing them through the Bitcoin ecosystem, the researchers concluded that a single entity was likely controlling the financial backbone of the majority of sextortion campaigns they investigated. In other words: the emails looked like a thousand different blackmailers; the cash register was often one operation.</p><p>Reading a wallet before you interact with it is a general skill, not a parlor trick. It is the same discipline we use to grade addresses in our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/wallet-labels/">wallet labels</a> guide, the same technique behind <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/address-risk-scoring-explained/">on-chain address risk scoring</a>, and the same pattern-reading you would apply when checking whether an NFT collection&apos;s volume is real or <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-detect-nft-wash-trading/">wash-traded</a>. On-chain history does not lie about what a wallet was built for.</p><h2 level="2" textAlign="left" id="h-the-2026-upgrade-real-breaches-named-crews-harassment">The 2026 upgrade: real breaches, named crews, harassment</h2><p>For years this scam ran on pure bluff — one old password and a lot of formatting. That changed as breach-extortion crews industrialized, and the sharpest public marker is the FBI&apos;s Internet Crime Complaint Center advisory issued May 15, 2026, on ShinyHunters (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ic3.gov/PSA/2026/PSA260515">IC3 PSA I-051526-PSA</a>).</p><p>ShinyHunters specializes in large-scale data breaches, stealing millions of customer records at a time. The extortion emails that follow use what the FBI describes as &quot;real or exaggerated claims of access to sensitive or personal information&quot; to pressure payment. The escalation beyond the old template is behavioral: harassing texts and phone calls to victims <em>and their family members</em>, and in some cases swatting. And the core bluff is still central — the advisory notes the actors may falsely claim to have embarrassing photographs or videos, &quot;which frequently do not exist.&quot;</p><p>So the 2026 decision tree has two branches:</p><ul><li><p><strong>The old template</strong> (old password, generic webcam claims, Bitcoin address, countdown): mass-mail bluff. Delete, report, rotate reused passwords.</p></li><li><p><strong>The named-crew variant</strong> (your data from a specific recent breach, real names, contact info of relatives, calls and texts): the <em>data</em> is real and the <em>harassment</em> is real, but the claimed compromising material is still, in the FBI&apos;s word, frequently fabricated. Do not pay. Verify claims through channels other than the one that contacted you. Save everything — emails, numbers, screenshots — and report. An immediate physical threat is a matter for local police, not for negotiation.</p></li></ul><p>The FBI&apos;s recommended actions in the advisory are worth internalizing because they generalize: verify urgent or unusual requests through a different communication method before responding; do not send payment; do not respond to demands; be cautious of follow-up impersonation — fake emails posing as your school, your provider, or law enforcement.</p><h2 level="2" textAlign="left" id="h-the-second-bite-sextortion-assistance-companies">The second bite: &quot;sextortion assistance&quot; companies</h2><p>There is a sequel, and the FBI has flagged it too. In April 2023, IC3 issued a public service announcement about for-profit companies that contact sextortion victims offering &quot;assistance&quot; — for a fee (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ic3.gov/PSA/2023/PSA230407">IC3 PSA, April 7, 2023</a>).</p><p>The economics are elegant and vile. The victim never reported the original email to anyone. So when a stranger calls days later saying &quot;we can make this go away / remove your data / track the scammer — $1,900 upfront,&quot; the victim assumes help has arrived. It has not. These outfits buy the same victim lists, or trawl for scared people responding publicly, and sell the cure to a crime that was never going to happen. It is the same skeleton as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-recovery-scams-explained/">crypto recovery scams</a> and the fake &quot;<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/fake-customer-support-scams/">customer support</a>&quot; crews that contact you first: anyone who initiates contact to sell you relief from a crime you didn&apos;t report is running the second act of the same play.</p><h2 level="2" textAlign="left" id="h-what-to-actually-do-in-order">What to actually do, in order</h2><p><strong>1. Do not pay.</strong> Payment converts you from an address on a list into a verified responder — the only category of recipient worth individual attention. The FBI&apos;s guidance for ShinyHunters-style extortion is explicit: do not send payment or respond to their demands.</p><p><strong>2. Do not click, do not &quot;view the evidence.&quot;</strong> The link goes to credential phishing or a page engineered to trigger a wallet signature. If your crypto wallet is what worries you, the durable defenses are covered in our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/airdrop-safety-checklist/">airdrop safety checklist</a> and our piece on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/infinite-approval-explained/">infinite approvals</a> — the signature, not the password, is what drains wallets.</p><p><strong>3. Rotate the exposed password and its siblings.</strong> The password in the subject line is burned everywhere you reused it. Change it, and stop reusing: a password manager makes every site&apos;s credential independent. Turn on app-based two-factor for email first — email is the master key that resets everything else. (SMS-based factors have their own failure mode; see our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/sim-swap-attacks-explained/">SIM swap walkthrough</a>.)</p><p><strong>4. Save the email and report it.</strong> Keep the full message with headers, the Bitcoin address, and any numbers that contacted you. In the US, file with the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ic3.gov/">Internet Crime Complaint Center</a>; the May 2026 advisory asks victims to retain usernames, addresses, monikers, and platforms used. Our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-report-crypto-scam/">step-by-step reporting guide</a> covers what a complaint actually does with the evidence. Outside the US, most national cybercrime portals accept these reports — they aggregate, and aggregation is how the botnets and wallets get mapped.</p><p><strong>5. Tell one person.</strong> These emails are engineered to weaponize shame, and shame thrives on silence. The FBI advisory explicitly points victims to mental-health resources, and it is the correct instinct: the threat is fake, the fear is real, and both get smaller when spoken aloud. If the variant you received involves genuine harassment of you or your family, treat it as the crime it is — document, report, and involve local police for any physical threat.</p><h2 level="2" textAlign="left" id="h-the-red-flag-checklist">The red-flag checklist</h2><table class="paragraph-table"><colgroup><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Signal in the email</p></th><th colspan="1" rowspan="1"><p>What it actually is</p></th></tr><tr><td colspan="1" rowspan="1"><p>Old password in the subject line</p></td><td colspan="1" rowspan="1"><p>A row from a years-old breach dump, not device access</p></td></tr><tr><td colspan="1" rowspan="1"><p>&quot;I recorded you through your webcam&quot;</p></td><td colspan="1" rowspan="1"><p>Template text; the video does not exist</p></td></tr><tr><td colspan="1" rowspan="1"><p>24–48 hour countdown</p></td><td colspan="1" rowspan="1"><p>A conversion tactic from direct-response marketing</p></td></tr><tr><td colspan="1" rowspan="1"><p>&quot;Sent from your own account&quot;</p></td><td colspan="1" rowspan="1"><p>Trivially forged header, a standard spam trick</p></td></tr><tr><td colspan="1" rowspan="1"><p>Link to &quot;view the file on you&quot;</p></td><td colspan="1" rowspan="1"><p>Credential phishing or a wallet-signature trap</p></td></tr><tr><td colspan="1" rowspan="1"><p>Bitcoin or Monero address, fixed amount</p></td><td colspan="1" rowspan="1"><p>A mass-mail collection wallet, reused across campaigns</p></td></tr><tr><td colspan="1" rowspan="1"><p>Named crew + real breach data + calls to family (2026 variant)</p></td><td colspan="1" rowspan="1"><p>Real data, real harassment — but the claimed footage is still frequently fabricated, per the FBI</p></td></tr><tr><td colspan="1" rowspan="1"><p>Later: a company offers paid &quot;sextortion help&quot;</p></td><td colspan="1" rowspan="1"><p>The sequel scam the FBI warned about in April 2023</p></td></tr></tbody></table><h2 level="2" textAlign="left" id="h-the-one-paragraph-takeaway">The one-paragraph takeaway</h2><p>The password is real, the video is not, and the wallet at the bottom of the email is a shared collection jar that researchers have watched recycle across campaigns since 2018. The 2026 named-crew variant adds genuine stolen data and genuine harassment — which raises the stakes on reporting, not on paying. Do not pay, do not click, rotate the reused password, save everything, file the report, and talk to one person you trust. Fear is the product being sold; everything in this article is just the refund policy.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/bitcoin-blackmail-email-scam/"><em>https://theonchaindiary.com/articles/bitcoin-blackmail-email-scam/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/3b103d2b58551113db831c1ad514e0a84e23e167f29961ef2f99b7a6dd1510a5.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Best Ways to Verify Token Addresses: 6 Checks That Hold Up Against Real Scams]]></title>
            <link>https://paragraph.com/@onchaindiary/best-ways-to-verify-token-addresses</link>
            <guid>K05nV42sS2WIqGXQGucR</guid>
            <pubDate>Tue, 20 Oct 2026 08:00:11 GMT</pubDate>
            <description><![CDATA[In October 2026, people in Southeast Asia who bought Ledger hardware wallets from an authorized reseller, CryptoBilis, received genuine packaging, a real brand, and a device carrying a hidden implant that read the recovery phrase during setup. The reseller was authorized. The packaging looked right. The distribution channel between the factory and the buyer had been compromised. By Bitquery's on-chain count, about $102 million moved out of 324 wallets across six chains, an estimate Ledger has...]]></description>
            <content:encoded><![CDATA[<p>In October 2026, people in Southeast Asia who bought Ledger hardware wallets from an authorized reseller, CryptoBilis, received genuine packaging, a real brand, and a device carrying a hidden implant that read the recovery phrase during setup. The reseller was authorized. The packaging looked right. The distribution channel between the factory and the buyer had been compromised. By Bitquery&apos;s on-chain count, about $102 million moved out of 324 wallets across six chains, an estimate Ledger has not confirmed. The victims did not fail to verify. They verified against signals the attacker had learned to fake.</p><p>The same pattern repeats every week with token addresses. A buyer finds a token, checks that the contract shows a blue checkmark on the explorer, sees a few thousand holders, buys, and discovers the contract will not let them sell. Every individual check passed. The token was still a fake.</p><p>The problem is not that verification is useless. It is that most guides ranking the best ways to verify token addresses teach the checks as if scammers cannot read. They can. Every public verification signal has been studied, priced, and weaponized. This guide walks through the six ways to verify a token address that actually hold up, what each one really tells you, and the specific bypass attackers use against it.</p><blockquote><p><strong>BLUF:</strong> No single check proves a token is real. Stack independent signals. (1) <strong>Pull the address from the project&apos;s official site, then cross-check it against a second official channel</strong> such as the project&apos;s X account or GitHub, not a search ad or a Telegram forward. (2) <strong>Confirm the address on the correct chain&apos;s block explorer</strong> and read what the contract actually does, not just whether it is verified. (3) <strong>Run the address through a scam scanner</strong> (GoPlus or Token Sniffer on EVM chains, RugCheck on Solana) and re-scan right before you buy, because scanner results are snapshots. (4) <strong>Read holder distribution and liquidity as adversarial data</strong> that can be manufactured. (5) <strong>Beware lookalike addresses</strong> that match the first and last characters of a real contract. (6) <strong>Distrust the channel that brought you the token</strong> if it is a paid search ad, a DM, or a group you joined last week. For chain-specific deep dives, see our guides for <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/erc20-token-security-check/">Ethereum</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/solana-token-safety/">Solana</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/base-chain-token-safety/">Base</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/arbitrum-token-safety/">Arbitrum</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/bnb-chain-token-safety/">BNB Chain</a>, and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/polygon-token-safety/">Polygon</a>.</p></blockquote><h2 level="2" textAlign="left" id="h-1-start-from-the-projects-official-source-not-from-search">1. Start From the Project&apos;s Official Source, Not From Search</h2><p>The first and highest-leverage check is also the most frequently faked: where did you get the address?</p><p>The correct routine is to navigate to the project&apos;s official website by typing the domain yourself or using a bookmark you saved earlier, find the token or contract address published there, and copy it directly. Then cross-check the same address against a second official channel, such as the project&apos;s verified X account, its GitHub repository, or its official documentation.</p><p>What breaks this check:</p><p><strong>Paid search ads.</strong> Attackers buy the top ad slot on Google for a token name or a DEX URL. The ad looks like the official site, sometimes with a domain that differs by one character. Anyone who clicks the ad and copies the &quot;official&quot; address from the landing page has completed the full verification routine against the attacker&apos;s own address.</p><p><strong>Compromised official channels.</strong> The hardware wallet distribution case above is the physical version. The on-chain version happens when a project&apos;s site, X account, or Discord gets compromised and starts posting a &quot;new contract&quot; or a &quot;migration&quot; address. In January 2024, the U.S. Securities and Exchange Commission&apos;s own X account was hijacked through a SIM-swap to post a fake Bitcoin ETF approval. If the source of record for an address can be hijacked, a single official channel is never enough, which is the entire point of cross-checking a second one.</p><p><strong>Fresh channels.</strong> A project whose website was registered three weeks ago, whose X account has posted for a month, and whose Telegram admin accounts were all created last week is not offering you an official source. It is offering you a stage set.</p><h2 level="2" textAlign="left" id="h-2-confirm-the-address-on-the-right-block-explorer-and-read-past-the-checkmark">2. Confirm the Address on the Right Block Explorer, and Read Past the Checkmark</h2><p>Once you have a candidate address, open it on the block explorer for the chain the token actually lives on. Etherscan for Ethereum, Basescan for Base, BscScan for BNB Chain, ArbScan for Arbitrum, Polygonscan for Polygon, Solscan for Solana. A token address that checks out on Etherscan but is being sold to you on Base is a red flag by itself, because scammers rely on buyers not noticing which chain they are on.</p><p>Three things to actually read on the explorer page:</p><p><strong>The token name and symbol versus the real thing.</strong> Fake tokens freely use the exact name and symbol of a legitimate token. Names are not unique on-chain. The contract address is the only identifier that cannot be imitated, only approximated.</p><p><strong>The verified badge, correctly understood.</strong> A verified contract on an explorer means the deployed bytecode matches source code the deployer submitted. That is all it means. It does not mean the code is safe, does not mean an auditor read it, and does not mean the deployer is who they claim. A <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/honeypot/">honeypot</a> with a buy-only modifier can be fully verified, and professional scam operations verify their contracts precisely because buyers treat the badge as a safety signal.</p><p><strong>What the code actually does.</strong> For most buyers the practical shortcut is the scam scanner in the next section. For anyone who can read Solidity, the highest-value minutes you can spend are on the transfer function, the mint function if one exists, and any owner-only functions. Our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/erc20-token-security-check/">ERC-20 token security check guide</a> walks through this line by line.</p><p>What breaks this check: cloned contracts. A scammer copies the full source of a legitimate token, deploys it at a new address, and verifies it. Every code-level check passes because the code is genuinely the real token&apos;s code. Only the address differs, which is why the source check in step 1 and the address comparison in step 5 still matter.</p><h2 level="2" textAlign="left" id="h-3-run-a-scanner-then-re-scan-before-you-buy">3. Run a Scanner, Then Re-Scan Before You Buy</h2><p>Automated token scanners are the fastest way to surface contract-level risk without reading code. They parse the contract, simulate a buy and a sell, and flag what they find.</p><ul><li><p><strong>GoPlus Security</strong> covers major EVM chains and checks dozens of risk indicators: honeypot behavior, hidden mint functions, ownership not renounced, trading taxes, and proxy contracts.</p></li><li><p><strong>Token Sniffer</strong> supports Ethereum and Base with automated scam scores and copy-contract detection.</p></li><li><p><strong>RugCheck</strong> is the standard for Solana, where the critical risks are not in Solidity at all but in token authorities: mint authority, freeze authority, and liquidity pool ownership.</p></li></ul><p>Two failure modes to keep in mind.</p><p><strong>Scanners are snapshots.</strong> A scan reflects the contract at scan time. Contracts that retain owner privileges can be configured to look clean, pass scans, accumulate buyers, and then activate a mint function or change a fee. The scan you ran yesterday is not a guarantee about the contract today. Re-scan immediately before a large purchase.</p><p><strong>Clean scans are a selling point.</strong> Well-funded operations test their contracts against the major scanners before launch and iterate until the score is green, because a passing score is itself marketing material in the shill posts. Treat scanner results as one signal in the stack, not a verdict. Chain-specific setups matter here too: applying EVM scanner logic to Solana tokens misses the exact authorities that matter, which is why our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/solana-token-safety/">Solana token safety guide</a> uses a different checklist.</p><h2 level="2" textAlign="left" id="h-4-read-holders-and-liquidity-as-adversarial-data">4. Read Holders and Liquidity as Adversarial Data</h2><p>After the contract itself, the market data around a token is the next thing buyers check, and the next thing attackers manufacture.</p><p><strong>Holder counts.</strong> Thousands of wallets holding a token looks like adoption. Sybil farms create those wallets in batches for a few dollars. On low-fee chains, spinning up a thousand holder wallets costs less than a restaurant meal. Look instead at the distribution: how much supply sits in the top ten wallets, how many wallets were funded from the same source in the same block range, and whether the earliest holders all bought within minutes of launch.</p><p><strong>Liquidity depth.</strong> A pool with millions in liquidity looks safe because exit looks possible. Verify whether the liquidity is locked or burned, and for how long, with our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-check-liquidity-locked/">liquidity lock check guide</a>. Unlocked liquidity in a pretty chart is just an exit ramp for the operator.</p><p><strong>Volume and the chart.</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/wash-trading/">Wash trading</a> cycles the same capital between controlled wallets to manufacture volume, holder growth, and momentum. In the WIFDER case on Solana, the token showed a Raydium pool, thousands of holders, and a parabolic chart, and hit a $2.3 million market cap within six hours. The single unchecked variable, retained mint authority, let the creator print 50 billion tokens and drain the pool in under four seconds.</p><p>The correct reading order is contract first, market data second. Market data that looks strong while the contract retains owner privileges is not a good sign. It is the signature of an operation that invested in its own appearance.</p><h2 level="2" textAlign="left" id="h-5-compare-the-full-address-not-the-first-and-last-characters">5. Compare the Full Address, Not the First and Last Characters</h2><p>Address poisoning is the bypass aimed directly at the act of comparing addresses. The attacker generates a wallet that shares the first and last six or so characters with an address you already trust, then sends a zero-value transfer from it so the lookalike lands in your transaction history. Weeks later, when you copy &quot;your&quot; address or &quot;the project&apos;s&quot; address from history instead of from the source, you send to the poison address. Ledger&apos;s 2026 incident response documented this technique draining victims at scale alongside the hardware supply chain compromise; our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/address-poisoning-attacks-explained/">address poisoning field guide</a> traces the mechanics on-chain.</p><p>The same lookalike logic applies to contract addresses. A fake token contract can be generated to match the first and last characters of the real contract, and a tweeted screenshot of an address that shows only the ends proves nothing.</p><p>Defenses that hold:</p><ul><li><p>Verify the <strong>full</strong> address, middle characters included, or better, compare checksummed addresses programmatically where the tooling supports it.</p></li><li><p>Keep a personal address book and paste from it, never from transaction history.</p></li><li><p>Treat any token or wallet address that arrives via DM, reply chain, or a &quot;helpful&quot; community member pasting it into chat as poisoned until re-verified from the official source.</p></li></ul><h2 level="2" textAlign="left" id="h-6-weight-the-channel-that-brought-you-the-token">6. Weight the Channel That Brought You the Token</h2><p>The last check is meta, and it catches what the others miss. Ask where the token found you.</p><p>A token you discovered through a paid search ad, a cold DM, a Telegram group you joined last week, a reply under a large account, or an unsolicited &quot;airdrop&quot; has already told you something about its distribution strategy. None of these channels are disqualifying on their own, but all of them are the standard delivery mechanisms of <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/pig-butchering-crypto-tracing/">pig butchering</a> funnels and fake airdrop campaigns. Our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/airdrop-safety-checklist/">airdrop safety checklist</a> covers the claims side of this in detail.</p><p>The uncomfortable version of this check: if the token&apos;s marketing is primarily aimed at people who have not read a guide like this one, the token&apos;s economics depend on those people. That is a fact about the token, not just its audience.</p><h2 level="2" textAlign="left" id="h-the-best-way-to-verify-a-token-address-all-six-checks-in-order">The Best Way to Verify a Token Address: All Six Checks in Order</h2><ol><li><p>Get the address from the project&apos;s official site you navigated to yourself, not from search, ads, or chat.</p></li><li><p>Cross-check the same address on a second official channel, such as X or GitHub.</p></li><li><p>Open it on the correct chain&apos;s explorer. Read the name, the verification status, and the code, in that order of skepticism.</p></li><li><p>Scan it with the right scanner for the chain, and re-scan right before buying.</p></li><li><p>Check holder distribution and liquidity lock status as adversarial data.</p></li><li><p>Verify the full address character by character, and keep your own address book.</p></li></ol><p>Most fake tokens that drain wallets pass some of these checks. Very few pass all of them, because the checks are independent and faking all six at once costs more than most scams expect to recover. The verification is not in any single green light. It is in the stack.</p><p><em>This article is educational, not investment advice. For chain-specific verification walkthroughs, see our token safety guides for </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/erc20-token-security-check/"><em>Ethereum</em></a><em>, </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/solana-token-safety/"><em>Solana</em></a><em>, </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/base-chain-token-safety/"><em>Base</em></a><em>, </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/arbitrum-token-safety/"><em>Arbitrum</em></a><em>, </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/bnb-chain-token-safety/"><em>BNB Chain</em></a><em>, and </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/polygon-token-safety/"><em>Polygon</em></a><em>.</em></p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/best-ways-to-verify-token-addresses/"><em>https://theonchaindiary.com/articles/best-ways-to-verify-token-addresses/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/5bbb437a3d601173b49e4f19db091bb6c83a7fa4b6d89f0afdcedcedb8449fc0.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[MetaMask Infrastructure Incident Explained: Why Your Wallet Was Never at Risk]]></title>
            <link>https://paragraph.com/@onchaindiary/metamask-infrastructure-incident-explained</link>
            <guid>dFqC0SErhT1mP6Bo8fA8</guid>
            <pubDate>Sun, 11 Oct 2026 07:49:37 GMT</pubDate>
            <description><![CDATA[On September 30, 2026, MetaMask disclosed an ongoing security incident affecting part of its infrastructure. The announcement was deliberately narrow: the company was "actively addressing and remediating the issue internally, in coordination with external partners and security advisors," had identified "no immediate threat to MetaMask wallets," and was — as a precaution — proactively exiting affected validators within its non-custodial staking operations. That last sentence is where most of t...]]></description>
            <content:encoded><![CDATA[<p>On September 30, 2026, MetaMask <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://metamask.io/news/user-update">disclosed</a> an ongoing security incident affecting part of its infrastructure. The announcement was deliberately narrow: the company was &quot;actively addressing and remediating the issue internally, in coordination with external partners and security advisors,&quot; had identified &quot;no immediate threat to MetaMask wallets,&quot; and was — as a precaution — proactively exiting affected validators within its non-custodial staking operations.</p><p>That last sentence is where most of the story lives. This article walks through the timeline, the on-chain numbers, and the key architecture that explains why a breach of a major wallet company&apos;s infrastructure still could not touch your wallet.</p><h2 level="2" textAlign="left" id="h-the-timeline">The timeline</h2><ul><li><p><strong>September 30</strong> — MetaMask&apos;s first public statement: an ongoing incident affecting &quot;part of our infrastructure,&quot; no immediate threat to wallets, precautionary exits of affected validators in non-custodial staking. MetaMask reminded users that its staking operations &quot;do not manage withdrawal keys for stake on behalf of our clients.&quot; (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://metamask.io/news/user-update">MetaMask user update</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.bleepingcomputer.com/news/security/metamask-discloses-security-incident-affecting-its-infrastructure/">BleepingComputer</a>)</p></li><li><p><strong>October 1</strong> — Follow-up: no indication that MetaMask wallets or customer funds were affected. Lido also confirmed that MetaMask Staking (formerly Consensys Staking) had taken precautionary measures around Ethereum validators tied to client assets. (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cryptobriefing.com/metamask-security-incident-no-user-funds-affected/">Crypto Briefing</a>)</p></li><li><p><strong>October 2–4</strong> — Consensys founder Joseph Lubin addressed the incident directly: &quot;Your Secret Recovery Phrase, your keys, and the assets in your wallet were not part of this incident because they CANNOT be. You custody and control your own keys. That is how self custody works.&quot; Consensys and partners rotated validator keys, which Lubin described as operationally inconvenient but necessary to reduce residual risk. The company declined to discuss details of an open investigation. (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://ambcrypto.com/no-indication-that-metamask-wallets-were-affected-joseph-lubin-reassures-users/">AMBCrypto</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://blockonomi.com/joseph-lubin-no-metamask-wallets-or-customer-funds-affected-by-security-incident">Blockonomi</a>)</p></li></ul><h2 level="2" textAlign="left" id="h-the-numbers-on-chain">The numbers on chain</h2><p>Two figures anchor the incident&apos;s real footprint. First, roughly 17,000 validators — together holding around 523,000 ETH — began exiting as a precaution (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cryptobriefing.com/metamask-security-incident-no-user-funds-affected/">Crypto Briefing</a>). Second, an on-chain researcher traced approximately 0.36 ETH in rewards diverted from 18 of the 19 affected validators: a tiny amount of money, but a clear signal that someone had touched validator reward flows.</p><p>Note the asymmetry: about half a million ETH of principal, unmoved; about a third of one ETH of rewards, skimmed. That asymmetry is not luck. It is Ethereum&apos;s key separation doing exactly what it was designed to do.</p><p>Press coverage of exit-queue data also noted that the ETH waiting to leave staking roughly quadrupled in the days after the disclosure (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://ambcrypto.com/no-indication-that-metamask-wallets-were-affected-joseph-lubin-reassures-users/">AMBCrypto</a>) — a reminder that &quot;precautionary exit&quot; still has a real cost in foregone rewards and queue time.</p><h2 level="2" textAlign="left" id="h-why-your-wallet-was-never-exposed">Why your wallet was never exposed</h2><p>Two architectural facts separate this incident from a fund-draining hack.</p><p><strong>1. MetaMask does not have your keys.</strong> MetaMask is a self-custody wallet. Your Secret Recovery Phrase and private keys are generated and stored on your device. There is no vault at MetaMask headquarters to break into — which is what Lubin&apos;s &quot;they CANNOT be&quot; statement means in plain terms. An intruder in the company&apos;s infrastructure never had a path to keys the company never held.</p><p><strong>2. Validator keys and withdrawal keys are separate.</strong> Ethereum&apos;s staking design splits a validator into two credentials. The validator key does the daily work — proposing blocks, attesting, collecting rewards. The withdrawal credential decides where the staked ETH ultimately goes. Consensys runs validators for its staking product but explicitly does not hold withdrawal keys for clients. So an attacker sitting inside validator infrastructure can disrupt operations and skim rewards, but cannot redirect the principal. Lubin made this exact point: an issue in validator infrastructure cannot result in improper movement of the underlying ETH (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://blockonomi.com/joseph-lubin-no-metamask-wallets-or-customer-funds-affected-by-security-incident">Blockonomi</a>).</p><p>This is also the honest framing for anyone using staking products: <strong>non-custody protects your principal. It does not fully protect your yield.</strong> Your yield depends on the operator&apos;s infrastructure staying clean — and when it doesn&apos;t, the cost shows up as skimmed rewards and downtime, not stolen stake.</p><h2 level="2" textAlign="left" id="h-the-follow-up-attack-you-should-actually-watch-for">The follow-up attack you should actually watch for</h2><p>When a security incident makes headlines, the reliable second act is phishing. Scammers replay the news back at you: an urgent &quot;security notice,&quot; a fake wallet-update page, a DM from &quot;MetaMask support&quot; asking you to verify your account or move funds to a &quot;safe&quot; wallet.</p><p>The filtering rule is the same one that applies to <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/fake-customer-support-scams/">every fake support scam</a>: real support never contacts you first — not by phone, not by DM, not by email you didn&apos;t initiate. There is no customer-support process in crypto that requires your recovery phrase, a &quot;verification&quot; signature, or remote access to your device. If someone reaches out about this incident and asks for any of those, they are running the follow-up scam, not the recovery.</p><p>If you want to check whether anything in your own wallet has actually changed — approvals, activity, unfamiliar transactions — <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-audit-your-wallet-activity/">auditing your own wallet activity</a> takes a few minutes and beats guessing.</p><p>Incidents like this also renew a healthy suspicion of &quot;trusted infrastructure&quot; in general: a real domain with a real product can still end up serving you a malicious prompt if its operator is compromised, which is the same lesson from the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/giwa-fake-rpc-bridge-scam-explained/">fake GIWA mainnet incident</a>. Trust the architecture you can verify, not the brand on the box.</p><h2 level="2" textAlign="left" id="h-what-to-do-now">What to do now</h2><p>Almost nothing. MetaMask&apos;s guidance is that users do not need to act; funds and settings can stay as they are. Rotating your Secret Recovery Phrase over this incident is unnecessary theater.</p><p>The two things worth doing are free: treat inbound &quot;support&quot; contact about the incident as hostile by default, and if you use MetaMask&apos;s staking product, expect some reward downtime while validators re-enter the queue — that is the precaution working as intended, not a loss.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/metamask-infrastructure-incident-explained/"><em>https://theonchaindiary.com/articles/metamask-infrastructure-incident-explained/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/eb1543d7c68cefec474b44a7d1e03f434d904ba541f465f7c331d7c260db9c31.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[The $86M 'Ledger Hack': What the On-Chain Evidence Actually Shows]]></title>
            <link>https://paragraph.com/@onchaindiary/ledger-drain-address-poisoning</link>
            <guid>sf6g0sFApjuF7u3ejTPB</guid>
            <pubDate>Sun, 11 Oct 2026 07:49:30 GMT</pubDate>
            <description><![CDATA[On October 9, 2026, on-chain analyst Specter (@SpecterAnalyst) flagged a coordinated drain of Ledger user wallets spanning Ethereum, TRON, and Bitcoin. Headlines quickly settled on "$86M+ stolen from Ledger users," with some reports suggesting the final figure could approach $100 million. Crypto Briefing and others framed the cause as a mystery — a possible device flaw, a seed compromise, or phishing, with Ledger staying silent. We pulled the full transaction history of all ten flagged theft ...]]></description>
            <content:encoded><![CDATA[<p>On October 9, 2026, on-chain analyst Specter (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/SpecterAnalyst/status/2108534068564373687">@SpecterAnalyst</a>) flagged a coordinated drain of <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/hardware-wallet/">Ledger</a> user wallets spanning Ethereum, TRON, and Bitcoin. Headlines quickly settled on &quot;$86M+ stolen from Ledger users,&quot; with some reports suggesting the final figure could approach $100 million. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cryptobriefing.com/ledger-users-drained-86-million-exploit/">Crypto Briefing</a> and others framed the cause as a mystery — a possible device flaw, a seed compromise, or phishing, with Ledger staying silent.</p><p>We pulled the full transaction history of all ten flagged theft addresses and traced the money ourselves. Our initial read — published hours after the news broke — saw an address-poisoning pattern in the zero-value transfers around the victim wallets. Hours later, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://finance.yahoo.com/markets/crypto/articles/ledger-pauses-reseller-sales-86-135100065.html">Ledger&apos;s official response</a> and CZ&apos;s comments pointed somewhere more specific: a <strong>supply-chain compromise through Malaysian reseller CryptoBilis</strong>, with devices that may have been tampered with or counterfeit before sale. That explanation fits the on-chain evidence at least as well — and it keeps the core conclusion intact: <strong>the firmware and genuine devices were not breached. The channel was.</strong></p><p><strong>BLUF:</strong></p><ul><li><p>The ten published addresses took in <strong>~$91.6M gross</strong> at press-time prices: <strong>65,245,481 USDT on TRON</strong> (137 external transfers, 136 senders — 96 of them moved ≥$100K each, median transfer ~$150K, largest $7M), 211.2 BTC ≈ $17.5M, 3,337 ETH ≈ $8.3M, plus ~$0.6M USDT on Ethereum. The TRON USDT has since been <strong>fully swept out</strong> of the four addresses; the BTC and the ETH still sit there.</p></li><li><p>Specter&apos;s <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://coinpedia.org/news/ledger-crypto-theft-86-9-million-reportedly-drained-across-98-wallet-addresses/">full tally</a> — <strong>$86.96M across 98 addresses</strong>, with tanuki42 independently estimating $72M+ — is a <em>holdings snapshot</em> at posting time, not cumulative inflow (its 211.199 BTC matches our three Bitcoin addresses). The two figures are different lenses on one operation, and Ledger has not endorsed either.</p></li><li><p>The ETH transfers we sampled are plain sends — no <code>approve()</code>, no blind signing, no drainer contract. (USDT transfers are contract calls by nature, and one matched TRON victim did leave an <code>Approve</code> — but the dominant shape is plain sends, consistent with a compromised seed rather than a signing exploit.)</p></li><li><p>Victim wallets were bracketed by <strong>zero-value transactions from lookalike vanity addresses</strong> (<code>0x69c8…</code> / <code>0x83ae…</code> clusters). We first read those as poisoning bait; on closer timeline review most land <em>after</em> the big sends, which reads more like the attacker&apos;s own operational addresses than bait.</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.wublock123.com/news/ledger-users-wallets-drained-86m-plus-assets-stolen-69802">Wu Blockchain</a> reports Ledger is investigating Southeast Asian buyers who purchased through distributor CryptoBilis; CZ called it a likely single-vendor supply-chain attack.</p></li></ul><h2 level="2" textAlign="left" id="h-what-the-ten-addresses-actually-received">What the ten addresses actually received</h2><p>Using Etherscan V2, Tronscan, and blockchain.info, we paginated through every inbound transfer to the ten addresses Specter published (address-by-address, full history, not first-page samples):</p><table class="paragraph-table"><colgroup><col><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Chain</p></th><th colspan="1" rowspan="1"><p>Amount</p></th><th colspan="1" rowspan="1"><p>≈ USD (press time)</p></th><th colspan="1" rowspan="1"><p>Distinct senders</p></th></tr><tr><td colspan="1" rowspan="1"><p>Ethereum (ETH)</p></td><td colspan="1" rowspan="1"><p>3,337.35 ETH</p></td><td colspan="1" rowspan="1"><p>$8.29M</p></td><td colspan="1" rowspan="1"><p>~40</p></td></tr><tr><td colspan="1" rowspan="1"><p>Ethereum (USDT, ERC-20)</p></td><td colspan="1" rowspan="1"><p>~605,845 USDT</p></td><td colspan="1" rowspan="1"><p>$0.61M</p></td><td colspan="1" rowspan="1"><p>—</p></td></tr><tr><td colspan="1" rowspan="1"><p>Bitcoin</p></td><td colspan="1" rowspan="1"><p>211.20 BTC</p></td><td colspan="1" rowspan="1"><p>$17.47M</p></td><td colspan="1" rowspan="1"><p>260 inbound txs</p></td></tr><tr><td colspan="1" rowspan="1"><p>TRON (USDT)</p></td><td colspan="1" rowspan="1"><p>65,245,481 USDT</p></td><td colspan="1" rowspan="1"><p>$65.2M</p></td><td colspan="1" rowspan="1"><p>136 senders, 137 external txs</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Total gross inflow</strong></p></td><td colspan="1" rowspan="1"><br></td><td colspan="1" rowspan="1"><p><strong>≈ $91.6M</strong></p></td><td colspan="1" rowspan="1"><br></td></tr></tbody></table><p>The TRON side is not a retail-longtail pattern: 96 of the 136 senders moved <strong>≥$100K each</strong> (together $63.9M), transfers under $10K number just 15 (~$16K combined), the median transfer is ~$150K, and the single largest is <strong>$7M</strong>. On Ethereum, inflows were similarly concentrated: ~40 senders averaging ~80 ETH each, led by a single 298.23 ETH transfer. This is wholesale wallet-sweeping, not nickel-and-dime collection.</p><p>One correction to the coverage: Crypto Briefing wrote that Bitcoin address <code>bc1qjqgwejnp8dc0x2938x9n9954hj97t82unx49dl</code> &quot;has reportedly received over 211 BTC.&quot; It received <strong>92.5 BTC</strong>. The 211 BTC figure is the sum of all three flagged Bitcoin addresses (92.5 + 111.3 + 7.4). Small error, but it shows how quickly unverified numbers harden into &quot;facts&quot; during a breaking event.</p><p>A larger correction to our own earlier framing, courtesy of a full TRON-grid pull that superseded our first TRON numbers (our initial TRC-20 statistics via the Tronscan web API missed the large transfers — an object lesson in why explorer convenience endpoints are not archives). The 10 public addresses alone grossed <strong>~$91.6M</strong> — more than Specter&apos;s $86.96M figure, which is a holdings snapshot at posting time rather than cumulative inflow. There is no missing &quot;$59M on unpublished addresses&quot; from our earlier decomposition; the TRON USDT ($65.2M) simply flowed through these four addresses and out again. What remains on the 10 addresses today is the BTC ($17.5M) and the ETH ($8.3M) — the part the thief hasn&apos;t laundered yet, and the part everyone can watch.</p><h2 level="2" textAlign="left" id="h-the-zero-value-fingerprints">The zero-value fingerprints</h2><p>Here is where it gets interesting. We pulled the full transaction history of the first large Ethereum victim — the address that sent 298.23 ETH to thief address <code>0x69c8f401…</code> at 05:09 UTC on October 9.</p><p>The minutes around the transfer look like this:</p><ul><li><p>05:09 — victim sends <strong>298.23 ETH</strong> to <code>0x69c8f401…</code> (plain transfer, empty input data)</p></li><li><p>05:11–05:12 — victim sends 14.91 ETH and 0.75 ETH to a second thief address, <code>0x83aeac16…</code></p></li><li><p>05:12–05:49 — the victim&apos;s address receives a string of <strong>0-value transactions</strong> from senders including <code>0x69c8c5f6…</code>, <code>0x69c888f9…</code>, <code>0x69c8b3e9…</code>, <code>0x83ae9f19…</code>, and <code>0x83ae51cd…</code></p></li></ul><p>Look at the prefixes. The zero-value senders share their first four hex characters with the two thief addresses: <code>0x69c8…</code> and <code>0x83ae…</code>. Four matching hex characters occur naturally in roughly 1 in 65,536 random addresses. Finding <strong>five</strong> lookalike addresses clustered around <strong>two</strong> thief addresses is not a coincidence — those are deliberately generated <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/vanity-address/">vanity addresses</a>.</p><p>This is the address-family fingerprint of a prepared operation. When we first published, we read this cluster as the bait layer of an <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/address-poisoning/">address poisoning</a> campaign — the same play we broke down in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/address-poisoning-attacks-explained/">Address Poisoning Attacks Explained</a> and a close cousin of <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-dusting-attacks-explained/">dusting attacks</a>. On closer review of the timestamps, however, most of the zero-value transfers land <strong>after</strong> the big sends, not before. Poisoning bait has to precede the victim&apos;s mistake to work; trailing zero-value traffic reads more like the attacker&apos;s own operational footprint — gas top-ups, tagging, or consolidation among addresses they generate with matching prefixes for bookkeeping.</p><p>Either way, the cluster proves one operator ran this at scale, with tooling, across three chains.</p><h2 level="2" textAlign="left" id="h-the-supply-chain-explanation-that-fits-everything">The supply-chain explanation that fits everything</h2><p>Hours after our first publish, two things landed. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.wublock123.com/news/ledger-users-wallets-drained-86m-plus-assets-stolen-69802">Wu Blockchain reported</a> that Ledger is investigating Southeast Asian users who bought devices through distributor <strong>CryptoBilis</strong> — a Malaysian shop founded in 2020 that also operates in Indonesia and the Philippines. Ledger Support asked CryptoBilis to pause all sales and shipments, told buyers from the past 90 days <strong>not to initialize their devices</strong>, and told anyone who already had to <strong>move funds to a new device with a new seed phrase</strong>. CZ separately called it a likely single-vendor supply-chain attack, with some users possibly holding tampered or counterfeit units.</p><p>A tampered or fake device explains every on-chain observation — including the ones that made us hesitate:</p><p><strong>Almost no signature-trick footprint.</strong> The ETH transfers we sampled carry empty input data — plain sends, no <code>approve()</code>, no blind signing, no drainer contract like the ones in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/wallet-drainer/">wallet drainer</a> campaigns. Two honest qualifications: any USDT transfer <em>is</em> a contract call (that&apos;s how ERC-20/TRC-20 works), and at least one victim matched to TRON address <code>TK6DWN…</code> did leave an <code>Approve</code> on-chain. Still, the dominant shape is plain sends — and a holder of the seed can sign both kinds equally, so this fits key compromise rather than a signing-flow exploit.</p><p><strong>Multi-chain consistency.</strong> BTC, ETH, and TRON moved in the same window from plausibly the same owners (one Ledger seed derives addresses on all three). A key holder sweeps everything they can at market-rate gas — which is the shape we see: plain sends across all three networks, the TRON USDT consolidated out within hours, the ETH later swapped and moved as well. (To be precise about &quot;still sitting there&quot;: the <em>ether</em> balance of the three EVM addresses is unchanged, but their USDT has been forwarded and some swaps occurred.)</p><p><strong>Victims who &quot;never exposed their seed.&quot;</strong> Multiple Reddit victims insisted they never typed their 24 words anywhere and barely interacted with dapps. With a tampered device, they&apos;re right — they never leaked it. It was never exclusively theirs to begin with: a fake or altered unit can ship with a preloaded seed, or with firmware that exfiltrates it during setup. (A researcher documented exactly this on counterfeit Ledger units sold through a Chinese marketplace in April 2026.)</p><p><strong>The week-long gap.</strong> The first TRON collection address went live October 2; the mass drain hit October 9. A supply-chain attacker with preloaded seeds doesn&apos;t strike immediately — they let balances accumulate, then sweep in one coordinated window.</p><p>What this is <em>not</em>, on current evidence: a firmware vulnerability in genuine devices, or a failure of the Ledger security model itself. The device did its job; the box it shipped in had already been compromised. And note Ledger has not confirmed the $86M figure nor explained the mechanism — the supply-chain framing is the strongest current hypothesis, not a settled fact.</p><h2 level="2" textAlign="left" id="h-timeline-of-the-operation">Timeline of the operation</h2><ul><li><p><strong>Oct 2, 15:20 UTC</strong> — first flagged TRON collection address is created and begins receiving test payments. A week of quiet setup.</p></li><li><p><strong>Oct 9, 05:09–05:55 UTC</strong> — the three Ethereum thief addresses activate within 46 minutes of each other; three more TRON addresses come online in the same window. The main drain begins.</p></li><li><p><strong>Oct 9, 10:26 UTC</strong> — a seventh collection address appears. The operation is still scaling.</p></li><li><p><strong>Oct 9, ~12:36 UTC</strong> — Wu Blockchain reports Ledger is investigating CryptoBilis-sourced devices in Southeast Asia; Ledger asks the reseller to halt sales.</p></li><li><p><strong>Oct 9, ~13:47 UTC</strong> — Coinpedia publishes Specter&apos;s fuller tally: $86.96M across 98 addresses; tanuki42&apos;s independent estimate of $72M+ corroborates the scale. CoinDesk notes the tracked addresses hold only ~$25M at last check — most of the non-published money has already moved.</p></li><li><p><strong>Oct 9, 13:31 UTC</strong> — most recent inbound TRON transfer at time of writing. Still live.</p></li><li><p><strong>Laundering status</strong> — all 211.2 BTC ($17.5M) and 3,337 ETH ($8.3M) sit <strong>unmoved</strong> in the flagged addresses (independently confirmed against mempool data by BeInCrypto at 13:44 UTC). Every cent of TRON USDT has already been swept out and consolidated. Watching those addresses is now trivially easy for exchanges and chain-analytics teams, which is likely why the big bags haven&apos;t moved — recall from <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/after-wallet-drainer-what-now/">the After a Wallet Drainer, What Now playbook</a> that thieves typically age funds or fragment through mixers before cashing out.</p></li></ul><h2 level="2" textAlign="left" id="h-if-you-hold-crypto-do-these-things-now">If you hold crypto, do these things now</h2><p><strong>First, the channel check (official Ledger guidance):</strong> if you bought a Ledger from CryptoBilis in the past 90 days — do not initialize it. If you already set it up, move your funds to a <strong>new device with a new seed phrase</strong>, bought directly from Ledger&apos;s official store. Never buy hardware wallets from third-party marketplaces; the April 2026 counterfeit-Ledger findings showed fake units shipping with seed-exfiltrating firmware.</p><p><strong>Then, hygiene that protects you regardless of the vector:</strong></p><ol><li><p><strong>Never copy addresses from your transaction history.</strong> That&apos;s the surface attackers poison. Pull addresses only from your verified source — the exchange&apos;s deposit page, the recipient&apos;s official site.</p></li><li><p><strong>Check first and last 6+ characters.</strong> Vanity mimicking usually copies only the edges; the middle diverges. Six characters each side catches most lookalikes.</p></li><li><p><strong>Use an allowlist for repeat payments.</strong> Most wallets support saved/verified contacts. Pay saved addresses, not pasted ones.</p></li><li><p><strong>Send a test transaction first.</strong> For anything above rounding error, move $20 before you move $20,000.</p></li></ol><p>And if you were affected by this specific incident: the BTC and ETH remain in unmoved, publicly flagged addresses — report to the receiving-chain explorers&apos; fraud tags and to your local cybercrime unit while the trail is still this fresh. For the broader playbook, see <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-avoid-crypto-phishing-scams/">How to Avoid Crypto Phishing Scams</a> and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-audit-your-wallet-activity/">How to Audit Your Own Wallet Activity</a>.</p><p><em>Update log: initial version (Oct 9, ~14:20 UTC) attributed the pattern to address poisoning based on the zero-value vanity cluster. Ledger&apos;s CryptoBilis response and CZ&apos;s supply-chain comments, surfaced in Chinese-language media from ~12:36 UTC, were incorporated later the same day, along with a timestamp re-check that moved most zero-value transfers to after the main sends. Core verified findings — $27.1M traceable, zero contract calls, 211 BTC unmoved — are unchanged. Evening update: the $86M was reconciled — Specter&apos;s full tally is $86.96M across 98 addresses (Coinpedia), with our $27.1M being the verified, still-unmoved portion on the 10 published addresses. Second evening correction: a full TRON-grid pull of TRC-20 records superseded our initial TRON statistics — the Tronscan convenience API had missed the large transfers, understating TRON inflow ~90x. Corrected figures: 65,245,481 USDT across 137 external transfers (median ~$150K, max $7M); 10-address gross inflow ≈ $91.6M; Specter&apos;s $86.96M is a holdings snapshot, not cumulative inflow. Timeline corrected (first TRON address created Oct 2 09:20:54 UTC; last external USDT inflow Oct 9 11:41:36 UTC). &apos;Zero contract calls&apos; qualified — USDT transfers are by nature contract calls, and one matched TRON victim left an Approve. The URL slug retains the initial &apos;address-poisoning&apos; framing for link stability; the article&apos;s conclusion supersedes it. We will keep updating as the addresses move or Ledger publishes findings.</em></p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-drain-address-poisoning/"><em>https://theonchaindiary.com/articles/ledger-drain-address-poisoning/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/aacecff18bb32514ed90f565a178b72e0f699c314ab5efdfbbe482d0000c6446.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[The Ledger–CryptoBilis Hack: How Buying a Trusted Reseller Became the Attack]]></title>
            <link>https://paragraph.com/@onchaindiary/ledger-cryptobilis-supply-chain-hack</link>
            <guid>kQvk8NUiYSqMDl32q0WV</guid>
            <pubDate>Sun, 11 Oct 2026 07:49:24 GMT</pubDate>
            <description><![CDATA[The most instructive hack of 2026 isn't a smart contract bug. It's a story about buying a company. On October 9, Ledger users in Southeast Asia woke up to empty wallets. By the end of the day, investigators had traced an estimated $72M–$90M to roughly 98 collection addresses across Bitcoin, Ethereum, and Tron; Tether had frozen what it could; and the attacker was already pushing funds through Tornado Cash. The devices at the center of it all came from one place: CryptoBilis, an authorized Led...]]></description>
            <content:encoded><![CDATA[<p>The most instructive hack of 2026 isn&apos;t a smart contract bug. It&apos;s a story about buying a company.</p><p>On October 9, Ledger users in Southeast Asia woke up to empty wallets. By the end of the day, investigators had traced an estimated $72M–$90M to roughly 98 collection addresses across Bitcoin, Ethereum, and Tron; Tether had frozen what it could; and the attacker was already pushing funds through Tornado Cash. The devices at the center of it all came from one place: CryptoBilis, an authorized Ledger reseller.</p><p>Then came the detail that reframed everything. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.odaily.news/zh-CN/newsflash/523609">Per Bitcoin News, citing Malaysian corporate records</a>: as of August 3, 2026, CryptoBilis was 100% owned by a Chinese national named Jiaming, registered at an address in Heilongjiang province. The company&apos;s former co-founder confirmed the sale closed in March — and that the original team had exited everything, kept from speaking by a confidentiality agreement.</p><p>A trusted distribution channel changed hands in secret. Seven months later, its customers&apos; wallets drained in a day. That sequence — not any single vulnerability — is what makes this case a textbook study in how supply-chain attacks actually work.</p><h2 level="2" textAlign="left" id="h-the-full-timeline">The full timeline</h2><table class="paragraph-table"><colgroup><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Date</p></th><th colspan="1" rowspan="1"><p>Event</p></th></tr><tr><td colspan="1" rowspan="1"><p>Dec 2020</p></td><td colspan="1" rowspan="1"><p>CryptoBilis founded in Malaysia by Arravind Prabu, Vimal Selvamany, and Dhivager Rathakrishnan under parent Fetch International (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://vulcanpost.com/737143/cryptobilis-malaysia-merch-store-cryptocurrency-payment/">Vulcan Post</a>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Through 2025</p></td><td colspan="1" rowspan="1"><p>Builds regional reputation: authorized Ledger reseller for Malaysia, Indonesia, Philippines; hosts Bitcoin Pizza Day events; CEO is president of Malaysia&apos;s ACCESS Blockchain Association</p></td></tr><tr><td colspan="1" rowspan="1"><p>Mar 2026</p></td><td colspan="1" rowspan="1"><p>Company acquired; original founders exit all operations, management, and administration — confirmed by former co-founder</p></td></tr><tr><td colspan="1" rowspan="1"><p>Aug 3, 2026</p></td><td colspan="1" rowspan="1"><p>SSM records show Jiaming (Heilongjiang, China) holds 100% of shares</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 8</p></td><td colspan="1" rowspan="1"><p>Mark Karpelès warns on X that tampered Ledgers with hidden implants are circulating; one device he examined came from Malaysia, in intact shrink wrap; the warning draws ~90K views</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 9, ~06:00 UTC</p></td><td colspan="1" rowspan="1"><p>Collection addresses begin receiving large USDT transfers</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 9, 12:24</p></td><td colspan="1" rowspan="1"><p>Specter publishes ten collection addresses across BTC/ETH/Tron; $86M+ estimate</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 9, 13:32</p></td><td colspan="1" rowspan="1"><p>Ledger confirms investigation, orders CryptoBilis to halt all sales and shipments</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 9, 14:01</p></td><td colspan="1" rowspan="1"><p>CZ calls it a supply-chain attack via a single vendor</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 9, afternoon</p></td><td colspan="1" rowspan="1"><p>MistTrack nears $90M; Tether freezes linked USDT</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 9, 16:30</p></td><td colspan="1" rowspan="1"><p>430.2 ETH moves through Tornado Cash; USDT swapped to USDD via Sun.io and PSM</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 9, 16:48</p></td><td colspan="1" rowspan="1"><p>SSM ownership findings published; former co-founder confirms March acquisition</p></td></tr></tbody></table><p>The minute-level flow on October 9 is documented by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.theblock.co/news/business/2026-10-09-ledger-cryptobilis-fund-losses-418163">The Block</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.coindesk.com/business/2026/10/09/ledger-investigates-potential-wallet-tampering-after-reports-of-usd86-million-in-crypto-stolen">CoinDesk</a>, and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cryptoticker.io/en/ledger-hack-cryptobilis-86-million-hardware-wallet/">CryptoTicker</a>.</p><h2 level="2" textAlign="left" id="h-the-shell-that-got-bought">The shell that got bought</h2><p>CryptoBilis was, by every public signal, a legitimate operation. Founded in late 2020 by a team that also ran a crypto payments company, it grew into what <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.cryptobilis.com.ph/isawwwshop-buyout-boosts-crypto-security/">its own marketing called</a> Southeast Asia&apos;s leading crypto commerce platform — selling Ledger, Trezor, OneKey, Tangem, and SafePal devices across Malaysia, Indonesia, and the Philippines. Its co-founder sat at the top of Malaysia&apos;s blockchain industry association. It organized the region&apos;s Bitcoin Pizza Day events. Its name, a play on <em>ikan bilis</em> (Malay for anchovies — the little fish next to crypto whales), was a local in-joke people trusted.</p><p>That is precisely what made it worth buying.</p><p>For an attacker, acquiring a five-year-old authorized reseller is cheaper and more reliable than counterfeiting one from scratch. The &quot;authorized reseller&quot; badge transfers with the company. The customer base transfers. The logistics chain — warehouses, packaging, shipping — transfers. Nothing about the storefront needs to change, and per the former co-founder&apos;s account, nothing did: the company kept selling, kept running events, kept its public face while the people who built it walked out of operations entirely in March.</p><p>Whether Jiaming or the acquiring entity directed the device tampering is <strong>not established</strong>. What the record shows is narrower and still damning as a pattern: the devices that drained wallets came from a channel whose ownership quietly changed hands months earlier, and nobody — not Ledger, not the customers — was any the wiser. A distribution channel is a trust product, and this one was sold without the trust being re-underwritten.</p><h2 level="2" textAlign="left" id="h-the-implant-hardware-that-passes-the-genuine-check">The implant: hardware that passes the genuine check</h2><p>The mechanism, per Mark Karpelès — who says he was investigating a related issue before the incident and asked victims to send him circuit-board photos — is physical, not cryptographic:</p><ul><li><p>A hidden implant sits <strong>under the screen</strong>, intercepting the data sent to the display.</p></li><li><p>When the user sets up the wallet, the recovery phrase shown on screen is captured and transmitted.</p></li><li><p>The original <strong>secure element remains intact</strong>, so Ledger&apos;s genuine-device verification passes — the check confirms Ledger&apos;s chip is genuine, not that nothing else was added.</p></li><li><p>The tampered device arrives in <strong>intact shrink wrap</strong>, defeating the standard &quot;check the seals&quot; advice.</p></li></ul><p>This explains the theft pattern better than phishing would. Lookonchain traced one victim who bought 80 BTC at ~$65,000 four months earlier, deposited all of it into a Ledger bought from CryptoBilis a week before the incident — gone. Another address, tagged TY24Ya, bought a device three weeks prior, loaded 7 million USDT, and lost the entire amount in a single sweep: likely the largest single loss in the case. Across Specter&apos;s Arkham data, the drains averaged roughly $890,000 per address — versus about $21,000 per victim in the Coldcard incident two months earlier. (Our companion piece traces the ten flagged theft addresses transaction by transaction; the verifiable-loss floor there is ~$27M, well below the $86M headline estimate.) An attacker holding harvested seed phrases can simply wait, watch balances accumulate, and take only the wallets worth taking.</p><p>And there is a chilling wrinkle in the timing. Karpelès posted his warning about implant-carrying devices on <strong>October 8</strong> — the day before the coordinated sweep. The warning drew around 90,000 views. The emerging speculation, explicitly flagged as unconfirmed, is that the attacker saw the warning, realized exposure was imminent, and triggered the mass drain overnight. If true, the community&apos;s own early warning system rang the bell that started the slaughter.</p><h2 level="2" textAlign="left" id="h-the-laundering-freezes-swaps-and-the-mixer">The laundering: freezes, swaps, and the mixer</h2><p>The hours after the drain turned into a live demonstration of stablecoin attack surface:</p><ol><li><p><strong>Tether froze first.</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cryptobriefing.com/tether-freezes-usdt-ledger-user-thefts/">MistTrack confirmed</a> large USDT freezes at linked addresses — freezing in place a chunk of the ~$16.5M in USDT that Specter&apos;s Arkham snapshot showed.</p></li><li><p><strong>The attacker swapped to USDD.</strong> Following the freezes, funds moved through Sun.io and the USDD Peg Stability Module into USDD — a Tron-based stablecoin Tether cannot freeze — with some routed onward to Binance hot wallets, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://phemex.com/tr/news/article/ledger-hack-suspect-converts-usdt-to-usdd-still-holds-706m-in-assets-99336">as Onchain Lens data showed</a>. Onchain Lens publicly called on Binance to freeze linked accounts.</p></li><li><p><strong>ETH went through Tornado Cash.</strong> 430.2 ETH (~$1.07M) across four wallets entered the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/tornado-cash/">Tornado Cash</a> mixer, breaking deterministic traceability — see our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/mixer/">mixer</a> explainer for why this works.</p></li><li><p><strong>The bulk is still visible.</strong> Arkham-tagged addresses held ~$70.6M at last count: 11,406 ETH, 213.37 BTC, 13.65M USDD, and 10.91M USDT. Every hour it sits there is a window for freezes; every swap shrinks it.</p></li></ol><h2 level="2" textAlign="left" id="h-what-this-case-teaches">What this case teaches</h2><p><strong>For users: the seller is part of the threat model.</strong> The rule that survived this incident: buy hardware wallets from the manufacturer directly, generate your own <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/seed-phrase/">seed phrase</a> on-device, and treat a new device as unproven for its first weeks — CZ&apos;s advice to leave a fresh device unused for a while before funding it would have saved several victims here. Our earlier piece on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/hardware-wallet-scams-explained/">hardware wallet scams</a> covers the pre-filled-seed variant of the same attack; this case adds the scarier upgrade, an implant that survives the genuine-device check. If you drained funds, the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/stolen-crypto-first-24-hours/">first-24-hours checklist</a> still applies — fast reporting is what makes interception possible.</p><p><strong>For vendors: reseller badges are liabilities if unmonitored.</strong> Ledger authorized this reseller, and the authorization outlived the company&apos;s original owners. A vendor that doesn&apos;t track ownership changes in its distribution chain is underwriting trust for whoever buys the shell. After this, expect &quot;authorized reseller&quot; programs to come with ownership-change disclosure clauses — and expect buyers to ask.</p><p><strong>For the industry: reputation is transferable, and that&apos;s the vulnerability.</strong> Five years of community events, an industry-association president as founder, official badges — all of it was packaged into an entity that could be bought silently. The security of a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/hardware-wallet/">hardware wallet</a> channel isn&apos;t cryptographic; it&apos;s corporate. This is the same lesson as the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/supply-chain-attack/">supply-chain attack</a> class we&apos;ve seen hit npm packages — trust artifacts (a badge, a publisher, a package name) get harvested instead of broken. For a transaction-by-transaction read of the theft addresses themselves, see our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-drain-address-poisoning/">companion tracing piece</a>.</p><h2 level="2" textAlign="left" id="h-what-to-watch">What to watch</h2><p>Three things will harden this from narrative into verdict: (1) Ledger&apos;s post-mortem confirming the implant mechanism and whether tampering maps to the March ownership change; (2) whether anyone establishes who Jiaming and the acquiring company are, and whether funds connect them to the drain addresses; (3) whether Binance freezes the accounts that received laundered flows. Until then, treat this as the confirmed parts — secret acquisition, device tampering, coordinated drain — plus the strong inference connecting them. We will update as findings land.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/ledger-cryptobilis-supply-chain-hack/"><em>https://theonchaindiary.com/articles/ledger-cryptobilis-supply-chain-hack/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/6d6269a89725fe0c1e25f6c11ee358c31acafa5dd7b0c4a60fbe03fa43d0ac83.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[FMMR Mining Scam: A Fake Pool Farmed 165 Wallets for 1.54M USDC — and the Permits Are Still Live Until 2030]]></title>
            <link>https://paragraph.com/@onchaindiary/fmmr-fake-mining-pool-scam</link>
            <guid>NmMT8MQIMEtcJeMdMibi</guid>
            <pubDate>Sun, 11 Oct 2026 07:49:18 GMT</pubDate>
            <description><![CDATA[An email that arrived because the scam stole our name In late September a victim in Zhejiang, China wrote to us. The way he found us says a lot about how these operations work: the fake app he had trusted called itself "Onchain." He searched the name and landed on this site. To be clear from the start — that app has no connection to Onchain Diary. The name was stolen. For the rest of this piece we'll use the operation's real storefront name: FMMR Mining, at fmmrvip.click. On October 11 he rep...]]></description>
            <content:encoded><![CDATA[<h2 level="2" textAlign="left" id="h-an-email-that-arrived-because-the-scam-stole-our-name">An email that arrived because the scam stole our name</h2><p>In late September a victim in Zhejiang, China wrote to us. The way he found us says a lot about how these operations work: the fake app he had trusted called itself &quot;Onchain.&quot; He searched the name and landed on this site. To be clear from the start — that app has no connection to Onchain Diary. The name was stolen. For the rest of this piece we&apos;ll use the operation&apos;s real storefront name: FMMR Mining, at <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://fmmrvip.click">fmmrvip.click</a>.</p><p>On October 11 he replied to our follow-up and gave us full permission to publish his story, writing that his goal was &quot;so more people know and fewer people get scammed.&quot; His QQ account, city, and Bilibili handles are withheld here; the on-chain data and timeline are published as-is. They are public records anyway.</p><h2 level="2" textAlign="left" id="h-what-happened-to-him">What happened to him</h2><p>It started in June, with a direct message on Bilibili from an account presenting as a woman doing medical-aesthetics work in Macau. Life chat first. Investment entered the conversation &quot;casually&quot; once trust built, then mining, then the obvious next step: you should join.</p><p>Act one was gentle. First deposit 300 USDC. Mining &quot;yields&quot; showed up, and — critically — a withdrawal actually cleared. For a lot of people the math checks out: risk 300 USDC to verify a channel that appears to pay. He scaled up.</p><p>Act two changed the script. One day the miner stopped and the on-chain balance was moved out. The platform&apos;s customer service said his IP was flagged and the funds were under regulatory review; releasing them required a 10,444 USDC &quot;verification fee.&quot; He recalls that 2,513 USDC of that fee was &quot;chipped in&quot; by the woman herself — remember this number, it becomes the sharpest piece of evidence in the whole case. Fee paid, the story changed: he was now suspected of money laundering, and needed to provide 14,560 USDC. Paid again, the story changed once more: multiple accounts detected, an 18,000 USDC deposit required. There he stopped, went to the police, and wrote to us.</p><p>His own post-mortem contains a line that deserves to be quoted to everyone who thinks they&apos;re too sharp for this. He knew from the start that cold DMs are almost always scams — he&apos;d even told friends he was chatting with her mainly to &quot;occupy her time so she&apos;d scam fewer people.&quot; He walked in with his guard up. He stayed because the app seemed to have F1 sponsorships (no partner named Onchain appears in the public <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://rtrsports.com/en/blog/every-teams-title-sponsor-for-the-2026-formula-1-season/">2026 F1 partner lists</a> — the crypto sponsors there are Crypto.com, Coinbase, and Gate); because the pool had four tiers and he was only on tier two, &quot;too early to pull the net&quot;; and because of one belief bigger than all the others: &quot;the money sits in my own wallet — she can&apos;t touch it.&quot;</p><p>That belief is what the rest of this investigation is about. They could touch it. Without asking him.</p><h2 level="2" textAlign="left" id="h-on-chain-autopsy-every-number-in-his-account-exists-on-ethereum">On-chain autopsy: every number in his account exists on Ethereum</h2><p>He sent us screenshots of two transfers — 10,680 USDC and 10,449 USDC. Both match mainnet records to the last digit. His wallet&apos;s full flow between August 28 and September 12, from Etherscan:</p><table class="paragraph-table"><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Time (UTC)</p></th><th colspan="1" rowspan="1"><p>Event</p></th><th colspan="1" rowspan="1"><p>Amount</p></th></tr><tr><td colspan="1" rowspan="1"><p>08-28 07:15</p></td><td colspan="1" rowspan="1"><p>Deposit (withdrawn from a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0xee7ae85f2fe2239e27d9c1e23fffe168d63b4055">Binance hot wallet</a>)</p></td><td colspan="1" rowspan="1"><p>6,999.40 USDC</p></td></tr><tr><td colspan="1" rowspan="1"><p>08-28 07:20</p></td><td colspan="1" rowspan="1"><p>Deposit (same rail)</p></td><td colspan="1" rowspan="1"><p>937.40 USDC</p></td></tr><tr><td colspan="1" rowspan="1"><p>08-28 08:00</p></td><td colspan="1" rowspan="1"><p>Transfer in from the &quot;friend&apos;s&quot; wallet</p></td><td colspan="1" rowspan="1"><p>2,513.00 USDC</p></td></tr><tr><td colspan="1" rowspan="1"><p>08-28 08:05</p></td><td colspan="1" rowspan="1"><p><strong>Drained</strong> (harvest #1)</p></td><td colspan="1" rowspan="1"><p>10,449 USDC</p></td></tr><tr><td colspan="1" rowspan="1"><p>09-11 11:26</p></td><td colspan="1" rowspan="1"><p>Deposit (Binance hot wallet withdrawal, &quot;verification fee&quot; round)</p></td><td colspan="1" rowspan="1"><p>10,679.43 USDC</p></td></tr><tr><td colspan="1" rowspan="1"><p>09-11 11:36</p></td><td colspan="1" rowspan="1"><p><strong>Drained</strong> (harvest #2 — ten minutes after deposit)</p></td><td colspan="1" rowspan="1"><p>10,680 USDC</p></td></tr><tr><td colspan="1" rowspan="1"><p>09-12 14:45</p></td><td colspan="1" rowspan="1"><p>Deposit</p></td><td colspan="1" rowspan="1"><p>3,835.59 USDC</p></td></tr><tr><td colspan="1" rowspan="1"><p>09-12 14:50</p></td><td colspan="1" rowspan="1"><p><strong>Drained</strong> (harvest #3)</p></td><td colspan="1" rowspan="1"><p>3,835 USDC</p></td></tr></tbody></table><p>The alignments are exact. Harvest #1 (10,449) corresponds to the &quot;verification fee&quot; of 10,444 in his telling. Harvests #2 and #3 sum to 14,515 (10,680 + 3,835), matching the &quot;money-laundering deposit&quot; of 14,560 he described. The 18,000 USDC final demand was never paid — which is why there is no fourth harvest on-chain. His customer-service arguments (&quot;is your platform even legitimate? you keep asking me for money&quot;) took place on September 14; the 26 pages of screenshots he compiled are full of that day&apos;s canned lines — &quot;multiple accounts failed system review,&quot; &quot;refund blocked by account errors&quot; — matching the on-chain rhythm beat for beat.</p><p>The funding rail&apos;s identity is nailed down too: all three of his large deposits were direct withdrawals from the same <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0xee7ae85f2fe2239e27d9c1e23fffe168d63b4055">Binance hot wallet</a>, a label confirmed independently by both Etherscan and BlockSec&apos;s AML database. The path is complete: buy USDC on Binance, withdraw to your own wallet, lose it to the pool&apos;s standing permit.</p><p>The executor is the harvester address <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0xfb6146EeeAF749243C370fF91506eb08A78Bf76C">0xfb6146...f76C</a>. No exploit, no flash loan, nothing exotic — just Ethereum&apos;s most ordinary mechanism, a signed <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/permit-sign-phishing/">USDC permit</a>. The &quot;terms&quot; he blind-signed at pool registration granted this address the right to spend his USDC: a 10-million-token cap, expiring January 12, 2030.</p><p>After that it ran like rent collection. Every time he topped up, they came and took the balance. Fastest cycle: deposit of 10,679.43 at 11:26, drained of 10,680 at 11:36. Even the gas for that drain had been forwarded to the harvester by the operation one minute earlier.</p><h2 level="2" textAlign="left" id="h-where-the-friends-2513-usdc-actually-came-from">Where the &quot;friend&apos;s&quot; 2,513 USDC actually came from</h2><p>This is the part of the case worth reading twice.</p><p>He told us 2,513 USDC of his verification fee &quot;was chipped in by her.&quot; On-chain: at 07:57 on August 28, the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0xe3a11fba8205ae79cfd91ab78af184d16042bbd0">persona wallet</a> received exactly 2,513.00 USDC — funded by the operation&apos;s own treasury. Three minutes later at 08:00, the same amount moved to his wallet. Five minutes after that, the harvester took the full 10,449, that 2,513 included.</p><p>The money she &quot;contributed&quot; had left the scam&apos;s treasury three minutes before it reached him. It made a perfect circle — treasury → her wallet → his wallet → collection address — returning to the same hands with eight thousand of his own USDC attached. Her wallet&apos;s broader history shows the same pattern: periodic treasury funding (1,000, 2,000, 2,513, 3,500), each batch forwarded within hours to a victim or looped back to the cash-out address. She wasn&apos;t a fellow miner. She was the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/pig-butchering-crypto-tracing/">pig-butchering</a> handler, running on house money.</p><p>This also answers the question victims&apos; families ask most: &quot;was the person chatting even aware?&quot; In this operation, at least, the hand that lent comfort and the hand that took the money were funded from the same treasury. There was no independent person behind the persona.</p><h2 level="2" textAlign="left" id="h-not-one-victim-165-wallets-154m-usdc">Not one victim: 165 wallets, 1.54M USDC</h2><p>Pull the full history of the collection address <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0xec31bb3d57d9c06de4c5db0d85a722f9224a5578">0xec31...5578</a> and the operation&apos;s true size appears: from June 1 to October 10, 2026, 537 incoming USDC transfers totaling 1,539,167 USDC from <strong>165 distinct addresses</strong>. Sixty-one of those addresses only ever sent 300–1,000 USDC — the same first-deposit threshold he paid. Forty-five sent 10K–50K. Four sent more than 50K. And the harvesting isn&apos;t done by one wallet: at least <strong>15 drainer addresses</strong> are confirmed running the same permit playbook, with over 100 transferFrom executions combined — our drainer&apos;s 11 are a rounding error.</p><figure float="none" class="paragraph-figure paragraph-figure-none"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/2b7db71859861c9e2f60f989271e1800ff0cfd75fe4c7610dff63fdd70db43a2.png" alt="FMMR fake mining pool fund flow and exit map" class="paragraph-editor-image"><figcaption>FMMR fake mining pool fund flow and exit map</figcaption></figure><p><em>The full fund-flow map: 165 victim wallets → 15+ drainers → collection pool (1.54M USDC) → treasury/mid-level → three exits. Every figure and address in the chart is verifiable on Etherscan.</em></p><p>The money moves up in a clean hierarchy: the collection address forwarded 805,000 USDC to a main treasury and split another three tranches (275,000, 205,820, 123,500) to mid-level wallets; the treasury concentrated roughly 912K USDC into an address labeled &quot;<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0x08ec0883dec73e786ccf01461e4e543e23a731a7">Bitget: Crosschain Bridge Vault</a>&quot; on Etherscan. Add the mid-level wallet&apos;s batched 180K, and <strong>roughly 1.09M USDC — more than half of everything stolen — exited through that exchange&apos;s cross-chain vault</strong>, a door that on-chain tracing alone cannot see past. The cash-out prep left traces too: in a single batch-settlement transaction on July 22, the treasury swapped 10,276.50 USDC into ~5.3 WETH through Uniswap V3&apos;s USDC/WETH pool; combined with other legs of the same transaction, ~7 WETH were routed via 1inch to an arbitrage-style wallet (tx <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/tx/0xd3dc8b4e92e7990d27c8a99c81de64192b5a3c4f32da8711112e172de2645537">0xd3dc...5537</a> verifiable on-chain). Stablecoins to ETH — standard pre-cash-out behavior. Below the exit address, the money takes two roads. One stays on-chain, split into dozens of small transfers to a dozen-plus network addresses that carry no label in any public database. The other takes a bridge — and not just once. On August 2, the treasury itself placed a 264,700 USDC order on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0xef4fb24ad0916217251f553c0596f8edc630eb66">deBridge&apos;s DlnSource contract</a> (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/tx/0xf7540f035536fc6ecc3e3b040f3873e7aebc166e17abd820362b70ded4ea8e56">tx verifiable on-chain</a>), destination <strong>Tron</strong>, payout in USDT — deBridge&apos;s order page shows a market maker unlocked it in 52 seconds, delivering 263,521.33 USDT on the Tron side. Four weeks later on August 30, a relay wallet fed another 206,208 USDC into the same bridge (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/tx/0xeda00cff45eef628e90d6133e3e394b13095587c55ce5b2b665513944b926f20">tx verifiable</a>). Those two orders alone moved 470K USDC off Ethereum — exactly where single-chain tracing goes dark. We decoded the Tron-side addresses embedded in the orders; one candidate landing wallet is confirmed receiving 162,058.48 USDT on October 3. Yields, harvest, consolidation, cross-chain exit — four functions, four wallet layers, an assembly line.</p><p>The pass-through discipline deserves a line too: seven minutes before that August 2 bridge order, the treasury had just received 265K USDC in via an ERC-4337 handleOps call — collect, forward, hold nothing. Two more fingerprints were impossible before the Pectra upgrade (May 2025). First, the persona wallet still carries an EIP-7702 delegation hooking its execution logic to a smart-wallet proxy (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0x490aac77c960b0569c8e446ac7e12490bd44ca1d">delegate verifiable on-chain</a>, labeled as Bitget Wallet&apos;s 7702 logic) — off-the-shelf commercial wallet infrastructure, not custom tooling. Second, and sneakier: the treasury reads as a clean, plain EOA today — yet in that July 22 batch settlement, an operator address invoked it with a batch method and moved its funds. A plain address cannot be &quot;called&quot; into executing anything unless it carried a 7702 delegation at the time. They attach the delegation when operating and strip it afterwards — easy to miss in forensics. An operation with account-abstraction tooling and the discipline to clean up after itself is not three people clicking manually.</p><p>The domain tells its own story. fmmrvip.click was registered July 28, 2026 (NameSilo, behind Cloudflare). The harvester&apos;s first drain came the next day, July 29 — the collection address had been receiving funds since June 1, and the operation&apos;s gas supplier was activated as early as March 30 — seeded from a hot wallet of FixedFloat, a no-KYC instant exchanger — sending over 700 gas transfers since, four months before this domain existed and anonymous from day one. Domains are consumables in this business, swapped out as they burn; the crew is permanent. In his latest email, the persona is already pitching him a &quot;new pool.&quot;</p><p>As of publication, fmmrvip.click is still serving its login page, titled &quot;FMMR Mining,&quot; and the collection address still holds roughly 130K USDC not yet moved.</p><h2 level="2" textAlign="left" id="h-the-money-sits-in-my-wallet-the-belief-this-industry-runs-on">&quot;The money sits in my wallet&quot; — the belief this industry runs on</h2><p>Return to the sentence he used to reassure himself, because it is the entire technical core of this crime class.</p><p>Wallet signatures come in two flavors. One moves funds directly — everyone watches those. The other grants allowances (an approve, or a permit signature): after signing, nothing visibly happens. The balance doesn&apos;t move. No alarm sounds. But the right to spend those tokens now belongs to someone else, who can act alone, later, at any moment. In this operation, every victim signed the same template: a 10-million-USDC cap on USDC, expiring January 12, 2030.</p><p>As of publication, of the seven permits we reviewed, <strong>not one has been revoked</strong>. Those wallets are pre-mined ground: the moment their owners deposit again, the harvest arrives within minutes. The fix is mechanical — revoke allowances via revoke.cash, or abandon the address (allowances die with the address&apos;s relevance). Teaching him this was the first thing we did in our reply.</p><h2 level="2" textAlign="left" id="h-four-things-you-can-do">Four things you can do</h2><ol><li><p><strong>Audit</strong>: connect at revoke.cash and review every live allowance. Anything signed for mining, quant, or &quot;activation&quot; services gets revoked. Built-in approval managers in major wallet apps do the same.</p></li><li><p><strong>Retire</strong>: a wallet carrying a large live allowance should never hold funds again. Empty it and stop using it.</p></li><li><p><strong>Recognize</strong>: four signals together are conclusive — a stranger steering friendship into investing, a small first deposit that genuinely withdraws, pressure to scale, and a wallet signature demanded during onboarding. The first three fatten the pig. The fourth is the knife.</p></li><li><p><strong>Report</strong>: if it happens, go to the police immediately with chats, handles, and transaction hashes. USDC is centrally issued by Circle, which can freeze addresses once law enforcement engages — a real avenue, but proceeds get fragmented through DEXes within days, so speed matters. Our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/stolen-crypto-first-24-hours/">first-24-hours checklist</a> walks the sequence.</p></li></ol><p>His case belongs to the same family as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/infinite-approval-explained/">infinite approvals</a> and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-spot-wallet-drainers/">signature scams</a>: the last line of defense in self-custody isn&apos;t your password or your hardware. It&apos;s the second before you sign something you haven&apos;t read. If you can&apos;t parse a signature request, don&apos;t sign it.</p><p><em>This article is on-chain safety education, not investment advice. The victim&apos;s account is published with his explicit permission and anonymized; all on-chain data comes from public Ethereum mainnet records, with key addresses linked to Etherscan for independent verification.</em></p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/fmmr-fake-mining-pool-scam/"><em>https://theonchaindiary.com/articles/fmmr-fake-mining-pool-scam/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/c27101c0100eb90282a5e52e1bc5565ecbaa5c1c713ab0a383a928623f3eff47.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Fake Crypto Support Scams Explained: Why Support That Contacts You First Is Always Fake]]></title>
            <link>https://paragraph.com/@onchaindiary/fake-customer-support-scams</link>
            <guid>GND3dXeqLaEukV9xmgDH</guid>
            <pubDate>Sun, 11 Oct 2026 07:49:10 GMT</pubDate>
            <description><![CDATA[The most expensive message in crypto is not a phishing link. It is a helpful stranger who arrives before you ask for help. You post a question in a project's Discord. Ninety seconds later, someone with an official-looking username DMs you: "Hi, I'm from the support team, I saw your issue in the channel. Let's resolve this privately." Or your phone rings, and the caller says they are from your exchange's security department, and there is suspicious activity on your account that must be address...]]></description>
            <content:encoded><![CDATA[<p>The most expensive message in crypto is not a phishing link. It is a helpful stranger who arrives before you ask for help.</p><p>You post a question in a project&apos;s Discord. Ninety seconds later, someone with an official-looking username DMs you: <em>&quot;Hi, I&apos;m from the support team, I saw your issue in the channel. Let&apos;s resolve this privately.&quot;</em> Or your phone rings, and the caller says they are from your exchange&apos;s security department, and there is suspicious activity on your account that must be addressed right now.</p><p>Both are the opening move of the same play. The FBI&apos;s Internet Crime Complaint Center documented it in an <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ic3.gov/PSA/2024/PSA240801">August 2024 alert</a> on scammers impersonating cryptocurrency exchange employees: the contact is unsolicited, the tone is urgent, the story is an account problem or an attempted compromise, and the fix always ends with you handing something over — login information, a clicked link, identity documents, or access to your device.</p><p>This guide breaks the scam into its working parts: how the funnel finds you, the three endings it is built to reach, what the aftermath looks like on-chain, and the one rule that makes the whole structure collapse.</p><h2 level="2" textAlign="left" id="h-the-one-rule">The One Rule</h2><p><strong>Real support never contacts you first.</strong></p><p>Not by phone. Not by DM. Not by email about an account you didn&apos;t write in about. Support in crypto is reactive: you open a ticket through the official help center, and the conversation happens there, or through email from the company&apos;s official domain about the ticket you opened.</p><p>This is not a custom or a best practice. It is a published invariant, and you can verify it on the support pages of the largest wallet in the industry. MetaMask&apos;s <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://support.metamask.io/start/how-to-contact-metamask-support">&quot;How to contact MetaMask Support&quot;</a> page states it in three consecutive sentences: support &quot;will never reach out to you first by direct message or email,&quot; MetaMask &quot;does not have a phone number,&quot; and it &quot;will never ask you for your Secret Recovery Phrase.&quot; The company&apos;s <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://support.metamask.io/stay-safe/safety-in-web3/what-are-metamasks-official-support-channels/">official channels page</a> adds the corollary: emails about open tickets come only from the support domain, and anyone asking for your secret recovery phrase is running a scam, full stop.</p><p>Almost every serious exchange and protocol publishes some version of the same rule. The details differ; the invariant doesn&apos;t. So when someone contacts you first, the question &quot;is this real?&quot; has already been answered by the fact of the contact itself.</p><h2 level="2" textAlign="left" id="h-how-the-funnel-finds-you">How the Funnel Finds You</h2><p>The scam is engineered around timing, and the timing is not accidental.</p><p><strong>The support-channel ambush.</strong> You have a problem — a stuck withdrawal, an airdrop claim that errors out, a sync issue — and you do what people do: you post about it in the project&apos;s public Discord or Telegram channel, or you reply to the project on X. Attackers watch these channels continuously, and the response is fast because it has to be: a &quot;support agent&quot; DMs you within minutes, often before real community members answer. The username matches the project&apos;s naming style. The avatar looks right. The message references your actual problem, sometimes quoting it back to you.</p><p>Everything after that moves you out of public view. <em>&quot;Let&apos;s continue in private so we can verify your identity.&quot;</em> Public channels are hostile terrain for the scam — real moderators and community members can interrupt. A DM is a clean room.</p><p><strong>The inbound call.</strong> The second variant needs no trigger from you. Your number is on a leaked or scraped list — a data broker dump, an old exchange KYC breach, a signup form from years ago — and the caller claims to be from your exchange&apos;s security or compliance team. The FBI&apos;s alert describes the script: there is a problem with your account, or someone is trying to compromise it <em>right now</em>, and you need to act immediately to protect your funds. Caller ID is not evidence. Numbers can be spoofed to display the exchange&apos;s real support line, which is why the FBI&apos;s first piece of advice is to hang up and call back using only the number listed on the official website — never a number the caller provides.</p><p><strong>The search-engine trap.</strong> The third entry point is the result page itself. You search for your wallet&apos;s or exchange&apos;s support contact, and the top result is an ad for a lookalike support site — the same logo, the same layout, a phone number that reaches a professional-sounding &quot;agent.&quot; The tell here is structural: a company like MetaMask has no phone number to find. If the contact you found is a phone line, it is not the wallet maker&apos;s support, no matter how well the site is built.</p><p>What all three variants share is the inversion: they come to you. Once you internalize that real support only ever answers, never initiates, every one of these openings reads as what it is.</p><h2 level="2" textAlign="left" id="h-the-three-endings">The Three Endings</h2><p>The funnel is flexible about the story but rigid about the destination. Every fake support conversation is built to end in one of three places, and knowing them in advance is usually enough to break the spell mid-conversation.</p><h3 level="3" textAlign="left" id="h-ending-1-the-phishing-page">Ending 1: The phishing page</h3><p>The &quot;agent&quot; needs to &quot;verify your account.&quot; You are sent to a support portal or wallet-verification page — a site that mirrors the real one down to the favicon. The page asks for the thing it was built to collect: exchange login credentials and a 2FA code, or, on the wallet side, your <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/seed-phrase/">seed phrase</a> entered into a twelve- or twenty-four-box form &quot;to confirm ownership.&quot;</p><p>There is no version of this that is real. No exchange asks for your password over a support chat, and no wallet maker has ever needed your seed phrase for anything — support can read your public address, which is all a diagnosis ever requires. A seed phrase entered into a web form is a wallet drained within minutes, usually from an automated <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/wallet-drainer/">wallet drainer</a> that has the sweep transaction queued before you finish clicking submit.</p><h3 level="3" textAlign="left" id="h-ending-2-the-verification-signature">Ending 2: The verification signature</h3><p>This one is subtler, and it catches people who &quot;would never share their seed phrase&quot; — because they never do.</p><p>Your wallet needs to be &quot;synchronized&quot; with the new security system, or your identity needs to be &quot;verified on-chain,&quot; or your stuck transaction needs to be &quot;released.&quot; The fix is a signature request pushed to your wallet. The message is rendered as hexadecimal garbage, or the request UI says you are signing something harmless, and the agent stays on the line, calmly telling you this is routine.</p><p>It is one of two attacks wearing the same coat:</p><ul><li><p><strong>A token approval.</strong> You are not verifying anything — you are authorizing a contract to spend a specific token, or an unlimited amount of it. This is the mechanics behind <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/infinite-approval-explained/">infinite approvals</a>, and the drainer waits until you have refilled the wallet or the gas price is cheap.</p></li><li><p><strong>A raw eth_sign message.</strong> On wallets and accounts that still allow it, signing raw arbitrary data can produce a signature that moves funds. This is the classic <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/eth-sign-phishing-explained/">eth_sign phishing</a> pattern, and it is the reason hardware wallets push you to read exactly what you are signing on the device screen.</p></li></ul><p>The rule that cuts through every variant: <strong>no support process in crypto requires a signature.</strong> Reading your public address is free and needs nothing from you. Anything else is extraction.</p><h3 level="3" textAlign="left" id="h-ending-3-the-remote-session">Ending 3: The remote session</h3><p>The &quot;technician&quot; cannot diagnose the problem remotely — they need you to install a remote-access tool or a screen-sharing app &quot;so engineering can see what&apos;s happening.&quot; Once the session is live, the ending depends on the operator&apos;s patience.</p><p>The fast version is a smash-and-grab: watch your screen until you unlock your wallet, then act in the seconds it stays unlocked, or read credentials and 2FA codes directly off your display as you type them into the &quot;support portal.&quot; The slow version is worse — the remote tool is a delivery mechanism for an <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/infostealer-malware-crypto-attacks/">infostealer</a>, which harvests browser passwords, session cookies, and wallet extension vaults, then phones home. You close the &quot;resolved&quot; ticket feeling helped; the extraction happens days later from a device you still trust.</p><p>There is no diagnostic in the world that requires a stranger to control your device. That is not support. That is handing over the keys and watching politely.</p><h2 level="2" textAlign="left" id="h-what-the-aftermath-looks-like-on-chain">What the Aftermath Looks Like On-Chain</h2><p>If the ending already happened, the transaction history tells you which one it was — and that determines your next move.</p><p>A seed-phrase compromise is the cleanest signature: everything with value leaves in one burst, including the ETH or gas token itself, because the attacker controls the keys outright. A malicious approval is the opposite: your ETH balance sits untouched, gas is spent only by the attacker&apos;s own transactions, and specific tokens disappear in transactions you can find in your history — signed by you, at a moment the &quot;agent&quot; was walking you through &quot;verification.&quot; Paste your address into any approval-revocation tool and the grant is sitting there, explicit, with a date and time.</p><p>Either way, the funds route through a chain of fresh addresses toward an exchange deposit or a mixer. That trail is what investigators work with, and it is why the first hours matter: exchange-side freezes are possible only while the funds are still sitting at a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/kyc/">KYC&apos;d</a> off-ramp. The full playbook — what to preserve, how to revoke approvals, where to file, what a freeze request contains — is in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/stolen-crypto-first-24-hours/">what to do in the first 24 hours after a theft</a>, and the reporting mechanics are in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-report-crypto-scam/">how to report a crypto scam</a>. Tools that read <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/wallet-labels/">wallet labels</a> can tell you whether the receiving cluster is already tagged as a drainer cash-out — useful both for triage and for your report.</p><h2 level="2" textAlign="left" id="h-the-verification-protocol">The Verification Protocol</h2><p>When you genuinely need support, the safe path takes thirty seconds longer and cannot be hijacked:</p><ol><li><p><strong>Close the conversation.</strong> Do not &quot;just ask one more question.&quot; Every additional message is attack surface.</p></li><li><p><strong>Navigate to the official site yourself.</strong> Type the domain or use your own bookmark. Do not use any link, phone number, or email address the &quot;agent&quot; provided — this is the FBI&apos;s explicit guidance in its exchange-impersonation alert.</p></li><li><p><strong>Use the help center inside the product.</strong> Exchanges put support inside the logged-in app or website; wallet makers publish a single support domain. If you have a ticket, replies come through that channel only.</p></li><li><p><strong>In Discord, verify roles in public.</strong> Real staff are visible in the server&apos;s member list with a role badge, and they answer where others can see. A &quot;moderator&quot; who exists only in your DMs has no verifiable existence.</p></li></ol><p>And the four asks that end any doubt, because each one is an automatic fail: a password or login, a seed phrase or private key, a 2FA code, or remote access to your device. No real support interaction in the history of crypto has required any of the four.</p><h2 level="2" textAlign="left" id="h-round-two-the-recovery-follow-up">Round Two: The Recovery Follow-Up</h2><p>The fake support scam has a sequel, and it opens on the same wound. Days after the loss, someone messages you: they are from a &quot;blockchain analytics firm&quot; or a &quot;recovery team,&quot; they have already located your funds, and for a fee — or an upfront &quot;gas deposit&quot; — they can get them back.</p><p>The FBI flags this follow-on explicitly in the same alert, pointing to its separate advisory on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ic3.gov/PSA/2023/PSA230811">fake recovery services</a>. The structure is always the same: an upfront payment, a stretch of &quot;processing,&quot; then a bigger payment to &quot;release the funds,&quot; until the victim stops paying. The scam works because the target list is already built — you are known to have lost money and to be desperate.</p><p>We cover the full anatomy, including the free channels that actually exist (exchange freeze requests, law enforcement referral, court-ordered forfeiture) in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-recovery-scams-explained/">crypto recovery scams explained</a>. The short version of that page applies here with full force: anyone who contacts you first promising recovery is running the second half of the scam that just hit you.</p><h2 level="2" textAlign="left" id="h-why-it-keeps-working">Why It Keeps Working</h2><p>Every surface the scam borrows is a surface you have been trained to trust, and none of it is authenticated.</p><p>Caller ID was built to display who owns a line, not to prove who is speaking, and spoofing it is trivial. A Discord username and avatar cost nothing to copy and take seconds to register. A support website can mirror a real one for the price of a lookalike domain. The &quot;agent&quot; will often have your real name, your real account details, and the real problem you posted minutes ago — not because they work at the exchange, but because breaches and public channels have already published the raw material. Each borrowed detail feels like proof, and none of it is.</p><p>The second ingredient is time pressure. &quot;Someone is trying to access your account right now&quot; is engineered to make verification feel like the risky option — as if the two minutes it takes to hang up and open the official site is the window in which the imaginary attacker wins. It inverts the actual risk math: the only scenario in which you lose money in those two minutes is the one where you stay on the line.</p><p>The third is that the scam arrives attached to a real problem. Most victims were not idle targets; they had a genuine stuck withdrawal or a failed claim and went looking for help. The scam does not need to invent a pretext — it intercepts an existing one, which is why the ambush variant centers on public support channels. That interception is also its weakness: the timing is too good. Real support does not answer a Discord post in ninety seconds. An impossibly fast, impossibly helpful responder is the scam announcing itself.</p><h2 level="2" textAlign="left" id="h-related-reading">Related Reading</h2><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/airdrop-snapshot-verification-scams/">Stuck funds, fake claims, verification traps: how airdrop scams set you up for fake support</a> — the airdrop cycle generates exactly the &quot;claim errors&quot; that fake agents offer to fix</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/social-media-crypto-scam-playbook/">The full social engineering playbook across X, Telegram, and email</a> — fake support is one channel tactic among several</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-detect-nft-wash-trading/">How to spot wash trading before you trust a market&apos;s volume</a> — fake volume and fake support are different products from the same supply chain</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/after-wallet-drainer-what-now/">After a drainer: what to do once the signature is already signed</a> — the post-incident guide for ending 2</p></li></ul><p>Fake support survives on a single asymmetry: the scammer knows the script and you don&apos;t. The script always opens the same way — they find you, before you find them. Now you know what that means.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/fake-customer-support-scams/"><em>https://theonchaindiary.com/articles/fake-customer-support-scams/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/2b5698542765cdfe0a668ee007595e299478df6519c48dfa2ec05ac3503aceb6.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Fake Crypto Job Offers Explained: The $1.5B Hack That Started With One Recruiter Message]]></title>
            <link>https://paragraph.com/@onchaindiary/fake-crypto-job-offer-scams</link>
            <guid>KHDWuzwXDSlzH3WQbgOI</guid>
            <pubDate>Sun, 11 Oct 2026 07:49:04 GMT</pubDate>
            <description><![CDATA[The largest crypto theft ever recorded did not start with a smart contract bug, a leaked private key, or a phishing site. It started with a job interview. On February 21, 2025, roughly $1.5 billion in ether left Bybit's cold wallet after three signers approved what looked like a routine withdrawal. The FBI officially attributed the theft to North Korean state actors. But the part of the story that matters for anyone working in crypto came out in the post-mortems: the attackers had compromised...]]></description>
            <content:encoded><![CDATA[<p>The largest crypto theft ever recorded did not start with a smart contract bug, a leaked private key, or a phishing site. It started with a job interview.</p><p>On February 21, 2025, roughly <strong>$1.5 billion in ether left Bybit&apos;s cold wallet</strong> after three signers approved what looked like a routine withdrawal. The <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.fbi.gov/investigate/cyber/alerts/2025/north-korea-responsible-for-1-5-billion-bybit-hack">FBI officially attributed the theft to North Korean state actors</a>. But the part of the story that matters for anyone working in crypto came out in the post-mortems: the attackers had <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.sygnia.co/blog/sygnia-investigation-bybit-hack">compromised a DevOps engineer at Safe {Wallet} months earlier through a fake job offer</a>, and quietly waited.</p><p>If you work in crypto — as a developer, an ops person, a designer, or even a part-time community moderator — the hiring pipeline aimed at you is also an attack pipeline. This article breaks down exactly how these campaigns work, what the file-based lures look like, and how to tell a real recruiter from a weaponized one.</p><h2 level="2" textAlign="left" id="h-the-attack-chain-step-by-step">The attack chain, step by step</h2><p>The Bybit incident is the best-documented example, investigated by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.sygnia.co/blog/sygnia-investigation-bybit-hack">Sygnia</a> with technical analysis from <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.nccgroup.com/research/in-depth-technical-analysis-of-the-bybit-hack">NCC Group</a>. The chain looks like this:</p><ol><li><p><strong>Contact.</strong> A recruiter profile on LinkedIn or another platform messages a target employee of a crypto infrastructure company. The profile is polished, the role is plausible — senior, remote, well paid.</p></li><li><p><strong>The lure file.</strong> The conversation moves to a &quot;job description,&quot; a resume template, or a take-home exercise. The file is weaponized. When opened on the engineer&apos;s Mac, it installed an infostealer.</p></li><li><p><strong>Credential theft.</strong> The infostealer harvested credentials and session tokens, including access to the company&apos;s cloud infrastructure.</p></li><li><p><strong>Dormancy.</strong> The attackers then waited. Bybit&apos;s post-mortem timeline shows the initial compromise happened long before the theft — the intrusion wasn&apos;t detected during the waiting period.</p></li><li><p><strong>Interface tampering.</strong> Using the stolen access, the attackers modified the JavaScript served by the wallet interface that Bybit&apos;s signers trusted. The multisig UI showed one address; the actual transaction data contained another.</p></li><li><p><strong>The blind spot.</strong> Three authorized signers saw a clean-looking screen and signed. The transaction redirected ~$1.5 billion to attacker-controlled addresses.</p></li></ol><p>Notice what&apos;s missing: no zero-day in the smart contract, no brute-forced key. Every technical control held. The attack worked because a human being wanted a better job.</p><p>This is why investigators classify these incidents as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/supply-chain-attack/">supply chain attacks</a> rather than simple <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/phishing-attack/">phishing</a> — the target wasn&apos;t the engineer&apos;s personal funds, but the infrastructure he could reach.</p><h2 level="2" textAlign="left" id="h-the-coding-test-variant-ginco">The coding-test variant: Ginco</h2><p>The Bybit case isn&apos;t isolated. In March 2024, according to a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.wiz.io/blog/north-korean-tradertraitor-crypto-heist">deep dive by Wiz on the TraderTraitor cluster</a>, an operative posing as a recruiter lured a developer at the Japanese crypto company Ginco into running a malicious Python script disguised as a take-home coding test.</p><p>The mechanics are brutal in their simplicity: the interview process itself becomes the infection vector. A developer who would never open a random attachment from a stranger will happily clone a repository and run a script when it&apos;s framed as &quot;complete this task so we can evaluate your code.&quot; The script runs with the developer&apos;s own permissions, on a machine that often holds SSH keys, wallet files, and exchange sessions.</p><p>Two details make this variant especially effective:</p><ul><li><p><strong>It selects for skilled targets.</strong> Only working developers get to the coding-test stage, so the attacker&apos;s malware lands on machines belonging to exactly the people with valuable access.</p></li><li><p><strong>It provides natural cover for follow-up questions.</strong> &quot;Did the test run okay for you?&quot; is a legitimate-sounding reason to keep the conversation going while the payload does its work.</p></li></ul><h2 level="2" textAlign="left" id="h-scale-this-is-an-industry-not-a-hobby">Scale: this is an industry, not a hobby</h2><p>The fake-recruiter playbook sits inside a much larger North Korean revenue operation. Chainalysis <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.chainalysis.com/blog/crypto-hacking-stolen-funds-2025/">counted $1.34 billion stolen by North Korea-linked groups in 2024 across 47 incidents</a> — roughly 61% of all funds stolen from crypto services that year, up from $660.5 million across 20 incidents in 2023. Their <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.chainalysis.com/blog/2025-crypto-crime-mid-year-update/">mid-year 2025 update</a> recorded over $2.17 billion stolen in the first half of 2025 alone, with Bybit the single largest event.</p><p>The staffing side of the operation is equally industrial. In June 2025, the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.justice.gov/archives/opa/pr/fourteen-north-korean-nationals-indicted-carrying-out-multi-year-fraudulent-information">US Department of Justice unsealed charges against fourteen North Korean nationals</a> for a multi-year scheme placing fraudulent remote IT workers inside US companies; <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.reuters.com/legal/government/doj-announces-arrest-indictments-north-korean-it-worker-scheme-2025-06-30">Reuters reported</a> the workers used identities of more than 80 US citizens to obtain jobs at more than 100 companies. In August 2025, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.justice.gov/opa/pr/two-us-nationals-sentenced-facilitating-fraudulent-remote-information-technology-worker">two US nationals were sentenced for operating &quot;laptop farms&quot;</a> — relay hardware that made overseas operators appear to log in from US addresses, generating millions in illicit salary revenue.</p><p>The same workforce that fills fake remote jobs also staffs the recruiter personas. When a &quot;senior talent partner&quot; messages you about a protocol role, there is no way to know from the profile whether you&apos;re talking to a real person, a North Korean operative, or both.</p><h2 level="2" textAlign="left" id="h-the-consumer-variant-fake-web3-gigs-and-test-our-dapp">The consumer variant: fake Web3 gigs and &quot;test our dapp&quot;</h2><p>Most readers won&apos;t be DevOps engineers at wallet infrastructure companies. But the same psychology scales down to part-time gigs, and Chinese- and English-speaking job groups on Telegram are full of it:</p><ul><li><p><strong>&quot;Test our dapp, we pay in USDT.&quot;</strong> You&apos;re asked to connect your wallet to an unfamiliar frontend and complete an interaction. The interaction is a malicious <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/permit-sign-phishing/">signature request</a> or a token approval. Nothing looks wrong because the scam <em>is</em> the job.</p></li><li><p><strong>&quot;Fill out this onboarding form.&quot;</strong> The form is a cloned Google-login page harvesting credentials, or the &quot;HR document&quot; is a macro-laced spreadsheet.</p></li><li><p><strong>&quot;We pay your salary in our token — here&apos;s your allocation, claim it here.&quot;</strong> The claim site asks for your seed phrase or an unlimited approval.</p></li></ul><p>The tell in all three: legitimate employers screen you; they don&apos;t need your wallet. The moment a job application requires connecting a wallet, approving a token transfer, or entering a seed phrase, it is not a job application. It&apos;s wallet drainer infrastructure wearing a hiring banner — the same playbook covered in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-spot-wallet-drainers/">how to spot wallet drainers</a>, aimed at people whose guard is down because they&apos;re in &quot;work mode.&quot;</p><h2 level="2" textAlign="left" id="h-red-flags-how-to-screen-the-screener">Red flags: how to screen the screener</h2><table class="paragraph-table"><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Signal</p></th><th colspan="1" rowspan="1"><p>Real process</p></th><th colspan="1" rowspan="1"><p>Weaponized process</p></th></tr><tr><td colspan="1" rowspan="1"><p>First contact</p></td><td colspan="1" rowspan="1"><p>Recruiter&apos;s email matches the company domain</p></td><td colspan="1" rowspan="1"><p>Personal Gmail, or a lookalike domain registered recently</p></td></tr><tr><td colspan="1" rowspan="1"><p>Materials</p></td><td colspan="1" rowspan="1"><p>Links to a public careers page</p></td><td colspan="1" rowspan="1"><p>Attachments: &quot;JD.pdf&quot;, resume templates, coding-test archives</p></td></tr><tr><td colspan="1" rowspan="1"><p>Interview</p></td><td colspan="1" rowspan="1"><p>Video call with verifiable employees</p></td><td colspan="1" rowspan="1"><p>Text-only chat; camera &quot;broken&quot;; urgency to skip calls</p></td></tr><tr><td colspan="1" rowspan="1"><p>Compensation</p></td><td colspan="1" rowspan="1"><p>Discussed after mutual interest</p></td><td colspan="1" rowspan="1"><p>Salary quoted in the first message, unusually high</p></td></tr><tr><td colspan="1" rowspan="1"><p>The task</p></td><td colspan="1" rowspan="1"><p>Sanity interview questions</p></td><td colspan="1" rowspan="1"><p>Run this script / connect this wallet / share your screen</p></td></tr><tr><td colspan="1" rowspan="1"><p>Domain age</p></td><td colspan="1" rowspan="1"><p>Company site years old</p></td><td colspan="1" rowspan="1"><p>&quot;Careers&quot; domain registered weeks ago</p></td></tr></tbody></table><p>None of these signals is conclusive alone. Together, they form a filter that catches nearly every fake-recruiter approach documented in public incidents.</p><p>Practical rules that survive contact with real campaigns:</p><ol><li><p><strong>Never open unsolicited job files on a machine that touches crypto.</strong> Keep a separate, cheap device for job hunting — the same isolation logic as a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/hardware-wallet/">hardware wallet</a>, applied to your career.</p></li><li><p><strong>Verify the recruiter out-of-band.</strong> Find the company&apos;s careers page yourself, and message the official HR contact listed there to confirm the person exists.</p></li><li><p><strong>Treat &quot;run this locally&quot; as a security decision, not a hiring step.</strong> A real take-home test can run in a browser sandbox or a fresh VM. Ask to use one; a legitimate employer won&apos;t care.</p></li><li><p><strong>Assume dormancy.</strong> The Bybit compromise sat quiet for months. If you fell for one of these last year and &quot;nothing happened,&quot; that is not evidence you were safe — it&apos;s the normal shape of these operations. Rotate credentials anyway.</p></li><li><p><strong>Report the profile.</strong> Every platform where the persona operates will take recruiter-impersonation reports. It won&apos;t stop the campaign, but it shortens the life of that particular persona.</p></li></ol><h2 level="2" textAlign="left" id="h-if-youre-hiring-the-mirror-image-problem">If you&apos;re hiring: the mirror-image problem</h2><p>The DOJ&apos;s laptop-farm cases mean the threat runs in both directions — the &quot;employee&quot; can be the attack. For crypto companies, the standard countermeasures after Bybit have hardened around a few points: dedicated, network-isolated machines for transaction signing (so a compromised laptop elsewhere can&apos;t reach the signing flow), mandatory verification of transaction data <em>independent of the rendered UI</em>, and social-engineering drills that specifically rehearse recruiter approaches, not just password phishing.</p><p>For individuals, the summary is one line: in this industry, an unsolicited opportunity is a security event until proven otherwise. Proving it otherwise takes minutes. Skipping the check is how a $1.5 billion theft began.</p><h2 level="2" textAlign="left" id="h-related-reading">Related reading</h2><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/npm-supply-chain-attacks-2026/">How state-backed malware turned npm packages into attack vectors</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/infostealer-malware-crypto-attacks/">Infostealer malware and crypto: what gets stolen first</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/blind-signing-explained/">Blind signing explained: why your screen can lie to you</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/bitget-hot-wallet-hack-explained/">The Bitget incident: when no private key was stolen at all</a></p></li></ul><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/fake-crypto-job-offer-scams/"><em>https://theonchaindiary.com/articles/fake-crypto-job-offer-scams/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/4fb822714772b3dd7327b0309cc7692a2f632ddce69003bc3a4eff757b3bf61d.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Crypto Task Scams Explained: How Easy-Money Jobs Turn Your Wallet Into a Money Mule]]></title>
            <link>https://paragraph.com/@onchaindiary/crypto-task-scam-money-mule</link>
            <guid>eky3lYMyjNDghwjs6FTn</guid>
            <pubDate>Sun, 11 Oct 2026 07:48:57 GMT</pubDate>
            <description><![CDATA[The job pays you first. That single detail is why task scams work, and it is the part people get backwards. When a stranger's Telegram group pays you $8 for liking three YouTube videos, the money is real, it arrives, and it is withdrawable. Nothing about that transaction is a scam yet. It is a marketing expense — the cheapest customer acquisition the fraud industry has ever built, because the next deposit is yours. The FBI's Internet Crime Complaint Center put a name on this in its 2024 annua...]]></description>
            <content:encoded><![CDATA[<p>The job pays you first.</p><p>That single detail is why task scams work, and it is the part people get backwards. When a stranger&apos;s Telegram group pays you $8 for liking three YouTube videos, the money is real, it arrives, and it is withdrawable. Nothing about that transaction is a scam yet. It is a marketing expense — the cheapest customer acquisition the fraud industry has ever built, because the next deposit is yours.</p><p>The FBI&apos;s Internet Crime Complaint Center put a name on this in its <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ic3.gov/AnnualReport/Reports/2024_IC3Report.pdf">2024 annual report</a>: &quot;task scamming,&quot; listed among the year&apos;s emerging schemes. The lifecycle it describes is consistent. Recruitment arrives by text or messaging-app group. The first tasks are trivially easy — rating restaurants, liking videos, boosting product listings — and pay small commissions that genuinely land. Then the funnel turns: the work moves to the operation&apos;s own crypto platform, &quot;boosted tasks&quot; multiply the promised return but require a deposit, and sooner or later a withdrawal is blocked over an &quot;error,&quot; a &quot;tax,&quot; or a &quot;data mismatch&quot; that only a further payment can fix.</p><p>This guide covers both halves of the machine. The first half takes deposits. The second half — less famous, more dangerous — offers the &quot;worker&quot; a promotion: a role receiving and forwarding other people&apos;s money. That is where a task scam victim becomes part of the laundering infrastructure, sometimes without ever losing a cent on tasks.</p><h2 level="2" textAlign="left" id="h-the-first-half-the-deposit-funnel">The First Half: The Deposit Funnel</h2><p><strong>Recruitment.</strong> The invite is casual and unsolicited: a WhatsApp or Telegram group about &quot;part-time earnings,&quot; often added after a wrong-number friendship message or a job-board reply. The group is alive — members post earnings screenshots, thank the &quot;teacher,&quot; celebrate payouts. Most of those members are operators running multiple accounts, and the screenshots cost nothing to fabricate.</p><p><strong>The easy stage.</strong> Tasks are real work in the trivial sense: like this video, rate this restaurant five stars, follow this account. Payouts are small and they arrive. This stage exists to produce one specific belief: <em>this platform pays</em>. Every later stage is priced against that belief.</p><p><strong>The escalation.</strong> Basic tasks &quot;sell out.&quot; The platform introduces boosted tasks with multiples of the return — available only after a deposit, on the platform&apos;s own crypto site, where you connect a wallet and fund a balance. You are now depositing your own money to keep doing a job. From the operator&apos;s side, the economics are shaped like every <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/exit-scam/">exit scam</a> before it: your deposit funds the payouts that keep the group&apos;s belief alive, and the operator&apos;s ledger never has to balance because withdrawals have a kill switch.</p><p><strong>The freeze.</strong> A withdrawal request fails. Customer service — responsive for the first time in days — explains the error: your account was flagged, the task sequence was entered incorrectly, a tax must be settled, a margin deposit is required. Every variant ends the same way: pay to unlock. Victims who pay discover a new reason for the next lock. This is not a bug in the platform. It <em>is</em> the platform.</p><p>The deposit half of the funnel is brutal, but it has a ceiling: you can only lose what you deposit. The second half is where the ceiling comes off.</p><h2 level="2" textAlign="left" id="h-the-second-half-your-account-becomes-the-pipe">The Second Half: Your Account Becomes the Pipe</h2><p>Some workers get a different promotion. The group offers a &quot;merchant services&quot; or &quot;payment processing&quot; role: the platform &quot;needs local payment channels,&quot; and your job is to receive incoming transfers on your bank account or payment app, convert them to crypto, and send them to a platform address, keeping a percentage commission.</p><p>Understand what this job actually is. The money arriving in your account is other victims&apos; money — deposits from the task funnel, or proceeds from an entirely separate fraud. Your role converts traced bank money into untraceable crypto and breaks the paper trail at the point where it is most convenient: you. The operators never touch the fiat. You are the insulation.</p><p>The FBI describes the arrangement without euphemism in its <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.fbi.gov/contact-us/field-offices/houston/news/press-releases/fbi-warns-of-money-mules">money mule warning</a>: criminals recruit mules to launder proceeds derived from online scams, and — the sentence that ends every &quot;I was just working&quot; defense — <em>&quot;acting as a money mule is illegal and punishable, even if you aren&apos;t aware you&apos;re committing a crime.&quot;</em></p><p>Two details make the mule role worse than the deposit role:</p><ul><li><p><strong>The money is provably stolen.</strong> When investigators unravel a fraud ring, the mule accounts are the visible surface. Each inbound transfer has a victim and a police report attached somewhere.</p></li><li><p><strong>You handed over your identity.</strong> The role requires a real bank account, and the crypto leg typically goes through a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/kyc/">KYC&apos;d</a> exchange account in your own name. The trail does not just pass through you; it is <em>named</em> you.</p></li></ul><p>A related variant skips the task theater entirely: an &quot;employer&quot; or online romantic partner asks to send money through your account, or a &quot;trading firm&quot; hires you as a payments clerk. Same machine, different wallpaper.</p><h2 level="2" textAlign="left" id="h-what-a-mule-wallet-looks-like-on-chain">What a Mule Wallet Looks Like On-Chain</h2><p>The mule leg of the scheme is visible from the outside, and it is worth knowing the pattern in both directions — to check an address you&apos;re about to interact with, and to understand what investigators and analytics firms see when they look at yours.</p><p>Paste the wallet address into any <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/block-explorer/">block explorer</a> and the structure jumps out:</p><ul><li><p><strong>Fan-in.</strong> Dozens or hundreds of small inbound transfers from unrelated addresses — different clusters, different patterns, no common counterparty. A normal salary or trading wallet shows few, regular counterparties. A mule wallet looks like a drain grate.</p></li><li><p><strong>Fast pass-through.</strong> Inflows leave within minutes. Balances don&apos;t accumulate because the mule&apos;s job is to forward, not hold. Watch the timing: a transfer arrives, and the same value minus commission exits toward a single consolidation address.</p></li><li><p><strong>Convergence on an exchange.</strong> The pass-through ends, repeatedly, at deposit addresses for a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/cex/">CEX</a> — the off-ramp where crypto becomes spendable money. Operators cycle through mules precisely because each exchange address burns out fast.</p></li><li><p><strong>Inherited labels.</strong> Analytics providers and community-maintained databases tag addresses by their transaction partners. Once stolen-fund flows pass through your wallet, the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/wallet-labels/">wallet labels</a> attached to it stop being about you — they become the labels of every victim and every scam cluster upstream. Risk-scoring services rate addresses exactly this way; our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/address-risk-scoring-explained/">address risk scoring</a> guide covers how a &quot;high risk&quot; designation forms and propagates.</p></li><li><p><strong>Angry counterparties.</strong> Victims trace their own stolen transactions, find your address mid-chain, and file reports — against you. From the victim&apos;s side you are the last leg they can see.</p></li></ul><p>Some operators route pass-through funds through a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/mixer/">mixer</a> before the exchange leg. That does not launder your position — it just adds &quot;proximity to a sanctioned mixer&quot; to the list of things your address is now known for.</p><h2 level="2" textAlign="left" id="h-the-consequences-ladder">The Consequences Ladder</h2><p>The unwinding, when it comes, tends to follow the same order regardless of country:</p><ol><li><p><strong>Exchange freeze.</strong> The exchange&apos;s own monitoring — or a law-enforcement request — freezes the account you used for pass-through deposits. Withdrawals locked, pending review.</p></li><li><p><strong>Bank freeze.</strong> A victim&apos;s report or a cross-bank fraud flag lands on the receiving account. In most jurisdictions, &quot;the funds are frozen pending investigation&quot; can mean weeks to months, and you will be explaining inflows one by one.</p></li><li><p><strong>Named party.</strong> Somewhere in a case file, your account appears in the fund-flow chart between a victim and a cluster. &quot;I didn&apos;t know&quot; determines charging decisions, not whether you appear.</p></li><li><p><strong>Criminal exposure.</strong> Where &quot;knowing&quot; can be argued — you ignored obvious red flags, the commission was implausibly high, the &quot;employer&quot; was anonymous — muling drifts from victimhood toward accomplice liability. The FBI&apos;s warning exists because &quot;I was unaware&quot; is a question for a courtroom, not a shield.</p></li></ol><h2 level="2" textAlign="left" id="h-red-flags-the-task-job-checklist">Red Flags: The Task-Job Checklist</h2><ul><li><p>Any job that asks <strong>you to pay</strong> to unlock work, tiers, withdrawals, taxes, or &quot;data corrections.&quot;</p></li><li><p>Earnings screenshots in a group where everyone is celebrating constantly. Real workplaces are not that happy.</p></li><li><p>The platform has its own crypto site you must deposit on, connected via your wallet.</p></li><li><p>Withdrawal &quot;errors&quot; that require payment to fix. No legitimate payroll works this way.</p></li><li><p>A role receiving third-party money into your bank account or payment app and forwarding it as crypto, minus commission — the mule role, whatever it is called.</p></li><li><p>Anonymous &quot;employers&quot;: no company name, no contract, no verification, communication only through Telegram groups that periodically dissolve and reform.</p></li><li><p>Pressure to recruit friends — your social graph is inventory too.</p></li></ul><p>One flag is a coincidence. Three is a pattern, and the pattern has a name.</p><h2 level="2" textAlign="left" id="h-if-you-are-already-inside">If You Are Already Inside</h2><p>The unwinding protocol, in order:</p><ol><li><p><strong>Stop forwarding.</strong> Every additional transfer deepens the exposure. This is true even mid-&quot;shift,&quot; even with a commission pending.</p></li><li><p><strong>Freeze, don&apos;t spend, don&apos;t return.</strong> Leave the remaining balance untouched. Do not send it back to the &quot;employer&quot; — that destroys evidence and pays the operators twice. Do not pick a victim from the incoming transfers and refund them directly; you cannot refund all of them, and partial self-help complicates every case. Funds should move on the instructions of your bank, the exchange, or law enforcement — nobody else.</p></li><li><p><strong>Preserve everything.</strong> Group names and links, the platform URL, handle names, task screenshots, payment instructions, and every transaction hash in and out. Time-stamp them. This is the difference between &quot;victim who documented&quot; and &quot;account holder with no story.&quot;</p></li><li><p><strong>Report.</strong> In the US, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-report-crypto-scam/">file with IC3</a> — the same report pipeline that tracks task scamming. Elsewhere, your national cybercrime channel. Include the hashes; investigators can join your report to existing cases through the on-chain trail.</p></li><li><p><strong>Call your bank and exchange proactively.</strong> &quot;I believe I received fraud proceeds through a task scam&quot; is a survivable conversation. Having it <em>after</em> they freeze the account, unprompted, is a worse version of the same conversation.</p></li><li><p><strong>Distrust the follow-up.</strong> After you report or freeze, someone will DM you offering to recover your deposits or &quot;clear&quot; your account — for a fee. That is round two, aimed at people who have just self-identified as victims. The same rule from our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/fake-customer-support-scams/">fake support guide</a> applies: anyone who contacts you first with a fix is selling the next stage of the problem.</p></li></ol><h2 level="2" textAlign="left" id="h-why-it-keeps-working">Why It Keeps Working</h2><p>The task scam is the only major fraud pattern that pays before it takes. Every other script in this archive — <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/phishing-attack/">phishing</a>, drainers, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/social-engineering/">social engineering</a> plays — must extract before it gives anything back. The task funnel inverts the burden of proof: the victim has already been paid, so the deposit stage feels earned rather than risky, and the mule stage feels like a promotion rather than a trap.</p><p>That inversion is also the defense. When easy money arrives before any work of value exists, the work was never the product. You were.</p><h2 level="2" textAlign="left" id="h-related-reading">Related Reading</h2><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-report-crypto-scam/">How to report a crypto scam</a> — the full reporting pipeline, evidence checklist, and what happens after you file</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/wallet-labels/">Wallet labels explained</a> — how addresses get tagged, and why mule wallets inherit the worst label upstream of them</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/pig-butchering-crypto-tracing/">Pig butchering tracing</a> — the slower, romantic cousin of the same funnel</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/telegram-airdrop-bot-scams/">Telegram airdrop bot scams</a> — the same groups, airdrop flavor: where task groups and claim bots overlap</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/how-to-detect-nft-wash-trading/">How to detect NFT wash trading</a> — fake volume and fake tasks are the same industry: manufactured proof, sold as opportunity</p></li></ul><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-task-scam-money-mule/"><em>https://theonchaindiary.com/articles/crypto-task-scam-money-mule/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/938ca248c6ab1c588304b5e8432220dee7e6db0b1e5ffc8e549ae307e14a6335.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Abstract Chain Is Shutting Down: Bridge Out Before December 15 or Lose Access]]></title>
            <link>https://paragraph.com/@onchaindiary/abstract-chain-shutdown-migration-guide</link>
            <guid>ivjfhjdM1Zt6BewrNKpw</guid>
            <pubDate>Sun, 11 Oct 2026 07:48:50 GMT</pubDate>
            <description><![CDATA[On October 6, 2026, Abstract announced on X that it is winding down: the chain shuts down on December 15, 2026, and "any funds not bridged by this date will be inaccessible." If you hold anything on Abstract — ETH, stablecoins, tokens, NFTs, balances inside Abstract apps or the Abstract Global Wallet — this article is your exit runbook: what actually closes and when, the three official exit routes, how this deadline differs from the Blast shutdown four days earlier, and the phishing wave that...]]></description>
            <content:encoded><![CDATA[<p>On October 6, 2026, Abstract announced on X that it is winding down: the chain shuts down on December 15, 2026, and &quot;any funds not bridged by this date will be inaccessible.&quot;</p><p>If you hold anything on Abstract — ETH, stablecoins, tokens, NFTs, balances inside Abstract apps or the Abstract Global Wallet — this article is your exit runbook: what actually closes and when, the three official exit routes, how this deadline differs from the Blast shutdown four days earlier, and the phishing wave that has already started forming around the word &quot;migration.&quot;</p><h2 level="2" textAlign="left" id="h-what-happened-in-one-paragraph">What happened, in one paragraph</h2><p>Abstract was the Ethereum <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/layer-2/">layer 2</a> built by Igloo Inc., the parent company of Pudgy Penguins, after Igloo acquired the Frame network in 2024 and rebuilt it on the ZK Stack. Mainnet went live in January 2025 with a thesis: consumer crypto — apps, brands, IP — would onboard the next wave of users through a chain instead of a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/bridge/">bridge</a> to nowhere. By the project&apos;s own figures the products worked: 144 apps deployed, more than 400,000 users onboarded, over 325 million transactions, and tie-ins with Red Bull Racing and Disney. None of it made the chain sustainable as a business. The announcement is unusually candid about why: growth &quot;began to stagnate&quot; under a restricted DeFi ecosystem, thin liquidity, minimal institutional crossover, and a budget smaller than competitors&apos;. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://l2beat.com/layer2s/projects/abstract">L2BEAT</a> counted roughly $47 million in value on the chain shortly before the announcement; <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://defillama.com/chain/Abstract">DefiLlama</a> showed DeFi apps on the chain holding under $10 million by the day after — most of the stranded value is plain bridged balances, not farm deposits. CEO Luca Netz <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/LucaNetz/status/2107555395640463480">wrote</a> that Igloo had quietly funded Abstract for 18 months, lost &quot;tens of millions of dollars&quot; over two years, deliberately chose not to launch a token or ICO, and &quot;could no longer justify taking from the Pudgy Penguins business.&quot; Igloo&apos;s focus now returns to the penguins and the PENGU token.</p><h2 level="2" textAlign="left" id="h-this-deadline-is-different-from-blasts">This deadline is different from Blast&apos;s</h2><p>Four days before Abstract&apos;s announcement, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/blast-l2-shutdown-withdrawal-guide/">Blast announced its own shutdown</a> — and the two exits are not the same shape. Knowing the difference is the difference between a calm migration and panic-driven mistakes.</p><table class="paragraph-table"><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><br></th><th colspan="1" rowspan="1"><p>Blast (announced Oct 2)</p></th><th colspan="1" rowspan="1"><p>Abstract (announced Oct 6)</p></th></tr><tr><td colspan="1" rowspan="1"><p>Deadline</p></td><td colspan="1" rowspan="1"><p>Oct 26 — interface closes</p></td><td colspan="1" rowspan="1"><p>Dec 15 — <strong>chain shuts down</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>After the deadline</p></td><td colspan="1" rowspan="1"><p>Funds stay recoverable via bridge contracts on Ethereum L1</p></td><td colspan="1" rowspan="1"><p>&quot;Any funds not bridged by this date will be inaccessible&quot;</p></td></tr><tr><td colspan="1" rowspan="1"><p>Official exit</p></td><td colspan="1" rowspan="1"><p>Blast interface, then L1 contracts</p></td><td colspan="1" rowspan="1"><p>Migration Hub + native bridge + listed third-party bridges</p></td></tr><tr><td colspan="1" rowspan="1"><p>Post-deadline recovery path</p></td><td colspan="1" rowspan="1"><p>Published (contract instructions promised)</p></td><td colspan="1" rowspan="1"><p>None announced</p></td></tr></tbody></table><p>The Blast deadline was an interface deadline. Abstract&apos;s is an asset deadline. As of the announcement there is no published route — no L1 contract walkthrough, no grace period — for recovering funds left on the chain after December 15. Maybe one gets published later; you should not plan your money around a maybe that has not been announced.</p><h2 level="2" textAlign="left" id="h-the-three-official-exit-routes">The three official exit routes</h2><p>Abstract&apos;s announcement points to two official properties, and the Migration Hub adds a third layer:</p><ol><li><p><strong>Migration Hub — migrate.abs.xyz.</strong> The primary exit. The hub also lists third-party bridges Stargate, Relay and Jumper as supported routes out.</p></li><li><p><strong>Native bridge — native-bridge.abs.xyz.</strong> Works directly, with a stated 3-hour delay on exits.</p></li><li><p><strong>Your own inventory.</strong> Plain wallet balances, balances inside Abstract&apos;s 144 apps, and assets held through the Abstract Global Wallet are all on the same clock. The engineering and ecosystem team says it will work with Abstract-based projects to relocate them — but a project that fails to migrate takes your in-app balances&apos; exit path with it.</p></li></ol><p>The mechanical exit checklist:</p><ol><li><p><strong>Inventory everything.</strong> Wallet balances, app balances, LP positions, NFTs listed on Abstract marketplaces, anything staked. If it lives in an app contract rather than your wallet, your exit depends on that app&apos;s migration, not just the bridge.</p></li><li><p><strong>Move early, in the official places.</strong> Type the domains yourself: migrate.abs.xyz and native-bridge.abs.xyz. Cross-check any link against Abstract&apos;s official X account and Discord before you connect a wallet — the announcement itself warns of impersonation and fake migration sites.</p></li><li><p><strong>Know where funds land.</strong> The native bridge exits to Ethereum mainnet — plan gas and destination wallet in advance. If you use a listed third-party bridge, confirm the destination chain before signing.</p></li><li><p><strong>Sign only what you can read.</strong> A migration is a bridge transaction. It is not a seed-phrase prompt, not an unlimited approval to an unfamiliar contract, not a &quot;verification&quot; signature. If a popup asks for anything beyond a standard send or bridge, stop — that pattern is <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/signature-scam-explained/">signature phishing</a>, and shutdowns are its favorite hunting season.</p></li></ol><h2 level="2" textAlign="left" id="h-the-scam-wave-has-already-been-announced-by-the-victims-side">The scam wave has already been announced — by the victims&apos; side</h2><p>Every chain shutdown in crypto history has been followed by the same parasite ecosystem, and Abstract&apos;s team knows it: the announcement dedicates a full paragraph to warning users about &quot;impersonation, fake migration sites, and DMs claiming to represent Abstract.&quot; When the operator itself puts that warning in the shutdown notice, assume the attacks are not a risk — they are a schedule.</p><p>What the wave looks like in practice:</p><ul><li><p><strong>Fake Migration Hub clones.</strong> Near-identical copies of migrate.abs.xyz with one contract address swapped. Bookmark the real domain now; type it, never paste it from a DM.</p></li><li><p><strong>&quot;Expedited migration&quot; fees.</strong> Nobody can move you up the bridge queue for a fee. The native bridge&apos;s 3-hour delay is a parameter, not congestion — anyone selling a bypass is selling nothing.</p></li><li><p><strong>Fake support accounts.</strong> Abstract support will not DM you first. Unsolicited &quot;help&quot; in replies and DMs follows the standard <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/social-media-crypto-scam-playbook/">social media scam playbook</a>.</p></li><li><p><strong>Address poisoning in the exit flow.</strong> When you paste the destination address for a large exit, a poisoned clipboard entry that mimics your real address is the cheapest attack that works. The defense is character-by-character verification, which we break down in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/address-poisoning-attacks-explained/">address poisoning</a>.</p></li><li><p><strong>&quot;Abstract 2.0&quot; re-registration claims.</strong> Any message saying you must sign something to &quot;keep your balance&quot; on a successor chain is a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/wallet-drainer/">wallet drainer</a> with a deadline costume on. No legitimate migration ever needs your <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/seed-phrase/">seed phrase</a>.</p></li></ul><p>If someone offers to recover funds you have not lost yet, that is the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-recovery-scams-explained/">recovery scam</a> pattern arriving before the loss. Shut it down.</p><h2 level="2" textAlign="left" id="h-why-consumer-chains-are-dying-two-shutdowns-in-five-days">Why consumer chains are dying: two shutdowns in five days</h2><p>Blast and Abstract failed for different stated reasons — Blast could not cover operating costs; Abstract could not find sustainable growth inside a consumer-crypto-only lane — but the underlying lesson rhymes. A chain is a business. When the business stops being fundable, the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/layer-2/">layer 2</a> stops.</p><p>Abstract is the sharper version of the lesson, because by every product metric the company published, the consumer thesis <em>worked</em>: 400,000 onboarded users, 325 million transactions, Disney and Red Bull Racing activations, a smart wallet (Abstract Global Wallet) the team calls the most adopted in crypto. Users came. What never came was the economics around them — the DeFi depth, the liquidity, the institutional money that turns activity into a chain that funds itself. Netz&apos;s own framing closes the case: Igloo &quot;could no longer justify taking from the Pudgy Penguins business.&quot; The chain was a business unit of an IP company, and when the unit&apos;s burn rate collided with the brand&apos;s balance sheet, the unit went.</p><p>That is the sizing rule, again, with a different face on it: a balance on someone else&apos;s chain is a claim against that someone&apos;s willingness to keep paying. Blast users got a runway; Abstract users get one too — ten weeks. Funds you cannot afford to strand on a corporate budget decision belong on mainnet or in cold storage.</p><h2 level="2" textAlign="left" id="h-what-is-still-unknown">What is still unknown</h2><ul><li><p><strong>No post-deadline recovery path has been announced.</strong> The &quot;inaccessible&quot; language may soften closer to the date (a Blast-style L1 contract walkthrough could appear), but nothing is published today. Check Abstract&apos;s official channels for updates rather than third-party summaries of them.</p></li><li><p><strong>App-dependent assets.</strong> If your assets sit inside an Abstract app rather than a plain balance, your exit path runs through that project&apos;s migration. Watch the projects&apos; own channels; the Abstract team says it will assist relocations.</p></li><li><p><strong>Third-party bridge availability.</strong> Stargate, Relay and Jumper are listed at the Migration Hub today; whether each keeps Abstract support live through December 15 is their decision, not Abstract&apos;s guarantee.</p></li></ul><p>We will update this article as the picture clarifies. The short version of every recommendation: bridge out through the official domains well before December 15, verify every address against official channels, and treat every unsolicited migration offer as an attack until proven otherwise.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/abstract-chain-shutdown-migration-guide/"><em>https://theonchaindiary.com/articles/abstract-chain-shutdown-migration-guide/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/174c03dd947ad88fe90b8c3428c588c895ee80ec7cbe9e25c1917ff012a367ea.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Blast L2 Is Shutting Down: How to Withdraw Safely Before October 26]]></title>
            <link>https://paragraph.com/@onchaindiary/blast-l2-shutdown-withdrawal-guide</link>
            <guid>d8R5QilwwBTbJLL7upzs</guid>
            <pubDate>Sat, 03 Oct 2026 05:44:42 GMT</pubDate>
            <description><![CDATA[On October 2, 2026, Blast announced on X that it is shutting down its Ethereum layer 2 network. The reason was blunt: "the ongoing costs of maintaining Blast exceed the revenue generated by the L2, and we do not see a credible path to making the chain economically sustainable." If you hold assets on Blast — in a wallet, in a dApp, or in the Blast progressive web app — this article is your exit runbook: what happens and when, how to withdraw at each stage, what to do if you miss the interface ...]]></description>
            <content:encoded><![CDATA[<p>On October 2, 2026, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/blast/status/2106032805280891073">Blast announced on X</a> that it is shutting down its Ethereum <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/layer-2/">layer 2</a> network. The reason was blunt: &quot;the ongoing costs of maintaining Blast exceed the revenue generated by the L2, and we do not see a credible path to making the chain economically sustainable.&quot;</p><p>If you hold assets on Blast — in a wallet, in a dApp, or in the Blast progressive web app — this article is your exit runbook: what happens and when, how to withdraw at each stage, what to do if you miss the interface deadline, and the scam patterns that reliably follow announcements like this one.</p><h2 level="2" textAlign="left" id="h-what-happened-in-one-paragraph">What happened, in one paragraph</h2><p>Blast was built by Tieshun &quot;Pacman&quot; Roquerre, the founder of Blur, and backed by $20 million from Paradigm and Standard Crypto. It opened for deposits in November 2023 before the chain even existed — with withdrawals disabled — and pulled in $300 million within days on the promise of native yield and a future airdrop. Mainnet went live in February 2024, the BLAST token debuted in June 2024 at a $2 billion fully diluted valuation, and the chain peaked at roughly $2.26 billion in total value locked that same month, per <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://defillama.com/chain/Blast">DefiLlama</a>. On the day of the shutdown announcement, DefiLlama showed about $32 million left in DeFi apps on the chain, and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://l2beat.com/layer2s/projects/blast">L2Beat</a> counted roughly $90 million in total value secured — about $50 million of it bridged in through Blast&apos;s canonical bridge. The BLAST token fell about 32% on the news to roughly $0.00028, about 99% below its 2024 high, per <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.coingecko.com/en/coins/blast">CoinGecko</a>. The team apologized to &quot;the users and developers who believed in Blast, built on it, and supported the ecosystem,&quot; and said its priority is making the shutdown &quot;as smooth and safe as possible.&quot;</p><h2 level="2" textAlign="left" id="h-the-shutdown-timeline">The shutdown timeline</h2><p>Blast is winding down in stages, and each stage changes what you can do:</p><table class="paragraph-table"><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>When</p></th><th colspan="1" rowspan="1"><p>What happens</p></th><th colspan="1" rowspan="1"><p>What it means for you</p></th></tr><tr><td colspan="1" rowspan="1"><p>Oct 2, 2026</p></td><td colspan="1" rowspan="1"><p>Shutdown announced</p></td><td colspan="1" rowspan="1"><p>Start planning your exit; do not wait</p></td></tr><tr><td colspan="1" rowspan="1"><p>~Oct 2–9 (about one week)</p></td><td colspan="1" rowspan="1"><p>Blast pulls its assets out of Lido</p></td><td colspan="1" rowspan="1"><p>Withdrawals are temporarily unavailable — this is announced behavior, not a sign of theft</p></td></tr><tr><td colspan="1" rowspan="1"><p>After the Lido unwind</p></td><td colspan="1" rowspan="1"><p>Withdrawals resume, delay cut to 24 hours</p></td><td colspan="1" rowspan="1"><p>The main exit window opens; withdraw here if you can</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 26, 2026</p></td><td colspan="1" rowspan="1"><p>Last day for the normal Blast interface</p></td><td colspan="1" rowspan="1"><p>The easy path closes</p></td></tr><tr><td colspan="1" rowspan="1"><p>After Oct 26</p></td><td colspan="1" rowspan="1"><p>Assets still recoverable via Blast bridge contracts on Ethereum L1</p></td><td colspan="1" rowspan="1"><p>Manual contract interaction; instructions promised before the deadline</p></td></tr></tbody></table><p>Two details are easy to misread. First, the withdrawal pause at the start is expected: Blast&apos;s native-yield model parked users&apos; ETH in Lido (that is where the yield came from), and that position has to be unwound before the bridge can pay out at full capacity — a process the team expects to take about a week. Second, October 26 is a deadline for the <em>interface</em>, not for your property. Funds left after that date remain withdrawable through the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/bridge/">bridge</a> contracts on Ethereum mainnet, as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://unchainedcrypto.com/ethereum-layer-2-blast-is-shutting-down-saying-costs-now-exceed-what-the-chain-earns/">Unchained</a> and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cointelegraph.com/news/blast-to-wind-down-ethereum-l2-after-costs-outpace-revenue">Cointelegraph</a> both confirmed from the announcement.</p><p>That said, &quot;recoverable through direct contract interaction&quot; is a meaningful downgrade in usability. Manual bridge-contract withdrawals mean constructing the right transaction against the right contract with the right parameters — no UI safety rail, and fertile ground for scammers offering to &quot;help.&quot;</p><h2 level="2" textAlign="left" id="h-how-to-withdraw-safely-before-october-26">How to withdraw safely before October 26</h2><ol><li><p><strong>Inventory everything.</strong> Check ordinary wallet balances on Blast, balances inside Blast dApps, and balances in the Blast PWA. Blast&apos;s announcement explicitly covers PWA balances — money in the app is not exempt from the deadline.</p></li><li><p><strong>Wait out the pause, then move early.</strong> Once withdrawals resume with the 24-hour delay, do not wait until the final week of the interface window. Exit queues and support backlogs get worse as deadlines approach, and every day you wait is a day scammers have to find you.</p></li><li><p><strong>Use the official route only.</strong> Withdraw through the Blast interface at the blast.io domain you already use — typed or from your own bookmark, never from a link in a DM, ad, or &quot;shutdown guide&quot; someone sent you.</p></li><li><p><strong>Expect the destination to be Ethereum mainnet.</strong> The announcement names Ethereum mainnet as the exit destination. Plan where the funds land: a wallet you control, with gas (ETH) available on L1.</p></li><li><p><strong>Watch what you sign.</strong> During the exit window you should be signing normal withdrawal transactions. Anything asking for unusual approvals, blind-signed messages, or your seed phrase is not part of the process. Our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/signature-scam-explained/">signature phishing walkthrough</a> covers the patterns in detail.</p></li></ol><h2 level="2" textAlign="left" id="h-if-you-miss-the-deadline">If you miss the deadline</h2><p>Funds stay recoverable after October 26, but only through direct interaction with the Blast bridge contracts on Ethereum L1. Blast has said it will publish detailed instructions before the cutoff. When those instructions appear, verify them against the official Blast channels — and treat any third party offering to perform the contract withdrawal &quot;for a small fee&quot; as a scam until proven otherwise. That offer is structurally identical to the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-recovery-scams-explained/">fake recovery services</a> that shadow every major crypto loss event: the shutdown version just replaces &quot;stolen funds&quot; with &quot;stuck funds.&quot;</p><h2 level="2" textAlign="left" id="h-wind-down-not-rug-pull-how-to-tell-the-difference">Wind-down, not rug pull — how to tell the difference</h2><p>A chain announcing its own death with a withdrawal runway is categorically different from an <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/rug-pulls-explained/">exit scam</a>. The signals that separate an orderly wind-down from a rug:</p><table class="paragraph-table"><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Signal</p></th><th colspan="1" rowspan="1"><p>Orderly wind-down (Blast&apos;s stated plan)</p></th><th colspan="1" rowspan="1"><p>Rug pull pattern</p></th></tr><tr><td colspan="1" rowspan="1"><p>Announcement</p></td><td colspan="1" rowspan="1"><p>Public, dated, on official channels</p></td><td colspan="1" rowspan="1"><p>Sudden silence or deleted accounts</p></td></tr><tr><td colspan="1" rowspan="1"><p>Funds</p></td><td colspan="1" rowspan="1"><p>Withdrawable on a published schedule</p></td><td colspan="1" rowspan="1"><p>Bridge drained or withdrawals permanently frozen</p></td></tr><tr><td colspan="1" rowspan="1"><p>Friction</p></td><td colspan="1" rowspan="1"><p>Delays are explained and bounded (1-week Lido unwind, then 24h)</p></td><td colspan="1" rowspan="1"><p>Excuses that shift every week with no end date</p></td></tr><tr><td colspan="1" rowspan="1"><p>Team behavior</p></td><td colspan="1" rowspan="1"><p>Publishes contracts path + instructions before cutoff</p></td><td colspan="1" rowspan="1"><p>Disappears, or pushes users to a &quot;new&quot; chain</p></td></tr></tbody></table><p>None of this makes the shutdown painless — roughly $50 million was still bridged through the canonical bridge as of Friday per L2Beat, and users now carry the operational burden of moving it. But it does mean panic-driven mistakes are the main way people actually lose money in scenarios like this one. Panic is what the scam wave feeds on.</p><h2 level="2" textAlign="left" id="h-the-scam-wave-is-the-real-threat">The scam wave is the real threat</h2><p>Every major shutdown, hack, or migration announcement in crypto history has been followed by the same parasite ecosystem. Expect all of the following dressed in Blast branding:</p><ul><li><p><strong>Fake &quot;expedited withdrawal&quot; services.</strong> Sites or accounts claiming they can bypass the withdrawal queue or the 24-hour delay for a fee. There is no queue to bypass — the delay is a protocol parameter, not a congestion problem.</p></li><li><p><strong>Fake support accounts.</strong> Blast support will not DM you first. Anyone in your mentions offering hands-on help with your withdrawal is running the standard <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/social-media-crypto-scam-playbook/">social media scam playbook</a>.</p></li><li><p><strong>Phishing clones of the shutdown instructions.</strong> When Blast publishes its L1 bridge-contract guide, expect near-identical copies with one contract address changed. Bookmark the official domain now; verify any contract address against multiple independent sources before interacting.</p></li><li><p><strong>&quot;Blast 2.0&quot; migration claims.</strong> Any claim that you must &quot;migrate&quot; or &quot;re-register&quot; your balance on a successor chain to keep it — especially one requiring a signature — is a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/wallet-drainer/">wallet drainer</a> pattern. No legitimate migration ever requires your seed phrase.</p></li><li><p><strong>Address poisoning in the exit flow.</strong> When you are copying the destination address for a large withdrawal, a poisoned clipboard entry that looks almost identical to your real address is a real risk. Read our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/address-poisoning-attacks-explained/">address poisoning breakdown</a> — the few extra seconds of character-by-character verification are the whole defense.</p></li></ul><p>The general rules do not change: never enter your seed phrase on any website, never sign messages you cannot read, and treat urgency — real or manufactured — as a signal to slow down.</p><h2 level="2" textAlign="left" id="h-the-structural-lesson-what-an-l2-balance-actually-is">The structural lesson: what an L2 balance actually is</h2><p>Blast&apos;s shutdown is a clean demonstration of something most L2 users prefer not to think about: your balance on a layer 2 is not an Ethereum balance with extra steps. It is a claim against a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/cross-chain-bridge/">bridge</a> operated by the chain&apos;s team, sequenced by a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/sequencer/">sequencer</a> the team runs, and — in Blast&apos;s case — backed by assets parked in a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/liquid-staking/">liquid staking</a> position whose unwinding now sets the pace of everyone&apos;s exit. When the business behind the chain stops being viable, the user&apos;s &quot;self-custody&quot; is only as good as the wind-down process the operator chooses to run.</p><p>Blast is at least running one. It is also not alone in reaching this endpoint: the same economics have already taken out smaller L2s like Kinto and zkLend, as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://startupfortune.com/blast-shuts-down-the-ethereum-layer-2-network-that-once-held-23-billion/">Startup Fortune noted</a>. Chains that paid users yield out of their own treasury economics had a business model, not a protocol invariant — and business models can end.</p><p>The takeaway is not &quot;never use L2s.&quot; It is a sizing rule: funds you cannot afford to move on someone else&apos;s schedule should not sit on a chain whose operator you cannot audit. Keep transaction balances on L2s; keep the rest on L1 or in cold storage, where no team&apos;s burn rate decides when you get to exit.</p><h2 level="2" textAlign="left" id="h-what-is-still-unknown">What is still unknown</h2><p>Honest limitations as of this writing:</p><ul><li><p>Blast has not announced a final sequencer halt date. At some point the chain itself stops producing blocks; until then, dApps on Blast may keep functioning even as the exit proceeds.</p></li><li><p>Nothing specific has been announced about assets locked inside Blast dApps (liquidity positions, NFTs listed on Blast marketplaces, staking contracts). If your assets are inside a dApp rather than a plain balance, your exit path depends on that dApp&apos;s contracts, not just Blast&apos;s bridge.</p></li><li><p>The promised L1 bridge-contract instructions have not been published yet. Verify any guide you find against Blast&apos;s official channels before following it.</p></li></ul><p>We will update this article as Blast publishes the contract instructions or any schedule changes. The short version of every recommendation above: withdraw through the official interface as soon as withdrawals resume, finish well before October 26, and assume every unsolicited offer of help is an attack.</p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/blast-l2-shutdown-withdrawal-guide/"><em>https://theonchaindiary.com/articles/blast-l2-shutdown-withdrawal-guide/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/cf52779d5b112b53241f4d5d7420aea6250539718327102e0db783cb418a12f8.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[NEAR Intents Hack Explained: How a Signed-Note Bug Drained $3.87M]]></title>
            <link>https://paragraph.com/@onchaindiary/near-intents-hack-explained</link>
            <guid>4ncpvBdBrwo9EQjHrxYT</guid>
            <pubDate>Fri, 02 Oct 2026 04:58:31 GMT</pubDate>
            <description><![CDATA[NEAR Intents, a cross-chain swap service on NEAR, lost $3.87 million on October 1, 2026 — almost all of it USDT — after an attacker exploited a bug in the service's deposit-and-withdrawal plumbing. The team halted services, confirmed the incident at 12:53 UTC, patched the contract-side flaw within about an hour of detection, and pledged to repay users in full. If you follow crypto security incidents, one detail sets this one apart from the usual drainer story: no user signed anything wrong. T...]]></description>
            <content:encoded><![CDATA[<p>NEAR Intents, a cross-chain swap service on NEAR, lost $3.87 million on October 1, 2026 — almost all of it USDT — after an attacker exploited a bug in the service&apos;s deposit-and-withdrawal plumbing. The team halted services, confirmed the incident at 12:53 UTC, patched the contract-side flaw within about an hour of detection, and pledged to repay users in full.</p><p>If you follow crypto security incidents, one detail sets this one apart from the usual drainer story: no user signed anything wrong. The attack worked entirely above the user layer, inside the machinery that decides who is owed what. Understanding that machinery — and where the money went — is useful for anyone who keeps balances inside swap services, bridges, or intent-based platforms.</p><h2 level="2" textAlign="left" id="h-what-near-intents-is-and-where-it-keeps-your-money">What NEAR Intents is, and where it keeps your money</h2><p>NEAR Intents is a swap service. You hand it a coin on one chain and it pays you a different coin on another — no bridge UI, no manual hopping. It is one of NEAR&apos;s busiest applications, and it landed in the news days after a US spot NEAR ETF started trading.</p><p>To work across chains, the service keeps vaults of coins on each chain it serves. This incident centered on a vault contract on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/bridge/">BNB Chain</a> — Bitquery&apos;s address labels tie the vault to the HOT Protocol contract family, while NEAR Intents calls the surrounding system its Omni deposit-and-withdrawal infrastructure.</p><p>The payout mechanism matters, because that is exactly what failed. In simplified form:</p><ol><li><p><strong>Deposit.</strong> You send coins to the vault. The service credits your internal balance.</p></li><li><p><strong>Signed note.</strong> When you want to withdraw, NEAR Intents&apos; back end signs a short note: pay this amount, to this wallet.</p></li><li><p><strong>Payout.</strong> Whoever holds that note hands it to the vault. The vault checks the signature and pays.</p></li></ol><p>Your balance does not live on BNB Chain. It lives in the service&apos;s own bookkeeping, and the signed note is how that bookkeeping tells the vault what you are owed. The vault, in other words, is a cashier that trusts the ledger behind it. That is the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/intent-based-architecture/">intent-based architecture</a> trade-off in miniature: smooth cross-chain UX, at the cost of a trusted middle layer holding <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/hot-wallet/">hot wallet</a> funds.</p><h2 level="2" textAlign="left" id="h-the-bug-notes-the-vault-had-every-reason-to-honor">The bug: notes the vault had every reason to honor</h2><p>By NEAR Intents&apos; account, the bug lived in how the Omni deposit-and-withdrawal infrastructure talked to its smart contracts — the side that decides who is owed what. The vault did as it was told.</p><p>Bitquery&apos;s reconstruction supports that reading. All seven of the attacker&apos;s withdrawals — two tiny tests, then the five big ones — came with notes in the same form as every legitimate user&apos;s. The signature verification was not broken. The balances behind the notes were.</p><p>That distinction is the whole story. An attacker who breaks signature verification must defeat cryptography. An attacker who gets the bookkeeping layer to believe in a balance only has to defeat a database — and a buggy integration is as good as a forged note. For the user, it means the service&apos;s promise (&quot;we will pay whoever our ledger says we owe&quot;) is only as strong as the ledger&apos;s integrity.</p><p>This is also why this incident is categorically different from the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/signature-scam-explained/">signature phishing</a> and drainer attacks we usually cover. Those start at your wallet, with a bait claim page and a malicious approval. Here, the claim page never entered the picture. The vault paid out from user deposits because the internal accounting said to.</p><h2 level="2" textAlign="left" id="h-timeline-of-the-theft">Timeline of the theft</h2><p>Bitquery indexed every hop, so the timeline is unusually complete:</p><table class="paragraph-table"><colgroup><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>When (UTC)</p></th><th colspan="1" rowspan="1"><p>What happened</p></th></tr><tr><td colspan="1" rowspan="1"><p>Sep 28</p></td><td colspan="1" rowspan="1"><p>Attacker&apos;s wallet is set up, funded with BNB for gas, swaps some to USDT</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sep 28 evening</p></td><td colspan="1" rowspan="1"><p>10 USDT deposited into the vault (building the position)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sep 30 ~18:00</p></td><td colspan="1" rowspan="1"><p>First test: 10 USDT withdrawn. About an hour later, an 11 USDT test</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sep 30 just before midnight</p></td><td colspan="1" rowspan="1"><p>First big withdrawal: 800,000 USDT</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 1, within the hour</p></td><td colspan="1" rowspan="1"><p>Two larger withdrawals (1.2M, 1.5M USDT)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 1, ~1 hour later</p></td><td colspan="1" rowspan="1"><p>Fourth withdrawal: 330,000 USDT</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 1, just after 06:00</p></td><td colspan="1" rowspan="1"><p>Fifth withdrawal: 35,000 USDT — total $3.87M</p></td></tr><tr><td colspan="1" rowspan="1"><p>Oct 1, 12:53</p></td><td colspan="1" rowspan="1"><p>NEAR Intents confirms the incident and pauses services</p></td></tr></tbody></table><p>Five withdrawals, about six hours, $3.87 million. The two 10-USDT probes the evening before are textbook attacker tradecraft: verify the mechanism end-to-end before committing.</p><h2 level="2" textAlign="left" id="h-where-the-money-went">Where the money went</h2><p>The laundering path is instructive, because it is the standard playbook for stolen <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/stablecoin/">stablecoins</a>:</p><ul><li><p><strong>76% — Bitcoin.</strong> $2.93M converted to 34.69 BTC across four Bitcoin wallets that had not spent a satoshi when Bitquery last checked. BTC held in fresh wallets is slow to trace and cheap to sit on.</p></li><li><p><strong>21% — KuCoin.</strong> $802k reached KuCoin deposit addresses by two routes. One of those addresses had been in use since August 6 — a detail that matters for investigators, because exchange deposit addresses sit behind KYC. This slice is the most realistic recovery target.</p></li><li><p><strong>2% — Monero exposure.</strong> The first batch was turned into a Monero token on Hyperliquid ($90k, unmoved). Monero is the classic exit toward untraceable value.</p></li><li><p><strong>1% — costs.</strong> Swap fees and price slippage along the way.</p></li></ul><p>Two details deserve emphasis. First, about a fifth of the loot ($822k) was swapped through NEAR Intents&apos; own service <em>during</em> the theft — including 750 BNB paid back to the very vault being drained. Second, the cross-chain swap provider Chainflip processed 17 of the attacker&apos;s swaps, then rejected the next three; within ten minutes the attacker moved to THORChain. That is the cat-and-mouse reality of front-line laundering controls: they slow the flow, they don&apos;t stop it.</p><p>If you want to go deeper on how investigators follow trails like this, our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/token-flow-analysis/">token flow analysis</a> walkthrough covers the techniques — and why the BTC-in-cold-wallets tail is where trails usually go cold.</p><h2 level="2" textAlign="left" id="h-not-the-first-cross-chain-incident-and-the-response-playbook">Not the first cross-chain incident, and the response playbook</h2><p>NEAR Intents said it had previously blocked a significant amount of suspicious transactions tied to an earlier hack elsewhere — blocking tainted inflows is one thing; having your own vault drained is another.</p><p>The response followed the now-standard incident playbook:</p><ul><li><p><strong>Pause everything.</strong> Services stopped, limiting further exposure.</p></li><li><p><strong>Patch fast.</strong> The contract-side flaw was fixed within about an hour of detection; core services returned quickly, with some cross-chain features offline longer.</p></li><li><p><strong>Pledge restitution.</strong> Users will be repaid in full, per the team&apos;s statement.</p></li><li><p><strong>Public pressure.</strong> The protocol&apos;s general manager gave the attacker a 48-hour window to return the funds and published three return addresses.</p></li><li><p><strong>Trace and engage.</strong> Work with law enforcement and blockchain analytics firms; AMLBot flagged the withdrawals and ZachXBT traced the outbound flows within the hour.</p></li></ul><p>The 48-hour ultimatum is more than theater. Money that reaches a KYC exchange is money the attacker can barely touch without exposure — every hour the $802k sits at KuCoin, the recovery odds improve. For a comparison of what victims and platforms can realistically do after funds move, see our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/stolen-crypto-first-24-hours/">stolen crypto: first 24 hours</a> guide and the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/recovery-help/">recovery help</a> hub.</p><h2 level="2" textAlign="left" id="h-what-this-means-for-ordinary-users">What this means for ordinary users</h2><p>The NEAR token dropped 6–10% on the news even though the NEAR chain itself never stopped — application-layer exploits get priced like protocol-layer ones. Separate the two in your head: your NEAR in your own wallet was never at risk here. The money at risk was money sitting <em>inside the service</em>.</p><p>That points at the practical takeaways:</p><ol><li><p><strong>A swap-service balance is a hot-vault deposit.</strong> When you finish a swap or a trade, withdraw to a wallet you control. Balances that linger are effectively interest-free loans to the platform&apos;s operational security.</p></li><li><p><strong>User-side OPSEC cannot cover platform-side bugs.</strong> Hardware wallet, careful signature review, revoked allowances — all of it assumes the theft starts at <em>your</em> keys. This one started at the ledger. Diversify where you park working balances, and size them like cash in someone else&apos;s safe.</p></li><li><p><strong>Recovery runs through chokepoints.</strong> Nearly a quarter of this haul is at an exchange, and that is where law enforcement actually gets leverage. It is also why the attacker&apos;s BTC-and-Monero tail exists: that money is parked, not spent, precisely because spending it risks exposure.</p></li><li><p><strong>Watch the pause, not the price.</strong> When a service halts withdrawals, assume the incident is material until a post-mortem says otherwise. Cheap insurance: move balances out during the uncertainty window.</p></li></ol><p>NEAR Intents has promised a full technical report. Until then, the working picture — a signed-note payout system, a bookkeeping bug, five withdrawals, and a laundering chain through BTC, THORChain, and KuCoin — is confirmed by the company&apos;s own statements and by independent on-chain tracing. We will update this article as the post-mortem and any recovery developments land.</p><h2 level="2" textAlign="left" id="h-sources">Sources</h2><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/near_intents/status/2105642219357241796">NEAR Intents incident statement (X)</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bitquery.io/investigations/near-intents-hack">Bitquery: NEAR Intents Hack — Where the $3.87M Went</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/AMLBotHQ/status/2105647685705597403">AMLBot flagging of the withdrawals (X)</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cryptobriefing.com/near-intents-attacker-48-hours-return-funds/">Crypto Briefing: NEAR Intents GM gives attacker 48 hours to return funds</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://finance.yahoo.com/markets/crypto/articles/near-intents-hacked-3-8-133008764.html">Yahoo Finance: NEAR Intents Hacked for $3.8 Million — Is NEAR Protocol Safe?</a></p></li></ul><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/near-intents-hack-explained/"><em>https://theonchaindiary.com/articles/near-intents-hack-explained/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/efd6c45a936da584feeb1d51368f8ba25954062da6a52ce4102d7b148e2083e4.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[GIWA Fake RPC Scam: Full Forensics of a 771-ETH Fake Bridge Built From Verified Code]]></title>
            <link>https://paragraph.com/@onchaindiary/giwa-fake-rpc-bridge-scam-explained</link>
            <guid>50vUwGXGf8KIqmUzIPRm</guid>
            <pubDate>Fri, 02 Oct 2026 04:58:24 GMT</pubDate>
            <description><![CDATA[On September 18, 2026, the GIWA ecosystem had a good news cycle: GIWATER, a DEX selected for Upbit's GIWA ecosystem incubation program, announced it had integrated a trading-card-game application — the first DEX in the Korean market to do so. GIWA itself is an Ethereum Layer 2 being built with Upbit, the largest Korean exchange, aimed at the Korean market. Its name recognition has been climbing since Dunamu filed GIWA trademarks a year ago. Eight days after that announcement, a swap frontend ...]]></description>
            <content:encoded><![CDATA[<p>On September 18, 2026, the GIWA ecosystem had a good news cycle: GIWATER, a DEX selected for Upbit&apos;s GIWA ecosystem incubation program, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.theblockbeats.info/flash/367799">announced</a> it had integrated a trading-card-game application — the first DEX in the Korean market to do so. GIWA itself is an Ethereum Layer 2 being built with Upbit, the largest Korean exchange, aimed at the Korean market. Its name recognition has been climbing since Dunamu <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.coindesk.com/web3/2025/09/08/upbit-parent-files-giwa-trademarks-amid-rumors-of-new-blockchain-launch">filed GIWA trademarks</a> a year ago.</p><p>Eight days after that announcement, a swap frontend branded DYORSWAP opened for business — and over the following fourteen hours, 1,331 unique addresses on Ethereum mainnet paid a combined 771.18 ETH into a contract they believed was the GIWA bridge.</p><p>This article reconstructs the operation from on-chain data we pulled ourselves — full transfer history paged through Etherscan&apos;s API, storage slots, balance snapshots at the block level, and the laundering chain. No screenshots, no secondhand numbers. The scam&apos;s design is worth studying in detail, because its central trick defeats the most common piece of due-diligence advice in crypto: &quot;check the contract on Etherscan.&quot;</p><h2 level="2" textAlign="left" id="h-what-a-fake-rpc-actually-controls">What a fake RPC actually controls</h2><p>Every wallet talks to a chain through an <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/rpc/">RPC</a> endpoint. Most users never think about theirs, because it arrives pre-configured. That is exactly the seam this attack targets.</p><p>If a frontend, tutorial, or &quot;helpdesk&quot; agent convinces you to point your wallet at an attacker-controlled RPC, the attacker now controls what your wallet <em>shows</em> you. Your keys never leave your device — they don&apos;t need to. A fake chain can display a balance that appears to arrive after you bridge. It can confirm transactions that happened nowhere. It can present any contract under any name.</p><p>In this incident, victims were onboarded to &quot;GIWA&quot; through the DYORSWAP interface, complete with a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/cross-chain-bridge/">cross-chain bridge</a> flow. The fake RPC made the theater self-consistent: you deposit, the fake environment shows your funds arriving on the &quot;L2,&quot; and nothing about the experience feels wrong. The theft is invisible at the moment it happens — the theft <em>is</em> the deposit transaction.</p><p>One detail from the transfer data shows how deep the theater went: the fake portal received 0.05 ETH <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://sepolia.etherscan.io/tx/0x0d3c7f0b668214874c39951fc619e248a46dbb93c4647a84ea89ebe45927cbdd">on Sepolia</a> and 0.01 ETH on Arbitrum. Some victims were walked through configuring an entire custom network — testnet credentials and all — before being routed to the mainnet deposit. When a &quot;mainnet bridge&quot; asks you to add a testnet, you are standing inside someone&apos;s soundstage.</p><p>This is <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/phishing-attack/">phishing</a> upgraded from faking a login page to faking a chain&apos;s entire view of the world.</p><h2 level="2" textAlign="left" id="h-the-verified-contract-trick">The verified-contract trick</h2><p>The deposit contract is <code>0xba9938c0b96a70e6479661b915e7e481fe435ab2</code>. Pull its code: a standard ERC-1967 <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/proxy-pattern/">proxy pattern</a>, implementation slot resolving to <code>0xe89f13c5ee4033b2d3cd76c9d6958efbfe26d3c2</code> — a fully <strong>Etherscan-verified </strong><code>OptimismPortal2</code>.</p><p>Pause on that. OptimismPortal2 is the real OP Stack portal contract — the contract family OP Mainnet, Base, and OP-Stack <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/layer-2/">Layer 2</a>s like GIWA use to receive deposits on Ethereum. The attacker deployed a proxy delegating to the genuine, verified implementation. A cautious victim who checked the contract before depositing saw a green checkmark and audited OP Stack source. Everything looked right. Two things were fatally wrong:</p><ol><li><p><strong>The storage belongs to the proxy&apos;s deployer.</strong> ETH sent to this contract sits in the attacker&apos;s proxy, not in any canonical portal.</p></li><li><p><strong>The L2 never hears about it.</strong> An OP Stack L2 derives deposits from events emitted by the <em>official</em> portal address. A lookalike emitting identical events changes nothing — no GIWA ledger ever credits these deposits. There is no &quot;the chain will still honor it&quot; edge case.</p></li></ol><p>And a third problem bigger than both: <strong>GIWA&apos;s mainnet does not exist.</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://docs.giwa.io/giwa-chain/en/get-started/connect-to-giwa">Official documentation</a> states it plainly: &quot;GIWA Mainnet is currently under development.&quot; The only public network is GIWA Sepolia, a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/testnet/">testnet</a>. Real mainnet bridge deposits were not possible for anyone, through any interface. The scam monetized a launch that hadn&apos;t happened.</p><h2 level="2" textAlign="left" id="h-the-fake-chain-listing-how-the-official-frontend-sold-the-scam">The fake-chain listing: how the official frontend sold the scam</h2><p>DYORSWAP is not a phishing brand, and — this is the part that rewrites the story — its official frontend was not bypassed either. DYORSWAP published a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/DYORSWAPDEX/status/2104120544178344112">security incident notice</a> on its verified X account (@DYORSWAPDEX, ~16.5K followers) at <strong>08:06:45 UTC on September 27</strong> that states, in effect, that the platform itself was the distribution channel:</p><blockquote><p>&quot;We have confirmed that the so-called GIWA Mainnet we previously identified was in fact a fake chain set up by scammers. The fake network used the correct GIWA Chain ID (9134), which made it appear legitimate during our initial verification. ... Unfortunately, significant losses have already occurred through the fraudulent bridge.&quot;</p></blockquote><p>Read that carefully. &quot;<strong>We previously identified</strong>&quot; — DYORSWAP had <em>listed</em> this &quot;GIWA Mainnet&quot; as a supported network. Victims were not duped into a lookalike site; they opened the real dyorswap.org, saw a GIWA Mainnet option presented alongside Arc, Base, and Arbitrum, and bridged through it. The notice also confirms the company is engaging security teams for on-chain tracing, preserving &quot;chat records, RPC information, bridge addresses, and on-chain transactions&quot; as evidence — and, notably, <strong>preparing to compensate affected users from its own treasury</strong>. That compensation commitment is effectively an acknowledgment that the official listing was the funnel.</p><p>The mechanism that made it work is depressingly simple: <strong>an EIP-155 chain ID is not an identity.</strong> Nothing in the protocol prevents anyone from running a chain that self-reports any chain ID they like. The real GIWA testnet runs 91342 (per GIWA&apos;s official docs); the fake mainnet reported &quot;the correct GIWA Chain ID&quot; per DYORSWAP&apos;s notice (which writes it as 9134 — either a truncation in the notice or the attacker&apos;s own choice; we record both rather than resolve it). If a multi-chain platform&apos;s listing verification stops at &quot;does the chain ID match the project&apos;s published one,&quot; then a fake chain with the right ID and an attacker-controlled RPC passes every check — and the platform then lends its domain, its UI, and its reputation to the scam. The user&apos;s own diligence was never given a chance: you cannot out-vet the platform that hosts the button.</p><p>This resolves the questions our earlier reconstruction left open — why deposits were plain Ethereum-mainnet transactions (the bridge flow&apos;s L1 leg: an OP-Stack-style <code>depositTransaction</code> on mainnet, with the fake chain&apos;s RPC free to &quot;confirm&quot; arrival on the L2 side that never existed), why the Sepolia touches appeared (users following the full network-add flow), and why the traffic curve looks like a coordinated push aimed at an official-frontend entry point. A chain-level supply-chain attack: not a fake website, not a fake contract — a fake <em>network</em>, wearing the right chain ID, listed on a real platform.</p><p>(Note: DYORSWAP&apos;s current public docs list sixteen supported chains and no GIWA — that is the post-incident state, after the fake listing was pulled. Our earlier reading of that page as &quot;GIWA was never supported&quot; was a snapshot fallacy: today&apos;s config cannot testify about yesterday&apos;s.)</p><p>The uncomfortable conclusion for every multi-chain platform: <strong>your chain-listing process is a security boundary.</strong> A chain ID match is a costume, not a credential. Hardening that boundary means verifying out-of-band with the chain&apos;s official channels (published RPC domains, genesis hash, explorer cross-checks — not the candidate chain&apos;s self-reported metadata), and treating any &quot;mainnet&quot; that appears before the project itself announces mainnet as presumptively fake. For users, the lesson lands differently: when the platform lists it, the platform vouches for it — so the failure you must insure against is no longer your own vigilance, it&apos;s the platform&apos;s.</p><h2 level="2" textAlign="left" id="h-the-deposit-curve-a-pump-not-a-search-result">The deposit curve: a pump, not a search result</h2><p>The full transfer history — 2,297 direct deposits, paged end to end — has a shape, and the shape tells you how victims arrived.</p><figure float="none" class="paragraph-figure paragraph-figure-none"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/be13adc72a7f95fff864f159929532fd5727ae0348a7a9fd3704bc7c7c834ef7.png" alt="Fake-portal deposits over time: green bars are ETH per 5-minute bucket, amber line is cumulative total" class="paragraph-editor-image"><figcaption>Fake-portal deposits over time: green bars are ETH per 5-minute bucket, amber line is cumulative total</figcaption></figure><figure float="none" class="paragraph-figure paragraph-figure-none"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/0f663f67c402132f3e72916500bb113fd33b6afc94d089248c3dcb0c80c7694f.png" alt="Hourly view: transfers (bars) and ETH (line). Red columns mark the three pump hours" class="paragraph-editor-image"><figcaption>Hourly view: transfers (bars) and ETH (line). Red columns mark the three pump hours</figcaption></figure><table class="paragraph-table"><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Hour (UTC, Sep 26–27)</p></th><th colspan="1" rowspan="1"><p>Deposits</p></th><th colspan="1" rowspan="1"><p>ETH</p></th></tr><tr><td colspan="1" rowspan="1"><p>Sep 26, 18:00–23:59</p></td><td colspan="1" rowspan="1"><p>16</p></td><td colspan="1" rowspan="1"><p>1.13</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sep 27, 00:00–01:59</p></td><td colspan="1" rowspan="1"><p>7</p></td><td colspan="1" rowspan="1"><p>3.42</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sep 27, 02:00</p></td><td colspan="1" rowspan="1"><p>32</p></td><td colspan="1" rowspan="1"><p>11.22</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Sep 27, 03:00</strong></p></td><td colspan="1" rowspan="1"><p><strong>748</strong></p></td><td colspan="1" rowspan="1"><p><strong>174.57</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Sep 27, 04:00</strong></p></td><td colspan="1" rowspan="1"><p><strong>685</strong></p></td><td colspan="1" rowspan="1"><p><strong>269.00</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Sep 27, 05:00</strong></p></td><td colspan="1" rowspan="1"><p><strong>445</strong></p></td><td colspan="1" rowspan="1"><p><strong>225.59</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Sep 27, 06:00</p></td><td colspan="1" rowspan="1"><p>234</p></td><td colspan="1" rowspan="1"><p>49.28</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sep 27, 07:00</p></td><td colspan="1" rowspan="1"><p>131</p></td><td colspan="1" rowspan="1"><p>20.30</p></td></tr></tbody></table><p>The first night is a trickle — one or two deposits an hour, the profile of stragglers finding a phishing link organically. Then at 02:00 the flow picks up, and from 03:00 to 05:59 the fake portal ingests <strong>1,878 transactions and 669 ETH in three hours</strong> — 82% of the entire haul. That is not SEO. That is not word of mouth. That is a distribution pump: a link pushed simultaneously through channels with reach, most plausibly Korean-language Telegram groups and social feeds, timed for midday Korea (03:00–06:00 UTC is noon–15:00 KST) when retail users are on their phones.</p><p>The deposit sizes confirm retail: median deposits are small, the largest single transfer in the entire dataset is 19 ETH, and 89 internal transfers worth 16.71 ETH arrived via just two intermediary contracts — consistent with routing contracts the fake frontend used to batch some deposits. This was a crowd-fleecing operation, priced for everyone.</p><p>We deliberately do not name any promoter accounts seen pushing DYORSWAP-style links in that window: distribution affiliates are often unaware of what they are distributing, and the operators are the story. The pattern itself — a burst of coordinated traffic aimed at a fake frontend during a pre-launch hype window — is what matters, and it will be reused.</p><h2 level="2" textAlign="left" id="h-the-exit-one-transfer-then-50-eth-blocks">The exit: one transfer, then 50-ETH blocks</h2><ul><li><p><strong>Sep 27, 07:29:59 UTC</strong> — An executor contract <code>0xccc2aecf5d24f0ea30cf81ec0dbec59f19ddcd10</code>, whose first-ever activity is this same minute, receives an <code>executeTransaction</code> call from the operator EOA. One internal transfer moves <strong>766.254042109579 ETH</strong> out of the fake portal to <code>0x04a9c8d8fee491411bda28b68ad80f0122fc4134</code> (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/tx/0x1f3c0a2375a6f043a4f2473f822398587d9af5225e4dc1275ca0eeda67dc7306">tx</a>) — a fresh address whose own first outgoing activity begins twelve minutes later. Block-level balance checks confirm the portal held exactly 766.254 ETH immediately before the sweep and ~0 after.</p></li><li><p><strong>07:41–07:53</strong> — The destination peels 251 ETH in 50-ETH blocks to <code>0x8c563fc543f6ecc2c8c09eb09d82798f7a7f3da4</code> (1 + 50 × 5).</p></li><li><p><strong>07:57–08:05</strong> — Another 301 ETH in the same 50-ETH blocks to <code>0xec160acd00d95ebbbe0394161101eb577ca96b60</code> (1 + 50 × 6).</p></li><li><p><strong>Afterward</strong> — <code>0xec16...6b60</code> had already forwarded 87 ETH onward in 15 transfers to a next-hop address by the time of our analysis; <code>0x8c56...3da4</code> was still untouched; the root <code>0x04a9...4134</code> still held 217.25 ETH. Standard layering — split, fan out, stage for whatever comes next (mixer, cross-chain hops, OTC).</p></li></ul><figure float="none" class="paragraph-figure paragraph-figure-none"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/03df1989fd708ad54b5aa70de625e9c42e8d6cd68e50648857ba35dcdf29de39.png" alt="Fund flow: 1,331 depositors → fake portal → single sweep → 50-ETH block layering" class="paragraph-editor-image"><figcaption>Fund flow: 1,331 depositors → fake portal → single sweep → 50-ETH block layering</figcaption></figure><p>The books balance to the wei: 771.18 ETH in, 766.25 swept, ~1.39 ETH residual plus gas. Nothing about the exit was improvised — the executor was deployed in the same minute it was used, the sweep destination was fresh, and the sub-wallet structure was waiting. This was an operation with a closing checklist, executed at 07:29 UTC the morning after the pump, one hour before the last stray deposit arrived at 08:04.</p><h2 level="2" textAlign="left" id="h-the-infrastructure-cluster">The infrastructure cluster</h2><p>Assembling the addresses from deployment records, storage slots, and funding flows:</p><ul><li><p><strong>Operator EOA</strong> <code>0x119e68b59c44291f76324c76377b776d0b4dd38c</code> — first mainnet activity September 26, 09:47 UTC, funded with 0.045 ETH of gas by <code>0x016606ac...49ee</code>, an address with history back to 2022. Nine hours later it deploys; nine hours after that the first victim deposits.</p></li><li><p><strong>Fake portal proxy</strong> <code>0xba99...5ab2</code> — ERC-1967, admin slot <code>0x91afa0ac...2472</code>, implementation = verified OptimismPortal2.</p></li><li><p><strong>Executor</strong> <code>0xccc2...cd10</code> — born and used in the same minute for the 766.25 ETH sweep.</p></li><li><p><strong>Sweep destination</strong> <code>0x04a9...4134</code> and sub-wallets <code>0x8c56...3da4</code>, <code>0xec16...6b60</code>.</p></li></ul><p>Five contracts/addresses and one EOA, purpose-built, used for roughly 22 hours of wall-clock time from first funding to final peel. The cluster fingerprint — a fresh EOA funded by an older address, a proxy wearing verified code, an executor deployed at moment of use, 50-ETH block layering — is the kind of signature that can be matched against future campaigns. We are keeping the full transfer dataset.</p><h2 level="2" textAlign="left" id="h-contract-review-why-every-check-passed">Contract review: why every check passed</h2><p>We ran a structured review of the deposit contract&apos;s architecture (AI-assisted, DeepSeek v4 Flash, against the on-chain state we pulled). Verdict and key findings:</p><blockquote><p><strong>[Critical] A verified </strong><code>OptimismPortal2</code><strong> implementation behind a lookalike ERC-1967 proxy, plus a fake chain environment, turned </strong><code>depositTransaction</code><strong> into unrecoverable ETH transfers. No OP-Stack derivation will ever honor them.</strong></p></blockquote><ul><li><p><strong>Proxy/implementation verification gap.</strong> The proxy holds the balance and storage; the admin slot (<code>0x91af...2472</code>) can replace the logic at any time. Verifying the implementation only proves its bytecode matches source — not that this proxy is canonical, not that it is immutable. <em>Detect: read the EIP-1967 impl/admin slots; compare all three addresses against official docs and L2Beat.</em></p></li><li><p><code>depositTransaction</code><strong> semantics abused.</strong> On a real portal it locks ETH and emits <code>TransactionDeposited</code>; L2 derivation only watches the canonical portal address. Here the proxy accepts ETH and may emit lookalike events, but no real L2 exists to listen. <em>Detect: treat an L1 transaction success as bridge credit only after confirmation on the official L2 explorer.</em></p></li><li><p><strong>Chain spoofing via custom RPC.</strong> Wallets trust RPC-provided chain metadata; the fake environment made &quot;GIWA&quot; appear live and Upbit-backed. <em>Detect: take RPC endpoints from official docs only; verify chainId and genesis hash independently.</em></p></li><li><p><strong>URL-parameter chain config.</strong> A multi-chain frontend driven by <code>?chainId=</code> becomes an untrusted config loader if it follows wallet context blindly: whoever controls the RPC controls chain identity, contract addresses, and what &quot;success&quot; looks like. <em>Detect (for dApp builders): hardcode an allowlist of chainId → RPC → canonical contracts; never derive bridge addresses from wallet-provided state.</em></p></li></ul><p>The full pattern is worth stating plainly: users were told to &quot;check the domain, check the contract.&quot; They did. Both checks passed. The attack lived one layer below both.</p><h2 level="2" textAlign="left" id="h-why-the-timing-was-the-weapon">Why the timing was the weapon</h2><p>Every element was scheduled around GIWA&apos;s visibility curve. The TCG integration put &quot;GIWA ecosystem&quot; into news feeds on September 18. The operator address woke up eight days later. For a mainnet that has not launched, the window between &quot;famous enough to search for&quot; and &quot;real infrastructure exists to compare against&quot; is not a gap — it is the entire opportunity. No canonical bridge address to diff against, no docs habit formed yet, and a population of users primed by a year of GIWA headlines to want in early.</p><p>Korea-specific context made it worse. Upbit&apos;s user base has been <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.upbit.com/service_center/notice?id=5317">repeatedly targeted</a> by impersonation phishing, and GIWA hype has already produced one official debunking — Upbit had to <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://economybloc.com/article/102528/">deny</a> a fake stablecoin-launch rumor in 2025. A market that is both excited and warning-fatigued is exactly where a fake &quot;early bridge&quot; converts best.</p><h2 level="2" textAlign="left" id="h-how-to-verify-a-real-bridge-in-order">How to verify a real bridge, in order</h2><ol><li><p><strong>Does the mainnet exist at all?</strong> Official docs only. If the project&apos;s own documentation says mainnet is in development — as GIWA&apos;s does today — every &quot;mainnet bridge,&quot; &quot;early deposit,&quot; and &quot;genesis liquidity&quot; offer is fiction. Not risky. Fiction.</p></li><li><p><strong>Take RPC endpoints from the official docs domain.</strong> Not from a chat group, an app&apos;s onboarding screen, or a helpful stranger. A fake RPC invalidates every subsequent check — it is the root of trust for everything your wallet displays.</p></li><li><p><strong>Diff the address, not the code.</strong> The canonical portal for any OP Stack L2 is a specific address published in official docs and tracked on L2Beat. A verified OptimismPortal2 at any other address proves only that the attacker copied good code.</p></li><li><p><strong>Treat testnet touches as red flags.</strong> A &quot;mainnet bridge&quot; flow that asks you to add a testnet or approve contracts on a network you didn&apos;t choose is staging a play for you.</p></li><li><p><strong>A chain ID is a costume, not a credential.</strong> Nothing stops an attacker&apos;s chain from self-reporting the same ID a real project publishes. Platforms and users verifying a &quot;new mainnet&quot; should demand out-of-band proof: the project&apos;s own announcement, official RPC domain, genesis hash — not the candidate chain&apos;s self-description. A &quot;mainnet&quot; that exists on a multi-chain app before the project announces mainnet is presumptively fake.</p></li><li><p><strong>Beware the traffic source.</strong> An interface that reached you through a group chat blast at lunchtime, rather than an official channel, is the distribution pattern of this exact scam. If a &quot;GIWA&quot; or pre-launch app link is circulating in a Telegram group, that circulation is the warning, not the social proof.</p></li><li><p><strong>If it already happened:</strong> stop using that wallet session, preserve URLs and transaction hashes, and follow the post-incident checklist in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/after-wallet-drainer-what-now/">what to do after a wallet drainer</a>.</p></li></ol><h2 level="2" textAlign="left" id="h-the-pattern-to-remember">The pattern to remember</h2><p>Strip away the Korean-market specifics and the structure is generic: <em>a pre-launch window, a famous name, a coordinated traffic pump, a self-consistent fake environment, and a real verified contract doing a job it was never authorized to do.</em> The recipe ports to any L2 before mainnet, any &quot;ecosystem partner&quot; announcement, any wallet that accepts custom RPCs.</p><p>The defense is unglamorous and absolute: <strong>before a mainnet exists, there is nothing to bridge to.</strong> Anyone who tells you otherwise is early to something — just not to the chain.</p><p><em>On-chain data queried via Etherscan APIs and block-level balance reads at the time of writing; balances and activity may have changed since. Addresses: fake portal proxy </em><code>0xba99...5ab2</code><em> · verified implementation </em><code>0xe89f...d3c2</code><em> · operator EOA </em><code>0x119e...d38c</code><em> · executor </em><code>0xccc2...cd10</code><em> · sweep destination </em><code>0x04a9...4134</code><em> · sub-wallets </em><code>0x8c56...3da4</code><em>, </em><code>0xec16...6b60</code><em>.</em></p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/giwa-fake-rpc-bridge-scam-explained/"><em>https://theonchaindiary.com/articles/giwa-fake-rpc-bridge-scam-explained/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/8cc8b7b1cc449600ebe41839b0d02efd8d567e5d8de653357ce5976a2598d680.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[ClickFix Scam Explained: How a Fake CAPTCHA Drains Crypto Wallets]]></title>
            <link>https://paragraph.com/@onchaindiary/clickfix-fake-captcha-scam-explained</link>
            <guid>Qdy2MmDgs5pVAHj7oDUw</guid>
            <pubDate>Fri, 02 Oct 2026 04:58:11 GMT</pubDate>
            <description><![CDATA[You are browsing the website of a local clinic or a plumbing company you have used before. The page blurs. A familiar box appears: "Verify you are human." You have done this a thousand times. But this verification does not want a click. It shows a string of text, tells you to copy it, press Win+R, paste it into the box that opens, and press Enter — all "to complete the verification." On a Mac, the instructions say to open Terminal, or in newer variants, Script Editor. The moment you press Ent...]]></description>
            <content:encoded><![CDATA[<p>You are browsing the website of a local clinic or a plumbing company you have used before. The page blurs. A familiar box appears: &quot;Verify you are human.&quot; You have done this a thousand times.</p><p>But this verification does not want a click. It shows a string of text, tells you to copy it, press Win+R, paste it into the box that opens, and press Enter — all &quot;to complete the verification.&quot; On a Mac, the instructions say to open Terminal, or in newer variants, Script Editor.</p><p>The moment you press Enter, you have installed malware on your own machine, with your own permissions, using your own hands. That is the whole trick. It is called ClickFix, and in 2026 it became one of the dominant ways attackers reach victims — including crypto users whose wallets are the end goal.</p><h2 level="2" textAlign="left" id="h-how-the-clickfix-trick-works-step-by-step">How the ClickFix trick works, step by step</h2><p>The mechanics matter less than the psychology, but the mechanics are worth seeing once:</p><ol><li><p><strong>You land on an infected page.</strong> Often this is a legitimate website that was compromised — not a shady domain. In the campaign Netskope documented starting in spring 2026, the infected sites were mostly small-business websites running WordPress or PrestaShop: clinics, trailer dealers, radiology centers, e-commerce shops. How they were initially compromised is still unknown.</p></li><li><p><strong>A fake CAPTCHA overlay appears</strong>, usually blurring the page behind it. Many variants copy the visual style of Cloudflare&apos;s verification pages, because that is what people are used to trusting.</p></li><li><p><strong>The prompt &quot;helpfully&quot; copies a command to your clipboard</strong> (or shows it in a copy box). It then instructs you to open the Windows Run dialog with Win+R, or PowerShell, or on macOS the Terminal — and paste.</p></li><li><p><strong>The pasted command is a downloader.</strong> It fetches the real payload from attacker infrastructure and executes it. Some variants immediately clean up after themselves: the Huntress-documented macOS chain deleted its temporary files, cleared the Terminal window, and wiped shell history so there was no visible trace of what ran.</p></li></ol><p>Every step after the fake CAPTCHA is performed by you, voluntarily. There is no attachment for an email scanner to flag, no downloaded file for antivirus to quarantine in many variants — LevelBlue&apos;s analysis of related campaigns found the chain executes almost entirely in memory. The attacker&apos;s insight is brutal: the most reliable way past every security product is to have the victim type the attack themselves.</p><h2 level="2" textAlign="left" id="h-the-2026-scale-5400-hacked-sites-and-an-on-chain-dead-drop">The 2026 scale: 5,400 hacked sites and an on-chain dead drop</h2><p>In <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.netskope.com/blog/malware-on-the-blockchain-an-ongoing-campaigns-new-webrtc-twist">research published on September 2, 2026</a>, Netskope Threat Labs described the infrastructure behind a massive ongoing ClickFix distribution network:</p><ul><li><p><strong>More than 5,400 compromised websites</strong> across more than <strong>2,200 organizations</strong>, worldwide, with no shared industry or region — mostly small businesses.</p></li><li><p>Several hundred of those sites were active on any given day, <strong>more than 300 each weekday</strong>; August peaked at <strong>536 distinct sites</strong> in a single day contacting the malicious endpoints.</p></li><li><p>The injected code on each site did not carry the payload itself. Instead it made a JSON-RPC <code>eth_call</code> to a <strong>smart contract on the BNB Smart Chain testnet</strong>, retrieved the next-stage script stored on-chain, and ran it in your browser.</p></li></ul><p>That last part deserves a pause, because it is the reason this campaign is so hard to kill. Storing attack code in a blockchain smart contract — a technique researchers call <strong>EtherHiding</strong>, first seen in the 2024 ClearFake fake-browser-update campaigns — turns the chain into a dead drop:</p><ul><li><p>The operator updates <strong>one contract</strong>, and every one of the 5,400 sites serves the new payload on the next page load. No need to rehack thousands of sites.</p></li><li><p>BSC testnet works like mainnet but its tokens are free from faucets, so running this distribution layer costs the attacker nothing.</p></li><li><p>There is no host or registrar that a takedown request can reach. The chain just keeps serving the code.</p></li></ul><p>For crypto users this is an uncomfortable inversion: the same property that makes blockchains censorship-resistant — nobody can take the data down — is being used as malware delivery infrastructure. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.bleepingcomputer.com/news/security/over-5-400-hacked-sites-serve-clickfix-payloads-stored-on-the-blockchain/">BleepingComputer&apos;s coverage of the campaign</a> walks through the same chain with the on-chain storage front and center.</p><p>Netskope also found a variant that skips the fake CAPTCHA entirely: the on-chain script opens an encrypted <strong>WebRTC data channel</strong> back to the attacker and runs whatever comes through it — a command-and-control channel that ordinary HTTP proxies do not inspect.</p><h2 level="2" textAlign="left" id="h-why-crypto-wallets-are-the-target">Why crypto wallets are the target</h2><p>ClickFix is not crypto-specific — it also delivers ransomware and general credential theft — but several of the observed payloads are aimed squarely at wallets. In <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.levelblue.com/blogs/spiderlabs-blog/fake-captcha-campaign-inside-a-multi-stage-stealer-assault">LevelBlue&apos;s multi-month analysis of fake-CAPTCHA delivery chains</a>, the final payload rotated between commodity infostealers (StealC, Lumma, Rhadamanthys, Vidar, Aura) and one payload that matters especially to anyone who sends transactions: <strong>a cryptocurrency clipboard hijacker</strong>.</p><p>Here is what that means in practice:</p><ul><li><p><strong>Infostealers</strong> sweep browser password stores, cookies, and saved wallet-extension data. If your seed phrase has ever lived in a file, a screenshot, a password manager note, or an browser extension vault on that machine, the stealer&apos;s file-pattern scan is designed to find it. Once the seed phrase is exfiltrated, the attacker does not need your computer anymore — they import the wallet themselves. Hardware wallets do not save you here: the theft happened at the moment the phrase passed through the infected machine, before the hardware wallet was ever involved.</p></li><li><p><strong>Clipboard hijackers</strong> watch your clipboard. You copy a wallet address, the malware swaps it for an attacker-controlled lookalike in the split second before you paste, and you send funds to the wrong address after &quot;carefully&quot; pasting it. This is the same endgame as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/address-poisoning-attacks-explained/">address poisoning</a>, executed by malware instead of by spoofed transactions in your history.</p></li><li><p><strong>Wallet drainers with a throttle.</strong> The most instructive case comes from <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.huntress.com/blog/mac-crypto-draining-malware">Huntress</a>, who responded to an incident where a Mac user pasted a ClickFix command into Terminal. The final payload was a Go-based stealer that harvested browser passwords and macOS Keychain data — and contained a function named <code>DRAIN</code> that could query a wallet&apos;s balance on-chain and redirect <strong>a configurable percentage</strong> of it (a <code>DRAIN_PCT</code> variable) to attacker-controlled addresses, across Bitcoin, Litecoin, Dogecoin, Ethereum, and XRP. Huntress noted it was the first wallet-draining malware they had analyzed capable of taking <em>less</em> than the full balance. Skimming a few percent at a time is a deliberate design: the victim does not notice, and the wallet keeps refilling.</p></li></ul><p>The full chain for that Mac case — the fake prompt, the fake password dialog, the persistence tricks, and the sanctioned bulletproof hoster behind it — is documented in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.huntress.com/blog/mac-crypto-draining-malware">Huntress&apos;s writeup</a>. The infrastructure traced to Aeza Group, a Russian bulletproof hosting provider sanctioned by the US in July 2025 and later jointly by the UK and Australia.</p><h2 level="2" textAlign="left" id="h-why-smart-people-fall-for-it">Why smart people fall for it</h2><p>The fake CAPTCHA works because it weaponizes three things at once:</p><ul><li><p><strong>Habit.</strong> You have verified your humanity thousands of times. Verification prompts no longer register as a security decision; they register as friction between you and the page.</p></li><li><p><strong>A legitimate context.</strong> The prompt appears on a real small-business website, or in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://guard.io/labs/captchageddon-unmasking-the-viral-evolution-of-the-clickfix-browser-based-threat">Guardio&apos;s documented cases</a>, inside phishing emails impersonating brands like Booking.com. Some campaigns even hosted the fake CAPTCHA flow on <code>script.google.com</code> — a real Google subdomain that security tools are reluctant to block.</p></li><li><p><strong>A plausible story.</strong> &quot;Press Win+R to verify&quot; sounds odd when you read it cold, but the dialog dresses it up as a step you simply have not done before. The command is pre-copied. Every micro-decision is made for you.</p></li></ul><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://guard.io/labs/captchageddon-unmasking-the-viral-evolution-of-the-clickfix-browser-based-threat">Guardio&apos;s research on the fake-CAPTCHA ecosystem</a> tracked how this format outcompeted and effectively replaced the older fake-browser-update scam: no download prompt, no scary warning screens, just a familiar check with one extra step. That is why ClickFix moved from a niche red-team trick to the initial access vector of choice for operations ranging from stealer delivery to ransomware.</p><h2 level="2" textAlign="left" id="h-how-to-protect-yourself">How to protect yourself</h2><p>The defense is behavioral, and it is binary:</p><ul><li><p><strong>A real CAPTCHA will never ask you to open Run, PowerShell, Terminal, or Script Editor.</strong> No legitimate verification needs you to paste a command. This single rule defeats every variant above, including future ones.</p></li><li><p><strong>Close the tab if a page tells you to paste a command.</strong> If you are worried the site is genuinely broken, revisit it later from a bookmark.</p></li><li><p><strong>Do not trust &quot;familiar site = safe site.&quot;</strong> The 5,400 sites in this campaign were legitimate businesses whose servers were compromised. Site reputation does not protect you from an injected script.</p></li><li><p><strong>If a pasted command has already run</strong>, treat the machine as compromised regardless of how fine it looks: the Huntress macOS chain deliberately erased its own traces. Move funds from any wallet whose seed phrase ever touched that machine — sweep to a freshly generated wallet on a clean device — and change passwords from a different computer. Our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/stolen-crypto-first-24-hours/">first-24-hours guide</a> covers the full triage sequence.</p></li><li><p><strong>Check where wallet addresses actually go.</strong> A hardware wallet&apos;s screen is the one place a clipboard hijacker cannot rewrite — verify the first and last characters of every address on the device itself, not on the computer.</p></li></ul><p>If you want the underlying concepts in more depth, see our explainers on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/clipboard-hijacking/">clipboard hijacking</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/phishing-attack/">phishing attacks</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/social-engineering/">social engineering</a>, and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/glossary/seed-phrase/">seed phrase security</a>. ClickFix is also a cousin of the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/signature-scam-explained/">signature scam</a> pattern — both attacks get you to authorize something yourself, which is exactly why they bypass technical defenses — and of the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/crypto-airdrop-scams-explained/">fake airdrop-claim drainers</a> that use fake websites instead of fake verification prompts.</p><p><em>This article is educational and not financial or security advice. Incident details are drawn from the linked first-party research from Netskope, Huntress, LevelBlue, and Guardio.</em></p><hr><p><em>Originally published at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com/articles/clickfix-fake-captcha-scam-explained/"><em>https://theonchaindiary.com/articles/clickfix-fake-captcha-scam-explained/</em></a><em>. More Web3 security guides and risk-scoring tools at </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://theonchaindiary.com"><em>Onchain Diary</em></a><em>.</em></p>]]></content:encoded>
            <author>onchaindiary@newsletter.paragraph.com (Onchain Diary)</author>
            <category>security</category>
            <category>crypto</category>
            <category>onchaindiary</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/7b5d13a4ef5ec5d29d5eabb8ecae007c873c08c8673450c6364607639467b5d9.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>