On-chain investigationMonad · BNB Chain · Robinhood Chain31 October 2026

A DNS hijack of 12 sites registered at Name.com drained $202K from 32 crypto wallets. Four in five of those dollars were taken on Monad

For one night, typing the right web address was not enough. We followed the drainer's payouts across six blockchains to count what people lost, and to find where the money went.

At a glance
For several hours on 31 October, 12 DeFi websites registered at Name.com led visitors to copies run by an attacker. The copies carried a wallet drainer. We traced $202,386 taken from 32 wallets on six chains between 01:00 and 05:33 UTC. Four in five of those dollars came from a single Kintsu staker on Monad, who lost $160,531. Two wallets lost 96% of the total. The attackers parked 2.64 million sMON in Kintsu's unstaking queue, where it still sat that evening. Every drain we traced used a victim's own signature.
$202K
Taken, valued when each drain happened
32
Wallets that lost $1 or more
81%
Of the money taken on Monad
$56.6K
Stolen stake in Kintsu's queue that evening
Key findingsEach line has its own share link
  1. $202K

    Taken from 32 crypto wallets on six chains in one night, after 12 DeFi sites registered at Name.com were hijacked.

  2. 79%

    Of everything taken came from one Kintsu staker on Monad, who lost $160,531.

  3. 96%

    Of all losses fell on two wallets. More than half of the victims lost under $100.

  4. 80 seconds

    One wallet was drained on Base, BNB Chain and Ethereum in that time. The kit sweeps every chain a wallet holds.

  5. $56.6K

    Of stolen Kintsu stake still sat in Kintsu's own unstaking queue that evening, unclaimed by the attackers.

  6. $138K

    The figure in early reports is close to the attackers' balances. Counting what each victim lost gives $202K.

01 · What happenedWhat happened in the Name.com DNS hijack

Late on Friday, 30 October, US time, some DeFi users opened apps they use every week. The pages looked normal. The address bar showed the right name. When they connected a wallet and signed, their money went to a stranger.

The apps belonged to 12 small crypto projects. They included Kintsu, a staking app on the Monad blockchain, and Flap, a site for launching memecoins on BNB Chain. All of their web addresses come from Name.com, a company that rents out domain names. For several hours those addresses led to copies of the sites, run by an attacker and loaded with a wallet drainer, a script that asks visitors to sign away their tokens.

The trick is called DNS hijacking. DNS is the internet's address book, and someone changed the entries for these sites. Bitquery reads every transfer on the chains these apps use, so we followed the drainer's payouts back to the people who paid. We traced $202K taken from 32 wallets on six chains. Four in five of those dollars came from a single Kintsu staker on Monad. Our count is higher than the $138K The Block reported that day, mostly because of stolen stake the attackers parked inside Kintsu, where it still sat that evening.

02 · The setupHow a website's address can be stolen

A web address is rented. A project registers its name with a company called a registrar, such as Name.com. The registrar keeps the record that says where the name should lead. Each time you type the name, your browser looks the record up through DNS.

Change the record and each visitor goes somewhere else, to a fake page that can look exactly like the real one. The address bar still shows the real name. It is the real name.

How a DNS hijack worksthe same web address, two destinations
THE SAME ADDRESS, TWO DIFFERENT DESTINATIONSA normal visitYou type the site's namethe address you always useThe domain record answersat the registrar, Name.comThe project's own serverset up by the teamThe real app loadsyou trade, stake, lend31 October, about 01:00 to 13:00 UTCYou type the same namenothing looks differentThe record was changedit now points elsewhereA server the attacker runsa copy of the real siteA drainer asks you to signmoney goes to the attacker
The record at the registrar decides which server a name leads to. The apps' smart contracts kept running as normal.

All 12 sites were registered at Name.com. They did not share a DNS provider. They used four: Vercel, NS1, Cloudflare and Name.com's own. The registrar is the one thing they have in common.

Nobody has said yet how the records were changed, though Vercel's domain service runs on Name.com and two of the projects pointed at Vercel. Kintsu said the hijack "happened on Vercel's end". Origami said it was waiting for Vercel and Name.com to explain the cause. Neither had done so when we checked.

