bikeroza.shop is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). 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 listed bikeroza.shop as a suspicious domain on 2026-10-23. The recorded page title reads “Sorry, the website has been stopped”, but the title date is unknown. An HTTP 200 response was observed on the same day, and Google Safe Browsing reported no threat.
How the scam works
The detections suggest the site may be used for phishing or other fraud, but no specific malicious behavior was observed on the page. In general, domains flagged for phishing attempt to trick users into revealing credentials or personal data by mimicking legitimate services. Without concrete evidence of a particular scheme, the risk remains classified as generic phishing/fraud potential.
Evidence
VirusTotal (analysis 2026-10-21, retrieved 2026-10-23) reported 18 detections across 92 engines, with 15 malicious and 3 suspicious labels. Google Safe Browsing checked on 2026-10-23 returned false. urlscan.io captured the site on 2026-10-23, marking it malicious with a score of 96, while its overall verdict was non‑malicious; the scan showed 307 redirects between HTTP and HTTPS. Cloudflare Radar (2026-10-23) marked the domain malicious under the malware category. OTX listed five pulses referencing the domain. PhishDestroy’s internal blocklist includes the domain, while external blocklists (including Spamhaus) reported no listing.
Infrastructure
The domain was registered with Namecheap, Inc. on 2026-04-28. It resolved to IP 94.154.172.92, which was listed as belonging to IP Vendetta Inc. (ASN 209101) and recorded in country SC. The web server runs nginx and presents a Let’s Encrypt TLS certificate valid until 2026-09-30. Open ports include 21, 22, 80 and 443, and standard DNS records (A, MX, NS, TXT) are present.
What to do
Visitors should avoid entering any credentials or personal information on the site; if they have already done so, change passwords and monitor accounts for suspicious activity. No wallet approvals were detected, so wallet‑related actions are not required. Defenders can block bikeroza.shop at the network perimeter and monitor outbound connections to 94.154.172.92 for any unexpected traffic.
No. PhishDestroy classifies bikeroza.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 bikeroza.shop safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on bikeroza.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 bikeroza.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.
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:14 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-23 11:24:14 UTClast content: 2026-10-23 11:24:14 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.bikeroza.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 · bikeroza.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 bikeroza.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.
