backpackwallet.org is a Solana impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (76/100). Registrar: Eranet International. Status: Last known active. Hosting: Oracle Corporation. PhishDestroy sent 1 abuse report. VirusTotal: 1/92 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 1. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
PhishDestroy’s automated assessment classified the domain as an impersonation phishing page. The recorded page title "Backpack Wallet: Crypto Exchange | Solana, Ethereum & BTC" shows the site pretends to be the Backpack Wallet service. PhishDestroy first observed the domain on 2026-10-23, 38 days after its registration on 2026-09-15. An HTTP 200 response was recorded on that date.
How the scam works
Impersonation phishing sites copy the branding and wording of legitimate cryptocurrency wallets to lure users into entering seed phrases, private keys, or approving malicious extensions. When such credentials are submitted, attackers can gain full control of the victim’s wallet and drain funds.
Evidence
VirusTotal flagged the domain as malicious on 2026-10-22, reporting one detection (Gridinsoft) out of 92 engines. Google Safe Browsing returned no warning on 2026-10-23. urlscan’s machine‑learning engine assigned a malicious score of 97 on 2026-10-23, although its overall verdict was clean. External blocklists MetaMask and SEAL listed the domain on 2026-10-23, and OTX recorded three related pulses on the same day. PhishDestroy’s internal blocklist also marked the domain as malicious on 2026-10-23.
Infrastructure
The domain was registered with Eranet International Limited on 2026-09-15 and uses the nameservers sns00011.webhostbox.net and sns00012.webhostbox.net. The recorded IP address was 66.116.209.243, belonging to an Oracle‑owned network in the United States. The site presented a TLS 1.3 certificate from Let’s Encrypt, valid until 2026-12-14.
What to do
Anyone who entered a seed phrase, private key, or approved a wallet extension on this site should treat those credentials as compromised, create a new wallet, and change any reused passwords. Defenders should block backpackwallet.org at the network perimeter, monitor DNS queries for the domain, and add it to internal phishing blocklists.
No. PhishDestroy classifies backpackwallet.org as a Solana impersonation page (risk: critical, 76/100); it was first detected on 2026-10-23. VirusTotal: 1/92 engines flag it. Treat the site as unsafe.
Is backpackwallet.org safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on backpackwallet.org. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used backpackwallet.org?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Issued by Let's Encrypt / YR2· stored validity ends in 51 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
66.116.209.243
Network ASN
AS31898
Organization
Oracle Corporation
Observed location
Phoenix, US
Server header
nginx/1.29.8
Nameservers 2
sns00011.webhostbox.net
sns00012.webhostbox.net
Mail routing 1 MX record
mail.backpackwallet.orgpriority 0
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR2
Valid from
2026-09-15 12:51:13
Valid until
2026-12-14 12:51:12
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint77292a4d455ef7630c21bce350321bdb9d9f95438c2da6aebe700ea8157af709Certificate names · 2 SANs
*.backpackwallet.org
backpackwallet.org
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-23 11:23:13 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-23 11:23:13 UTClast content: 2026-10-23 11:23:13 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains2
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
app.backpackwallet.orgDomain record
www.app.backpackwallet.orgDomain record
The original observation time is not recorded for these hostnames.
Technologies · 2 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · backpackwallet.org
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same automated brand label: Solana8
Reports with the same collector label. A shared label does not establish impersonation or common ownership. View matching reports →
6 evidence signal groups linked1 stored notification recordsLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including backpackwallet.org)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