03 · The nightThe night, drain by drain

The first drain we found landed at 01:00 UTC, on BNB Chain. Ten minutes later, Flap's site was seen serving the fake page. Flap warned its users about an hour after that.

Blockaid, a wallet security firm, warned about Flap and Kintsu at 02:54 UTC and tied the sites to a drainer kit sold as Step Drainer. Soon after, it named ten more sites serving the same kit.

The drains came in one nightevery drain we found, 00:00 to 06:00 UTC, 31 October
EVERY DRAIN WE FOUND, BY TIME AND CHAIN · CIRCLE SIZE = DOLLARS TAKEN01:10 Flap's site serves the fake page02:54 Blockaid warns about Flap, Kintsu03:51 A researcher flags Name.comMonadRobinhoodBNB ChainBaseEthereumArbitrum00:0001:0002:0003:0004:0005:0006:00Circle sizes:$100$1K$10K$100K
Each circle is one drain, sized by dollars taken. The biggest came on Monad at 01:56 UTC.

All but one of the drains we counted landed before 04:00 UTC. The largest came on Monad. The last we found came on Ethereum, after half past five. Name.com put 10 of the domains on hold around midday UTC, and by late afternoon the registry showed none of them on hold.

04 · The methodWhat the drainer asked people to sign

A drainer works through signatures. The fake page asks your wallet to approve something that looks routine, like a deposit or a claim, and that signature quietly hands over your tokens.

We saw four kinds of request. Some victims sent coins straight to a contract the attacker controls. Some approved a token so the attacker could pull it later. Some signed a batch that sent their tokens out in one go. One user signed a permission inside a lending app, which let the attacker take the deposits out on their behalf.

Then almost every payment went three ways. A collector, the attacker's own contract, split it between three wallets: 55%, 30% and 15%. Some drains skipped the collector and paid the three wallets directly, in the same shares. Two drains went to the 15% wallet first, a lending account and a set of trading-pool positions.

One drain, step by stepBNB Chain, 01:40 UTC, 31 October
ONE REAL DRAIN, BNB CHAIN, 31 OCTOBERVictim's wallet01:40:21 UTCpays 0.4833 BNB ($342)Collector contract0x2449…5bD501:40:26, five seconds later55% wallet 0.2658 BNB0x012f…D38630% wallet 0.1450 BNB0x7bf2…769515% wallet 0.0725 BNB0x5aff…8dBfAlmost every drain we counted ends in this same 55/30/15 split to the same three wallets.
Five seconds after the victim paid, the collector split the money three ways.

That split works like a fingerprint. It is how we tied the drains, on each chain, to this campaign.

05 · The lossesHow much the hijack took

We traced $202,386 taken from 32 wallets on six chains. Another 15 wallets lost less than a dollar each. Most of those were tiny deposits in Neverland, a lending app on Monad.

Most of the money was taken on Monaddollars taken on each chain
DOLLARS TAKEN ON EACH CHAIN · WALLETS THAT LOST $1 OR MORE$0$50K$100K$150KMonad$163,318 · 19 walletsRobinhood$35,920 · 5 walletsBNB Chain$2,386 · 7 walletsBase$427 · 1 walletEthereum$298 · 3 walletsArbitrum$38 · 1 wallet
Robinhood Chain comes second, and almost all of it is one account.

Most victims lost little. More than half lost under $100. Two wallets carry the total. One belonged to a Kintsu staker on Monad. The other used Morpho, a lending app, on Robinhood Chain. Together they lost 96% of the money.

