The post says the retrospective is still open. Leftover $PYTH for wallets that used the oracle. Limited time. One button to claim. That is how a free Pyth drop arrives in a feed, not as a transfer you can read, but as a countdown you are already late for.
The page is not unlocking a leftover allocation. Connect Wallet opens a session a drain script can spend. Approve that connection and the wallet can empty, often in seconds. Blockchain transfers do not come with an undo button. Free retrospective tokens are the costume. The wallet is the prize.
Pyth Network is a real oracle that publishes price feeds many apps already rely on, and a genuine retrospective claim window for $PYTH already ran its course. This article is not a review of that oracle and it is not an accusation against the project. The trap is the fake retrospective or portal claim page that clones the chrome and asks you to connect a wallet. That is the only door this write-up is about.
Overview
The $PYTH airdrop scam is a fake retrospective and portal claim pitch built to steal cryptocurrency. It presents a live, limited-time distribution of free $PYTH for people who used price feeds, held the ticker, missed an earlier round, or somehow still have a leftover share after the real window closed. The only action that matters is Connect Wallet. That click is not an eligibility check. It is the handoff to a drainer.
One current example in this wave is portal-pyth.network. Treat that address as a snapshot, not the story. The operators stand up throwaway portal and retrospective hosts, push them for a few days, then move. The next page will not keep the same name. The tell is the clone-and-connect pattern, not the hostname you happened to see first.
Once a wallet is connected, a malicious approval can move assets to an attacker-controlled address. The transfer is public, fast, and final. Closing the tab does not claw the coins back. Changing a browser password does not either. If you already tapped Connect, treat that wallet as burned and work the recovery steps below before you do anything else.
Free $PYTH is the bait, not a balance
Read the headline the way a tired person reads it between two other tabs. Claim your $PYTH retrospective. Portal drop is live. Check oracle history after connect. Limited window for leftover allocations. Do not miss a closed-season share. Every line is doing the same job. It makes a stranger’s button feel like a reward you already earned by using price feeds or holding the ticker.
A real allocation, when one exists, is boring on purpose. A published claim path on a site the project has used for months. A snapshot you can match to on-chain activity you already made. A window that lasts long enough that you do not have to panic-click from a reply. Nobody who is actually sending you tokens needs you to treat a four-hour clock as a forfeiture after the official season already ended.
These clone pages lean on the opposite feeling. Exclusive. Live. Closing. Eligible if you connect. Leftover share waiting. Free is the word that shuts down the part of your brain that asks who signed the contract. Free also hides the price. You are not paying in dollars. You are paying with whatever is already sitting in the wallet you connect, including stables, liquid tokens, and any $PYTH you already earned the honest way.
That is why the pitch works on people who would never wire $500 to a stranger. Connecting a wallet feels like opening an oracle dashboard you already trust, not like signing a check. The page never has to name a dollar amount. It only has to make Connect Wallet feel like loading a claim. The drainer names the amount later, on-chain, after the permission is already granted.
Oracle culture makes that claim feel urgent. Apps already pull Pyth feeds without asking the end user to stare at a logo. Gas, finality, feed updates. Products that quietly sit on top of a real price layer train users to tap Connect without thinking they just opened a spending door. The clone spends that training. It does not need you to discover a new token. It needs you to believe that waiting is how you miss a retrospective share you already earned.
Holders of real $PYTH are a second audience. If you already claimed in a genuine round, a leftover portal distribution sounds like housekeeping. Unclaimed supply. A second window. A page that will send what you missed after the official period closed. That story is useful to a thief because it targets people who already proved they will connect a wallet to collect a drop, and who already keep value next to oracle-related balances.
The claim button is the handoff
Connect Wallet does not open an oracle. Claim $PYTH does not mint anything. Check retrospective history does not read a ledger. Those labels exist so the next window looks like a product step instead of a permission request. You have used Connect on real DeFi screens. The muscle memory is the exploit.
The button is doing one job. It opens a wallet connection. After that, the page can ask for a signature, a token approval, a permit, or a spending permission dressed as a portal check. None of those actions drops a leftover allocation into your balance. All of them can let a script spend what you already hold.
Do not open a claim page to just look. On a phone the address bar is easy to ignore, and looking is how a Claim tap becomes a connected wallet. If a friend forwarded the link, tell them the same thing. The page is the attack, not a preview of an attack. A fake retrospective is still a drain even when the art looks like the portal you used last season.
A second, quieter control often sits next to the filled button. Docs. Feeds. Portal. Those labels are layout. They make Connect Wallet look like the serious choice, the way a real protocol site has a docs link beside a start button. Clicking them does not make the host official. The official part was supposed to exist before anyone asked you to connect.
Retrospective language is doing extra sales work. A retrospective implies a cleanup of something that already happened, not a giveaway invented this morning. If you used apps that pull real price feeds, the clone does not need to invent a brand. It only needs to invent a leftover claim sitting on top of that habit. Portal language does the same job. It sounds like finishing a season, not collecting a coupon, which is why people who would skip a meme claim will still tap a retrospective button.
Connect Wallet is the drain
The connection window looks like the one you have seen on real oracle and DeFi sites, which is the point. Familiar names lower the pulse. Your usual wallet is in the list so you do not bounce. Choosing it is not a verification of a $PYTH drop. It is you handing the page a live session with the account that holds your coins, and often the account that already holds real $PYTH.
Hardware wallets are not magic here. A device still signs what you tell it to sign. If the prompt is a drain approval dressed as a retrospective check, the device will do the harm you authorize. The metal box protects the key from malware on the computer. It does not protect you from saying yes to the wrong program.
People stall at this step because the names look right. Wallet connection flows are everywhere in 2026, and DeFi users already click through them to swap, stake, or claim on a real dashboard. The presence of a known brand in a list is not the same as that brand endorsing the site. Your wallet vendor did not send you a leftover $PYTH portal. The claim page borrowed the logo the way a fake invoice borrows a bank’s.
If the dialog asks for a signature, a token approval, a permit, or an unlimited spend, that is not a gasless hello. That is the drain being armed. Decline it. Disconnect. Leave. There is no allocation waiting on the other side of a yes, and there is no retrospective share that needs your seed or your spend permission to exist.
The hostname will change
These claim pages live on throwaway hosts because throwaway hosts are cheap to replace. A pages.dev name, a lookalike domain, a hyphenated portal name, a fresh subdomain, a paste of the same pitch under a new TLD. When one address gets reported, the next one is already in a draft folder. Bookmarking yesterday’s host does not keep you safe tomorrow.
That is why this write-up is not a tour of one landing page. The operators will change the purple accent, the retrospective copy, the claim badge, and the URL. They will not change the funnel. Free $PYTH, or a cousin allocation story, for people who might have oracle history. A Connect Wallet button. A permission that can empty the account.
Learn the pattern, not the spelling. If a stranger’s page needs your wallet to check eligibility for a limited $PYTH drop after the real window closed, you are not late to a portal. You are early to a drain. The next host will hope you only remember the old URL and not the sequence that emptied the last wallet.
A ticker on a price site does not baptize a random claim host. If you want the real project site, type pyth.network yourself. Official channels do not hide on a disposable portal URL built for a one-week costume. People who already used real price feeds still should not connect a wallet to a page that showed up in a reply, a DM, or an ad.
How The Scam Works
The $PYTH drain is a short funnel. A social or ad lure. A retrospective page that looks like the oracle portal you already trust. A wallet connect that feels like logging in. A drainer that spends the approval. Each stage exists to make the next one feel small.
The lure rides a real oracle
These pages do not wait for you to type Pyth into a search bar. They arrive as a post, a reply, a quote tweet, a Telegram forward, a group-chat alpha ping, or a paid ad that looks like coverage. The account may be stolen. It may be brand new with an oracle avatar and a few thousand fake followers. It may be a compromised influencer handle posting a claim link under a thread about price feeds, $PYTH holders, or some other allocation rumor.
The Federal Trade Commission has already mapped that habit in broader crypto fraud. In its analysis of reports from January 2021 through March 2022, consumers reported losing over $1 billion in cryptocurrency to scams, about one out of every four dollars reported lost to fraud, or roughly 25% of that pool.
Nearly half of the people who reported a crypto-related scam said it started with an ad, post, or message on social media. A fake $PYTH retrospective is one more costume on that road, not a new invention.
The copy in those posts is always the same shape even when the host changes. Live now. Last hours. Check if you qualified. Claim your leftover $PYTH before the snapshot. A screenshot of a dark portal site and a purple button. You are not being invited to read an oracle explainer. You are being invited to tap before someone else does.
Rogue ads and pop-ups do the same work for people who never open crypto Twitter. A shady download site, a fake your wallet is eligible interstitial, a push notification from a page you should never have allowed to alert you. The destination is still a claim page. The story is still that a $PYTH drop is live and you are late, even when the real retrospective already closed.
Group chats make the lure travel farther than the first account. One person pastes a link with this is live. The next person trusts the first person more than the URL. By the time the fifth forward lands, nobody remembers who found it. That is by design. The portal page does not need a famous domain if it can borrow a friend’s name, or the look of an oracle the whole chat already respects.
The lure is stronger because a real oracle sits under other products. You can trade inside an app that pulls Pyth feeds and never stare at a Pyth wordmark. That hidden plumbing is honest when the app is real. It is poison when a clone says your hidden history just unlocked a leftover share. People who never thought they were waiting for a drop still feel late.
The page copies a portal, not a project
When the link lands, the visitor sees a claim dashboard, not a warning. A live badge. A ticker. A countdown feeling even when no clock is printed. Large type that says claim your $PYTH retrospective. Under it, the limited-time line for leftover allocations and a portal share. A filled Connect Wallet button where the eye already expects a claim screen.
What is missing is the boring proof a real allocation would drown you in. No published snapshot you can match to a known on-chain record. No official verification from a channel you already follow. No rules for who is eligible and who is not, beyond connect to see. The page asks you to believe the drop is live because the badge says live and the chrome looks like the portal you used last season.
That emptiness is easy to miss after the word free, and easier still after a closed window. People who missed a real claim season are trained to fear permanent forfeiture. The page spends that fear. It does not need a white paper you would actually read. It needs enough dark panels and feed marks to survive a three-second glance on a phone. Three seconds is enough to tap Connect. Three seconds is not enough to notice there is no checker behind the costume.
Social icons sit where a real community would sit. That is not verification. Icons are cheap. A Telegram logo does not mean the project has a Telegram. An X logo does not mean the account in the post is official. If you follow those icons, you often land on a second lure, not on a company.
The same costume works for other oracle and DeFi stories. Swap the $PYTH retrospective for another protocol skin and the funnel still stands. This article stays on Pyth because that is the bait in front of you. The drain class is older than this clone and it will outlive this host. The real oracle is not the operator. The clones are.
Claim is not a leftover mint
On a real distribution, eligibility is already sitting in on-chain history. Activity recorded. Apps used. Time spent around a published season. You do not need a stranger’s page to invent that record. On these pages, check retrospective history means start the wallet session. The phrase is doing sales work. It sounds like you are opening a statement that is already yours.
Nothing is already yours on that host. There is no allocation waiting behind the button. There is no snapshot of your address from last season living on that domain. There is no program quietly holding $PYTH until you connect. The page needs you to believe that sentence so you do not read the permission the wallet is about to show.
Some visitors hesitate and look for a check eligibility step, hoping the site will say they do not qualify and leave them alone. That step is still a connect. Eligibility is the excuse. The wallet is the target. A page that cannot see your address without a connection is not checking a list. It is asking for the keys to the list.
Real eligibility for a genuine drop, when it is discussed at all, is on-chain activity you can already see. It is not a connect-to-check page that showed up in a reply after the official window closed. An oracle does not need you to arm a spender so it can count your leftover share.
If a later prompt says the claim failed, or that you need to unlock the drop, or that gas must be paid from a token you do not hold, stop. Those lines are second bites. They exist to push another signature after the first one already opened the door. Close the tab. Do not try to finish a check that was never a check.
A closed real window can make the hesitation worse. People who already missed a genuine claim do not want to miss a second chance. The clone spends that regret. It does not need you to invent new activity. It needs the wallet that might have been eligible once to say yes one more time.
Feed usage is a favorite excuse. The page pretends it will score your oracle history after connect, the way a real dashboard might show activity. Scoring is a story. The connect is the product. If the only way to see a number is to approve a stranger, you are not viewing a statement. You are funding one.
The connect dialog is the permission
Tap Connect and the wallet picker appears. It is the same family of connection UI used across legitimate apps, which is why it feels safe. You have connected wallets to real sites before. The habit is useful on a project you already trust. It is dangerous on a page that showed up this morning with a leftover $PYTH story.
The list is often long on purpose. Ethereum wallets, Solana wallets, hardware wallets, mobile wallets. A genuine retrospective for one season does not need to greet every ecosystem in one breath. A drainer does. The operator does not care which chain you use. The operator cares that you approve something.
Read the prompt the way you would read a bank transfer. What is being spent. Which contract is asking. Whether the permission is unlimited. Whether the action is a simple sign-in or a token approval. If you cannot answer those questions in one sentence, the answer is no. A closed $PYTH window will not reopen while you decline.
People lose coins here because the window feels like a login wall. Login walls are supposed to be boring. Drain approvals are not. A site that needs a signature to prove you own the wallet can also use that signature to move the wallet. Treat every prompt as a spending decision, even when the button says Claim $PYTH.
The drainer is the product
After the connection, the page’s only remaining job is to empty the wallet. Drainers are built for this exact moment. They look for liquid balances, approvals they can spend, and assets they can transfer in one burst. The user still thinks they are waiting for a retrospective to populate. The attacker is already broadcasting.
Speed is part of the design. Seconds, not hours. If you watch the wallet after a connect and see outbound transactions you did not build, that is not a glitch in the airdrop. That is the theft completing. Native coin, stablecoins, $PYTH you already held, NFTs with open approvals, whatever the script can reach. The mix depends on what you held, not on what the portal pretended to send.
Because confirmations are irreversible, the operator does not need you to stay on the page. You can close the laptop. You can reboot. You can delete the site from history. The chain does not care. The new owner of those coins is the address the drainer specified, and there is no Pyth support desk that can freeze it for a clone you visited.
Some drains leave a little dust so the wallet still looks alive. That leftover is not kindness. It is a hook for a second sweep, or for a recovery pitch that asks you to send more to unlock the rest. Do not feed the old address. Do not treat leftover dust as proof the first transfer was a mistake.
This is the same family of fake airdrop drains that has already worn other tickers and other throwaway hosts. The costume changes. The connect-and-empty step does not. A $PYTH retrospective clone is not a new kind of crime. It is an oracle sticker on a funnel that already works, which is why the recovery advice below is the same advice you should follow for any wallet you connected to a stranger’s claim button.
The coins do not come back
There is no disputes team on a public chain. There is no chargeback. There is no Pyth support that can reverse a confirmed transfer sent by a clone you approved. Once the network includes the transaction, the coins belong to the new address. Closing the claim tab after that moment is hygiene, not recovery.
That finality is why the lure has to be free. If the page asked you to wire $2,000 to a stranger, more people would stop. If it asks you to claim leftover $PYTH, the cost is hidden until the explorer updates. The $ figure appears after the permission, not before it. By then the argument is over.
Exchanges can sometimes freeze funds that later land in a custodial account they control. That is a maybe, not a plan. It depends on speed, on the path the coins took, and on whether anyone can see that path from the hashes. It does not depend on a helper in DMs who wants a seed phrase. Save the transaction IDs first. Then file the reports. Then stop talking to strangers about the wallet.
A second crew hunts the same wallet
After a drain, the DMs arrive fast. People offering to trace the funds for a small fee. People who need you to share the seed so they can deploy a recovery contract. People who want a USDT prepayment to unlock a case ID. People posing as exchange staff, law firms, or Pyth support.
They are hunting the same wallet a second time. A drained address is a lead. It proves you will click, you held enough to steal, and you are now desperate. The recovery pitch is cheaper to run than the first claim page because you already did the hard part. You already connected once.
Nobody legitimate needs your recovery phrase. Nobody legitimate needs you to send more crypto to get the first batch back. A real investigator asks for transaction hashes you already have, through a form you typed yourself, not through a reply under the $PYTH post. Block the helpers. Do not argue. The report you file is the only official path.
What To Do If You Have Fallen Victim to This Scam
If you connected a wallet to a fake $PYTH claim page, assume the attacker can still spend what is left. Work in this order. Do not send more coins to the same address to unlock a retrospective. Do not paste a seed phrase into any site that offers to reverse the drain. Those are second scams that feed on the first.
- Disconnect and close the tab. In the wallet app, disconnect the site session. Revoke the connected dapp if the app has a connected-sites list. Then close the browser tab. This does not move coins back. It stops you from signing a second approval while you are still rattled. Stay off the claim page. Do not reload it to see if the leftover $PYTH went through.
- Create a brand-new wallet. Generate a fresh recovery phrase on a device you trust, write it down offline, and never type those words into a website. The old wallet’s seed is still yours, but any dapp it approved may still be able to pull from the old address. A new wallet means a new seed. Do not import the compromised phrase into a clean app and call that a migration. Importing copies the risk.
- Revoke approvals on the old wallet. Use the official explorer tools for the chains that wallet used. On Ethereum-style networks, open the address in a block explorer and review token approvals. Revoke anything you do not recognize, anything granted today, and anything tied to a claim, portal, or airdrop spender. On Solana, revoke unknown token delegations in the wallet or a reputable revoke tool you typed yourself, not a link from a helper in DMs. Hardware wallet users should still revoke. The device does not cancel an approval you already signed.
- Move remaining assets to the new wallet. After you revoke what you can, send what is left to the new address. Do this while you can. Drainers sometimes leave dust or a second sweep for later. Do not leave a little bit on the old address as a test. If an NFT or a staked position cannot move until an unlock date, document it, revoke related spenders, and treat that position as still at risk until it can be migrated. Never fund the old wallet again.
- Preserve transaction IDs and screenshots. Copy every outbound hash from the time of the connect. Save the from address, the to address, the token, and the time. Screenshot the claim page URL only if you already visited it. Do not return to capture a prettier picture. Export the wallet activity if the app allows it. Those records are what an exchange, an investigator, or a report form can actually use. A vibe that Pyth stole my coins is not a record, and the real project did not run the clone.
- Report the theft. File at the FTC fraud report form if you are in the United States, and at the FBI Internet Crime Complaint Center. Add the TXIDs. If the coins passed through a centralized exchange you can identify from the explorer, use that exchange’s theft-report path with the same hashes. Tell your wallet vendor through its official support page, not through a reply guy under the $PYTH post. Local police reports help some insurance and tax records even when the coins cannot be frozen.
- Ignore recovery agents. After a drain, the DMs arrive fast. People offering to trace the funds for a small fee. People who need you to share the seed so they can deploy a recovery contract. People who want a USDT prepayment to unlock a case ID. People posing as exchange staff, law firms, or Pyth support. They are hunting the same wallet a second time. Nobody legitimate needs your recovery phrase. Nobody legitimate needs you to send more crypto to get the first batch back. Block them. Do not argue. The report you already filed is the only official path.
If you signed nothing and only opened the page, disconnect any preview connection the wallet created and leave it there. Curiosity is not a crime, but it is how the next tap happens. If you shared the link in a group chat, go back and warn the thread. One quiet edit is worth more than a later apology.
Tax and recordkeeping are unglamorous and still worth a calendar reminder. Stolen crypto is still a transaction history you may need. Keep the TXIDs with the date you connected. If you use an accountant, send that packet once rather than rebuilding it from memory in April. Do not pay anyone who promises to turn the hashes into a refund.
Going forward, keep airdrop hunting off the wallet that holds your rent. A burner address with a tiny balance can survive a bad click. The main wallet cannot. Official claims, when they are real, will wait for you on a site you already use. They will not need you to connect a stranger’s page because a leftover $PYTH retrospective said the window was still open after the real one closed.
The Bottom Line
The $PYTH retrospective on a throwaway claim page is not a live oracle drop. It is a wallet drain wearing portal chrome, a live badge, and a Connect Wallet button. Free leftover tokens for people who used price feeds is the story. Connect Wallet is the product. Once that connection is approved, the coins can leave in seconds, and the chain will not give them back.
A real oracle and a finished claim season do not make a random portal host official. Official claims do not need you to panic-click Claim $PYTH on a disposable URL after the window already ended. The hostname will rotate. The pattern will not. If you already connected, disconnect, open a new seed, revoke, move what is left, save the hashes, file the reports, and hang up on anyone selling a recovery. The leftover drop was never yours. The wallet still can be.
