packscan.co is an Ethereum impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (95/100). Registrar: NameCheap. Status: Last known active. Hosting: Cogent Communications. PhishDestroy sent 1 abuse report. VirusTotal: 3/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 3. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
PhishDestroy classified packscan.co as a suspicious domain based on VirusTotal detections recorded on 2026-10-21. The site was first seen by PhishDestroy on 2026-10-23 returning HTTP 200 and the recorded page title “New Private Tab”.
How the scam works
The listing reflects a generic phishing risk where attackers host pages that imitate legitimate services to trick users into revealing credentials or authorizing transactions. No specific credential‑harvesting form, wallet‑approval prompt, or malware was observed on this domain, so the assessment does not confirm a particular technique beyond the broader phishing category.
Evidence
VirusTotal (analysis 2026-10-21) reported three detections: two malicious (alphaMountain.ai, CRDF) and one suspicious (Ermes) out of 92 engines. Google Safe Browsing checked on 2026-10-23 reported no flag. urlscan.io captured the site on 2026-10-14 with a clean verdict, while a later capture on 2026-10-23 flagged it as malicious by its ML engine (score 97) though the overall verdict remained non‑malicious. External blocklists MetaMask, ScamSniffer and SEAL all list the domain, and Spamhaus DBL categorised it as phishing on 2026-10-23. OTX recorded three pulses mentioning packscan.co, and PhishDestroy’s internal blocklist marks the domain as blocked.
Infrastructure
The domain was registered with NameCheap on 2026-09-28, 25 days before first detection. The recorded IP address 170.75.160.175 belongs to Cogent Communications in Canada. TLS was provided by Let’s Encrypt, valid from 2026-09-28 to 2026-12-27. DNS records include an A record, multiple MX records via registrar‑forward servers, and NS records at dns1.registrar-servers.com and dns2.registrar-servers.com; DNSSEC was not enabled.
What to do
Visitors should avoid entering any credentials or personal information on packscan.co; if they have already done so, they should change related passwords and monitor accounts for suspicious activity. Defenders should block network traffic to packscan.co and log any connections to the recorded IP 170.75.160.175, applying the blocklist entry to this exact domain only.
No. PhishDestroy classifies packscan.co as an Ethereum impersonation page (risk: critical, 95/100); it was first detected on 2026-10-23. VirusTotal: 3/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
Is packscan.co safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on packscan.co. 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 packscan.co?
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.
DOM Analysisanalyzed Oct 23, 2026score 35/1007 brand signals
Submitted URLhttps://packscan.co/
Favicon Hash
Case ID
Observed page title
New Private Tab
Automated brand references
AcrossBackpackBaseDiscordEthereumSolanaTelegram
TLS Certificate
Issued by Let's Encrypt / YR1· stored validity ends in 64 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
170.75.160.175
Network ASN
AS174
Organization
Cogent Communications
Observed location
Toronto, CA
Server header
nginx
Nameservers 2
dns1.registrar-servers.com
dns2.registrar-servers.com
Mail routing 5 MX records
eforward4.registrar-servers.compriority 15
eforward5.registrar-servers.compriority 20
eforward2.registrar-servers.compriority 10
eforward1.registrar-servers.compriority 10
eforward3.registrar-servers.compriority 10
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR1
Valid from
2026-09-28 16:56:22
Valid until
2026-12-27 16:56:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint266bd5ca8b6c83e36392387663136d69c982987573fe08f2d4b298f76e2a2cd6Certificate names · 2 SANs
packscan.co
www.packscan.co
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:24:17 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-23 11:24:17 UTClast content: 2026-10-23 11:24:17 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 subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.packscan.coDomain 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 · packscan.co
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.
Content matches8
Same favicon hash or the same page title as this host.
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 packscan.co)
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.
(US)