Many small losses, two huge onesshare of victims against share of dollars, by size of loss
SHARE OF VICTIMS AGAINST SHARE OF DOLLARS, BY HOW MUCH EACH WALLET LOSTShare of the 32 walletsShare of the dollars0%25%50%75%100%Under $109 wallets, 28%$27, under 0.1%$10 to $1009 wallets, 28%$333, 0.2%$100 to $1,00010 wallets, 31%$4.2K, 2.1%$1,000 to $10,0002 wallets, 6%$3.2K, 1.6%$10,000 and up2 wallets, 6%$195K, 96.2%
More than half the victims lost under $100. Two wallets lost 96% of the money.
The 10 biggest losseswallet, dollars taken and the chains it was drained on
THE 10 BIGGEST LOSSES · WALLET AND THE CHAINS IT WAS DRAINED ON$0$50K$100K$150K0xa9ad…382e$160,531 Arbitrum + Monad0x5526…39ae$34,096 Robinhood0xaeaf…bc67$1,603 BNB Chain0xee8b…c51f$1,588 Robinhood0x13bc…04ce$959 Monad0x97c2…cc74$833 BNB Chain + Base + Ethereum0xc7cc…479d$783 Monad0x8c12…8d80$586 Monad0x4fa1…09d7$342 BNB Chain0xbeaf…b893$196 BNB Chain
Wallets are shown by address only. None of them is named here.

06 · MonadMonad: one staker, most of the money

Monad is a fast, young blockchain, and Kintsu is a staking app built on it. You stake MON, Monad's coin, and get sMON back, a token that earns staking rewards and can still be traded or used in other apps.

Just before 02:00 UTC, a single wallet signed away 4.79 million sMON, worth $106K at the time. It went through a spare address and was split three ways three seconds later. The owner was a regular Kintsu user. Since September they had staked more MON every few days.

Within three minutes the same wallet lost four Uniswap positions too. Those are the receipts you get when you add coins to a trading pool, and these held mostly WMON, a wrapped form of MON. The wallet was also made to create two new contracts, which carried off about 99,000 MON. It lost a little ETH on Arbitrum as well. In all, this one staker lost $160,531, four in five of everything the hijack took.

Kintsu stake and pool positions made up most of itwhat was taken on Monad, by kind of asset
WHAT WAS TAKEN ON MONAD, BY KIND OF ASSET$0$25K$50K$75K$100KKintsu stake (sMON)2 wallets$106,735Uniswap positions (WMON + gMON)1 wallet$52,754Plain MON1 wallet$1,964Neverland deposits31 wallets$1,865
The Neverland losses came from 31 wallets but add up to less than $2,000.

Over the next two hours the drainer worked through smaller accounts, and 31 wallets lost their Neverland deposits. Most were small.

A drain does not record which site its victim came from. The largest Monad losses were in Kintsu's own token, which fits kintsu.xyz. Kintsu told users to revoke anything they had signed since midnight UTC.

07 · Robinhood ChainRobinhood Chain: one Morpho account, $2K

Robinhood Chain is a new network for stock tokens. Morpho runs a lending app on it. Borrowers lock up tokens there to back their loans.

One user signed a Morpho permission. It let the attacker's contract manage their Morpho account. Just after 03:30 UTC, that contract pulled tokens out of the account and sent them to the attacker's 15% wallet. Twenty minutes later it came back. The second pull took more than the first. Unlike most drains, this money went to the 15% wallet whole, and that wallet later passed most of it to the other two.

Most of the haul was PONS, a token traded on the chain. There was also a token called The Index, and stock tokens for six companies, Nvidia and SpaceX among them. About an hour and a half later the attacker sold the PONS, The Index and the Nvidia tokens for 15.23 ETH.

One Morpho account, emptied and soldRobinhood Chain, 31 October (UTC)
ONE MORPHO USER ON ROBINHOOD CHAIN, 31 OCTOBER (UTC)03:32First pull from MorphoThe Index, stock tokens, PONS03:52Second pullmost of the PONS05:15–05:16Three tokens soldfor 15.23 ETH05:26–05:33Paid onto the 30% and 55% walletsWHAT EACH TOKEN SOLD FORPONS13.35 ETHThe Index1.30 ETHNVDA stock token0.59 ETHStock tokens for SpaceX, Apple, Microsoft, Alphabet and Coinbase were also taken, in small amounts, and not sold.
The sale raised 15.23 ETH, worth $34,096 at the time.

That one account makes up 87% of what the attackers took outside Monad. Morpho's code did what it was told. We have written about Morpho's dead lending markets before.

08 · The sweepOne wallet, three chains, 80 seconds

The kit checks every chain where a wallet holds money. One wallet was drained on Base, then on BNB Chain, then on Ethereum. The whole sweep took 80 seconds.

