bikewave24.shop is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: Namecheap. Status: Last known active. Hosting: IP Vendetta Inc. PhishDestroy sent 1 abuse report. VirusTotal: 18/92 engines flag it. Do not enter credentials or connect a wallet.
PhishDestroy added bikewave24.shop to its internal blocklist on 2026-10-23 after the domain was first observed by us on that date. The page returned HTTP 200 and displayed the title “Sorry, the website has been stopped”. No dated content was captured, and the site performed mutual 307 redirects between HTTP and HTTPS.
How the scam works
The listing is based on automated detections that label the domain as phishing or malware, but no specific malicious behavior was observed on the captured page. Consequently, the assessment reflects a generic risk that the site could be used for credential harvesting, fraudulent redirects, or malware distribution, which are common tactics for domains flagged by multiple security engines.
Evidence
VirusTotal scanned the domain on 2026-10-22 and reported 15 malicious and 3 suspicious detections from 92 engines. Google Safe Browsing reported no threat on 2026-10-23. urlscan.io recorded a malicious engine score of 96 on 2026-10-23, though its overall verdict was non‑malicious. Cloudflare Radar flagged the domain as malicious for malware on 2026-10-23. OTX lists four pulses referencing the domain as of 2026-10-23. PhishDestroy’s own blocklist marks it as blocked.
Infrastructure
The domain was registered on 2026-04-26 through Namecheap, Inc. The recorded IP was 94.154.172.92, announced by IP Vendetta Inc. (ASN 209101) and listed with the country code SC. The server presented a Let's Encrypt certificate valid until 2026-09-30 and ran nginx. DNS records include standard NS, MX and TXT entries from the registrar’s name servers.
What to do
Do not enter credentials, private keys or seed phrases on this site. If any login information was submitted, change the associated passwords immediately and review account activity. Network defenders should add bikewave24.shop to their deny lists. Continue monitoring reputable threat feeds for any new indicators.
{
"Sophos": "phishing and fraud",
"Webroot": "Phishing and Other Frauds",
"alphaMountain.ai": "Phishing (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "phishing and other frauds"
}
No. PhishDestroy classifies bikewave24.shop as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 18/92 engines flag it. Treat the site as unsafe.
Is bikewave24.shop safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on bikewave24.shop. 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 bikewave24.shop?
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.
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
94.154.172.92
Network ASN
AS209101
Organization
IP Vendetta Inc.
Observed location
Victoria, SC
Server header
nginx
Nameservers 2
dns1.registrar-servers.com
dns2.registrar-servers.com
Mail routing 5 MX records
eforward1.registrar-servers.compriority 10
eforward5.registrar-servers.compriority 20
eforward4.registrar-servers.compriority 15
eforward2.registrar-servers.compriority 10
eforward3.registrar-servers.compriority 10
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR2
Valid from
2026-09-23 09:17:04
Valid until
2026-09-30 01:17:03
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprintcf50b5651f2296293e87039f0a88b7e957b99b513fb8625daefa3b58ecf8328cCertificate names · 1 SAN
94.154.172.92
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:16 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-23 11:24:16 UTClast content: 2026-10-23 11:24:16 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.bikewave24.shopDomain record
The original observation time is not recorded for these hostnames.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · bikewave24.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.
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 bikewave24.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)
