PhishDestroy first recorded ruji.network on 2026-06-18. Stored VirusTotal result: 12/92 engines flagged. Malicious: 10. Suspicious: 2. Analysis time (as stored): 2026-10-02 06:37 UTC. Retrieved (as stored): 2026-10-30 04:00 UTC.
Page title: “Web3 Connect Demo”
More about the sources
Recorded security signals
Stored VirusTotal result: 12/92 engines flagged. Malicious: 10. Suspicious: 2. Analysis time (as stored): 2026-10-02 06:37 UTC. Retrieved (as stored): 2026-10-30 04:00 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
ABUSE NOTICE · 7D+ 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@dynadot.com. The latest stored availability evidence still shows the domain reachable; 5 months 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.
Elapsed since first report
5 months
Reports sent
1
Latest case ID
PD-20260618-EDF1B5
Current status
HTTP 301 at latest stored check
Analysis
Domain summary
PhishDestroy first recorded ruji.network on 2026-06-18. Stored VirusTotal result: 12/92 engines flagged. Malicious: 10. Suspicious: 2. Analysis time (as stored): 2026-10-02 06:37 UTC. Retrieved (as stored): 2026-10-30 04:00 UTC. Risk: critical (evidence score 98/100). Registrar: Dynadot. Status: Last known active. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
The domain ruji.network, now offline, is identified as a phishing threat by 5 out of 91 VirusTotal vendors. Hosted on Amazon's infrastructure, it employs a Let's Encrypt SSL certificate, a common tactic to lend legitimacy to phishing sites. PhishDestroy has flagged this domain on its public blocklist, highlighting its malicious nature.
Registered with Dynadot Inc, ruji.network was created on June 9, 2026, and detected by PhishDestroy on June 18, 2026. The domain's quick takedown indicates effective intervention, yet its initial operation period underscores the need for rapid detection systems. The platform risk score of 68 out of 100 suggests a significant threat level, while the abuse score of 21 out of 100 reflects moderate malicious activity.
Despite being offline, ruji.network's presence in the threat landscape emphasizes the importance of early detection. The domain's use of Let's Encrypt SSL and Amazon hosting showcases how legitimate services can be manipulated for phishing purposes. This incident serves as a reminder of the evolving tactics employed by cybercriminals to bypass traditional security measures.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
ruji.network is a phishing domain flagged by 5/91 vendors, hosted on Amazon infrastructure. It uses Let's Encrypt SSL.
AI summary
The domain ruji.network, now offline, is identified as a phishing threat by 5 out of 91 VirusTotal vendors. Hosted on Amazon's infrastructure, it employs a Let's Encrypt SSL certificate, a common tactic to lend legitimacy to phishing sites. PhishDestroy has flagged this domain on its public blocklist, highlighting its malicious nature. Registered with Dynadot Inc, ruji.network was created on June 9, 2026, and detected by PhishDestroy on June 18, 2026. The domain's quick takedown indicates effective intervention, yet its initial operation period underscores the need for rapid detection systems. The platform risk score of 68 out of 100 suggests a significant threat level, while the abuse score of 21 out of 100 reflects moderate malicious activity. Despite being offline, ruji.network's presence in the threat landscape emphasizes the importance of early detection. The domain's use of Let's Encrypt SSL and Amazon hosting showcases how legitimate services can be manipulated for phishing purposes. This incident serves as a reminder of the evolving tactics employed by cybercriminals to bypass traditional security measures.
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
Every stored field, with its source and date
Network Security Intelligence
Cloudflare Radar VerdictMalicious
Dga domains
Questions about ruji.network
Is ruji.network legit?
PhishDestroy rates ruji.network as critical risk (evidence score 98/100) from the recorded evidence; it was first recorded on 2026-06-18. Stored VirusTotal result: 12/92 engines flagged. Malicious: 10. Suspicious: 2. Analysis time (as stored): 2026-10-02 06:37 UTC. Retrieved (as stored): 2026-10-30 04:00 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is ruji.network safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on ruji.network. A confirmed blockchain transaction cannot be reversed.
What should I do if I used ruji.network?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. 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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-11-22 11:18 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:18 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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 03:54 UTC.
Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
5 entries
Lifecycle
Domain registered
Added to PhishDestroy+9 d 8 h
First abuse report sent+5 min
VirusTotal analysis with detections+105 d 13 h
Reported 9 d 8 h after registration
AlienVault OTX
16 community references
+31 d 6 h
VirusTotal
12/92 engine detections
+98 d 22 h
URLScan
Page captured
+6 d 15 h
Abuse report sent
PD-20260618-EDF1B5 · Receipt 45953
abuse@dynadot.com
+5 min
Added to PhishDestroy
ruji.network
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Landing pages recorded by URLScan1
URLScan scans retained with this report ended on these pages instead of this domain. Dates are scan times.
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 ruji.network)
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
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 →
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.