Three chains in 80 secondsone wallet's drains on Base, BNB Chain and Ethereum
ONE WALLET, THREE CHAINS · 0x97c2…cc74, 31 OCTOBER (UTC)01:23:3001:24:0001:24:3001:25:0001:25:30Base 01:23:510.1902 ETHBNB Chain 01:25:060.1743 BNBEthereum 01:25:110.1262 ETH80 seconds from the first chain to the last
The kit sweeps every chain where a wallet holds money.

Three of the victims we found were hit on more than one chain. Within half an hour, address-poisoning bots had copied some of the drains with look-alike fake tokens. They hope a victim will later copy a wrong address from their history. We have tracked those bots before, and we left their fake transfers out of the count.

09 · The walletsWho is behind the three wallets

Nobody has been named. The wallets have a past, though.

The two bigger wallets are new. On the chains we checked, they got nothing before the hijack. The 15% wallet is older. Since 22 September it has been paid by the same Robinhood Chain contract that later emptied the Morpho account. The keys that run the attacker's contracts on Ethereum and Robinhood Chain got their first funds on 20 September, ten minutes apart.

The 15% wallet also took a 20% share of two other drains that morning, with the rest going to a different wallet. Step Drainer is sold as a kit, The Block reported, citing researchers at LevelBlue: about $750 for the code, or $150 plus a 20% cut of each theft. A wallet that takes a fixed share from more than one drainer fits a seller's cut. The chain cannot show who holds it.

10 · The moneyWhere the stolen money went

By the evening of 31 October, none of the money had reached an exchange or a bridge that we could see. About half of it had been swapped into MON, Monad's coin.

About half of it was swapped into MONwhere the stolen money sat at 18:30 UTC, 31 October
WHERE THE STOLEN MONEY SAT AT 18:30 UTC, 31 OCTOBER · SHARE OF EVERYTHING TAKEN0%15%30%45%60%Swapped to MON or held as tokens, Monad52%Waiting in Kintsu's unstaking queue29%Sold for ETH, Robinhood Chain18%BNB and memecoins, BNB Chain0.4%Never forwarded, inside two collectors0.9%ETH on Base, Ethereum and Arbitrum0.4%
Shares of the $202,386 taken, each part valued when it was taken.

The Kintsu stake is the exception. Minutes after the big sMON drain, the 55% wallet asked Kintsu to unstake its share, 2.64 million sMON. Unstaking on Kintsu takes two steps, a request and then a claim, and the claim had not been made. That stake was worth about $56,600 that evening and was still in Kintsu's own contracts. If those contracts let the team hold or cancel a request, this money could still be stopped.

Two smaller payments, worth $1,764 in all, had not moved either. The attacker never split them. They sat in two collectors, one on BNB Chain and one on Robinhood Chain. The three wallets can be followed with the Bitquery MCP.

11 · The countWhy our number is higher than $138K

The Block put the haul at about $138K on the day. That is close to what the three wallets held that evening, about $139K by the monadscan explorer's count. Count what each victim lost, at the moment they lost it, and you get $202K.

From $138K to $202Kthe wallets' balances against what victims lost
WHY OUR COUNT IS HIGHER THAN THE WALLETS' BALANCES$0$50K$100K$150K$200K$139KWallet balancesthat evening+$57KKintsuunstaking queue+$1.8KNever forwarded,two collectors+$5.0KPrice moves,swap costs, other$202KOur count,at drain time
Balances come from the monadscan explorer that evening. Our count values each drain at the moment it happened.

The biggest difference is the Kintsu stake, which dropped out of the attackers' balances the moment it went into Kintsu's queue and is still stolen money. The rest comes from price changes and swap costs since the drains, and from receipt tokens the explorer does not price.

SourceClaimRecordVerdict
The BlockAbout $138,000 stolenThe wallets held $139,074 that evening. Victims lost $202,386 at the time of each drainClose to balances, low on losses
The BlockA BNB Chain Safe got 3.1 BNB from four walletsIt is the drainer's collector. It passed three payments on within seconds and still held 2.27 BNB that eveningA collector, not a safe
Kintsu, OrigamiThe hijack happened on Vercel's sideAll 12 domains are registered at Name.com, which Vercel's domain service runs on. They used four DNS providersFits, cause not confirmed

