rufus.im
Evidence Summary
PhishDestroy first observed rufus.im on Sep 21, 2026. Stored content metadata identifies Unknown as the apparent target. Current evidence score: 66/100 (high).
Positive findings are stored from 3 sources: VirusTotal, MetaMask, and SEAL. VirusTotal recorded 4 detections among 89 engines: CRDF, Forcepoint ThreatSeeker, Gridinsoft, VIPRE on Sep 21, 2026 at 03:27 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Sep 21, 2026 at 02:20 UTC. Non-positive and contextual checks: Google Safe Browsing returned no flag on Sep 21, 2026 at 03:28 UTC. URLScan captured the page on Sep 21, 2026 at 03:35 UTC.
The collector marked the hostname reachable on Sep 21, 2026 at 03:35 UTC, but did not retain the HTTP response code. At collection time, the hostname resolved to 188.114.96.3. The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance.
The content indicators and 3 positive source findings support the current Unknown impersonation and phishing classification. The target field identifies Unknown, but the record does not establish whether the page requested credentials, a seed phrase, or a wallet connection.
Forensic History & Detection Timeline
-
Threat First Observed Sep 21, 2026 · 05:27 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
188.114.96.3.
Threat Response Pipeline
Public Blocklist Status
Evasion analysis
Cloaking & traffic-distribution check
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
Stored Capture · 2 sources
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
VirusTotal Analysis
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of rufus.im · checked Sep 21, 2026
Evidence & External Reports
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive