blueairdirect.shop appeared on PhishDestroy’s watchlist on 2026-10-18. The domain currently returns no content and was unreachable when checked on 2026-10-19. It has been added to PhishDestroy’s blocklist and remains listed. The site’s purpose cannot be confirmed because the page does not load. Its lack of reachable content is typical of domains used for short‑lived phishing campaigns.
How the scam works
The domain mimics a legitimate retail storefront, suggesting visitors may be asked to provide personal information or interact with cryptocurrency wallets. If a visitor follows such prompts, attackers could capture login credentials, personal data, or obtain wallet approvals that enable fund transfers. The loss would be the unauthorized use of the victim’s accounts or assets.
Evidence
VirusTotal scanned the domain on 2026-10-19 and recorded three detections from 92 scanning engines, with alerts from alphaMountain.ai, Gridinsoft and Netcraft. The domain appears in two OTX threat pulses and is currently listed only on PhishDestroy’s blocklist. The low number of detections suggests limited visibility but still warrants caution.
Infrastructure
The site resolves to IP address 162.222.90.238, which belongs to the Malakmadze Web LLC network in Georgia. No registrar or registration date information is available. No TLS certificate details are known.
What to do
Anyone who visited blueairdirect.shop should assume any entered credentials are compromised and change passwords immediately. If a cryptocurrency wallet was connected, revoke all approvals and monitor the wallet for unauthorized activity. Organizations should block the domain and its IP at firewalls and DNS filters. Continue monitoring threat feeds for related indicators.
RegistrationCreated May 26, 2026 (146d)—Expires May 26, 2027
Technical detailsProvenance & timestamps
First DetectedOct 18, 2026
Submitted URLhttp://blueairdirect.shop/
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · blueairdirect.shop
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.
4 evidence signal groups linked0 stored notification recordsUnverified
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 blueairdirect.shop)
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)