12 · The sitesThe 12 hijacked sites

Three of the sites run on Solana and one on Aptos. We could not count losses there. No drainer address for those chains has been published. The three wallets in this story are EVM addresses, which Solana and Aptos do not use. FluxBeam and StonkFun said they had no reports of users losing money. We looked at StonkFun's fee wallet in an earlier piece.

DomainProject's chainDNS providerIn our count
flap.shBNB ChainVercel DNSyes
kintsu.xyzMonadVercel DNSyes
pickle.financeEVM, several chainsVercel DNSyes
origami.financeEVMVercel DNSyes
longbow.cashnot confirmedVercel DNSif EVM or Monad
echelon.marketAptosVercel DNSno
apexdefi.xyznot confirmedNS1if EVM or Monad
shprd.financenot confirmedNS1if EVM or Monad
fluxbeam.xyzSolanaNS1no
stakepoint.appSolanaCloudflareno
stonkfun.xyzSolanaCloudflareno
supswap.xyznot confirmedName.comif EVM or Monad

13 · What to doIf you used one of these sites

We have traced several wallet drains this month, including the Predict.fun and Polymarket hacks. The advice is much the same.

Revoke any token approval you gave on 30 or 31 October, on every chain you use. A tool such as Revoke.cash lists them.

On Morpho, check which addresses can manage your account, and remove any you do not know. On Monad, check your Kintsu, Neverland and Uniswap positions. If one is gone, note the time and the transaction for the project's team.

Bookmark the apps you use. After an incident, check the project's own X account before you connect again. Wait for the all-clear. Ignore anyone who messages you offering to get your money back.

14 · The methodHow we traced the Name.com DNS hijack

We started from the three payout wallets The Block published and read each transfer into them on seven chains with Bitquery's data. Two of them, Optimism and Polygon, showed no drains. Each payment led back to a victim or to a collector, and each collector led to more victims.

Monad is not in our database yet. We read it from Monad's public network and the monadscan explorer instead. Each dollar figure uses the price at the time of the drain. You can buy the full history of the other chains as files on the Bitquery Data Store: the Ethereum, BNB Chain, Robinhood Chain, Base and Arbitrum datasets. For cases like this one, we also run crypto investigation services.

Limits on these findings

Transfers were read up to 18:30 UTC on 31 October. Anything later is not covered.

Totals count payments that reached the three wallets or a collector we found. A collector that took money and never paid out would be missed, so the totals are a floor.

Monad values use CoinGecko's MON price at the time of each drain. sMON and gMON are converted at the rates the attackers got when they sold them. A 10% move in MON's price moves the total by about $16,300.

Two BNB Chain memecoins had no price at drain time and use their 31 October afternoon price.

Losses on Solana and Aptos are not counted.

The Morpho collateral had no market price when it was pulled. It is valued at what the attacker sold it for, between one and two hours later; five small stock-token amounts that were not sold are left out.

Not counted: two USDC drains at 08:47 and 09:20 UTC on 31 October (about $169) that paid a different wallet 80% and the 15% wallet 20%, and a drain of under $100 on Base at 21:51 UTC on 30 October that paid the 15% wallet alone. Neither can be tied to the hijacked sites.

On Monad, the largest victim's sMON passed through a throwaway address before the split, and its plain MON left through two contracts the wallet was made to create. All of it is counted once, under that wallet.

A drain does not record which site its victim used. Losses are matched to sites by chain and token only.

15 · The recordThe addresses behind the hijack

0x012f89ff307568f8409bbe379ca92ed41bc4d386
0x7bf2037264efbff55bd52777772779c1d9e87695
0x5aff449b63c033df386af0c45384cd20c5918dbf
0x24497068ca4166ca32a04ae530ce00cf79755bd5
0x2323a3d19c6181b0e854209f405e6fdef6ad821d
0x40ea475e8b31fb8e86b9bd23b986d6e09cdadf7b
0x323719352ab49d3c8420f01e864fc115734ab956
0x7461a0c63caf04828778c6dd838bc9506b3c74dc
0xafb51dfeee427bf49b28ded45f8aac8881ccf448
0x33c529d75e195b27931a15285cb703575ff172163715c7c01785cc44d7c4e568
0x39b36904796f53ca801bbd393ba09b1169fe3b87462719a177efde2e30967379
0x984dd03a4219062c4e4c2db38d31535656b5cd91
0xa3227c5969757783154c60bf0bc1944180ed81b9
Kintsu sMON contract on Monad, holding the unstaking request. No Bitquery explorer page for Monad yet
Run it yourself

