Security engines reporting a detection: 10. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 72H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@rashost.com.
The latest stored availability evidence still shows the domain reachable; 3 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
beyway.shop is an impersonation phishing site. It presents itself as a trusted service so that visitors will hand over credentials or personal and payment information. PhishDestroy first detected it on 2026-10-16. When last checked on 2026-10-19 the site was still online and redirecting visitors, so it should be treated as an active threat.
How the scam works
Impersonation pages copy the look, wording and flow of a real brand or shop. Victims are usually led there through ads, search results, social media posts or direct messages. Once the visitor believes the page is genuine, it asks them to log in, register, check out or verify an account, and everything typed is sent to the operators. The .shop domain and the redirect behaviour fit a pattern of luring people with a storefront-style address and then passing them to the page that harvests their data. Victims risk losing account access, card details, money spent on goods that never arrive, and personal information that can be reused for further fraud.
Evidence
On 2026-10-19, VirusTotal showed 10 of 92 security engines flagging the domain. The flagging vendors included alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft, LevelBlue and Netcraft. The domain also appears in 3 AlienVault OTX threat pulses and is listed on the PhishDestroy blocklist. Detection is moderate rather than universal, but several independent vendors agree the site is malicious.
Infrastructure
The domain was registered on 2026-07-26 through Dynadot Inc. This was less than three months before PhishDestroy detected it, which is a typical lifespan for throwaway phishing domains. It resolves to 188.244.119.46 on network AS199242 Malakmadze Web LLC, with hosting located in the US.
What to do
Do not visit beyway.shop or follow its redirects. If you entered a password there, change it right away on the real service and on any other account where you used it, and turn on two-factor authentication. If you submitted card or bank details, contact your bank to block the card and dispute any charges, then watch your statements and inbox for follow-up scams that use your stolen details. Security teams should block the domain and its IP address at the DNS, proxy and email gateway layers, search logs for any connections to it, and report it to the registrar and hosting provider so it can be taken down.
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 10:47:13 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-19 10:47: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.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · beyway.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.
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 beyway.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)