Follow the drainer's wallets in plain English

Every EVM transfer in this story comes from Bitquery's blockchain data. The Bitquery MCP server puts that data behind an AI assistant, so you can ask where a wallet's money went, or which wallets paid a collector, without writing a query. The full history is also sold as files on the Bitquery Data Store, as the Ethereum dataset and the BNB Chain dataset.

Watch the three payout wallets on every EVM chainList every wallet that paid a drainer's collectorTrace a drained wallet's money across chainsCheck an address against Bitquery's labels
Explore Bitquery MCP →Ethereum, BNB Chain, Robinhood Chain, Base and Arbitrum transfers, calls and events from Bitquery. Data read on 31 October 2026.
Legal disclaimer

This article is provided for informational and educational purposes only and reflects analysis of publicly available on-chain data as of the dates indicated. It does not constitute legal, financial, compliance, or investment advice, and nothing in it is a recommendation to buy, sell or hold any token or asset, or to use or avoid any website, wallet, registrar, protocol, exchange or service.

The findings describe transactions and balances observed on Monad, Robinhood Chain, BNB Chain, Base, Ethereum and Arbitrum on 30 and 31 October 2026. Attributions come from on-chain behaviour; they may be incomplete or incorrect and may be revised as more data becomes available.

References to Name.com, Vercel, Kintsu, Flap, Origami, Pickle Finance, FluxBeam, StonkFun, StakePoint, Echelon, SupSwap, Longbow, Shprd, ApexDeFi, Morpho, Neverland, Uniswap, Blockaid, LevelBlue, The Block or any other named project, company or service describe what the public record shows and what those parties have said in public. They are not statements about any party's intent, security practices, solvency or conduct, and nothing here asserts that any named party acted unlawfully or negligently. Victims are identified by wallet address only. The wallets that took the funds are described by their behaviour and attributed to nobody.

Nothing herein should be relied upon as a definitive determination of fact. Readers should conduct their own independent verification before taking any action. The authors and publisher accept no liability for any loss or damage arising from reliance on this material. All trademarks and company names are the property of their respective owners.

Reported by Gaurav Agarwal for Bitquery Research, with AI tools; every figure was checked against the raw data.

FAQ

Was Name.com hacked?

Nobody has confirmed that. All 12 sites were registered at Name.com, and their DNS records were changed. Two of the projects blamed Vercel, whose domain service runs on Name.com. Neither firm had said what went wrong when we checked.

How much was stolen in the Name.com DNS hijack?

We traced about $202K taken from 32 wallets on six chains, most of it on Monad. Losses on Solana and Aptos are not included.

Which sites were hijacked?

flap.sh, kintsu.xyz, pickle.finance, origami.finance, longbow.cash, echelon.market, apexdefi.xyz, shprd.finance, fluxbeam.xyz, stakepoint.app, stonkfun.xyz and supswap.xyz.

Is it safe to use these sites now?

By the afternoon of 31 October, none of the domains was on hold. Several projects said their sites were back. Check the project's own posts before you connect, and revoke any approval you gave on 30 or 31 October.

Can victims get their money back?

Most of it had been swapped and sat in the attackers' wallets that evening. About $56,600 of stolen Kintsu stake was still in Kintsu's unstaking queue. It is the best chance of recovery we can see.

What is DNS hijacking?

It is when someone changes the record that tells browsers where a website lives. Visitors type the right name and land on a page the attacker controls.

Run the next investigation in minutes

Ask any question of the blockchain. Bitquery's AI Investigations agent traces funds, attributes wallets, and writes auditable reports across every major chain. Prefer to do it yourself? Connect the Bitquery MCP server to your AI assistant, pull the raw datasets, or query the chain directly with the Bitquery API.