The domain www.yusjibtravel.ng.yusjibtravels.com is a phishing site engaged in brand impersonation, specifically targeting users of the decentralized finance (DeFi) platform Aave. This scam operates as a DeFi fraud, attempting to deceive victims into interacting with malicious smart contracts or disclosing sensitive wallet information. As of the latest verification, www.yusjibtravel.ng.yusjibtravels.com has been taken offline, though prior activity posed an elevated risk to users.
Technical indicators confirm the domain's malicious intent. The domain was flagged by 2 of 95 security vendors on VirusTotal, including SOCRadar, and appears on 1 security blocklist (PhishDestroy). Registered through OwnRegistrar, Inc. on November 30, 2024, it resolves to the IP address 192.3.190.186, hosted on AS36352 (HostPapa) in the US. No SSL certificate was issued, and the observed HTTP status was 530. Nameservers associated with the domain are dns1.webproserver.com and dns2.webproserver.com. Google Safe Browsing did not flag the domain at the time of analysis.
Users who interacted with www.yusjibtravel.ng.yusjibtravels.com should immediately revoke any token approvals granted to unknown contracts via wallet interfaces like Etherscan or Revoke.cash. Funds should be transferred to a new, secure wallet to mitigate potential losses. Enable two-factor authentication (2FA) on all accounts, monitor for unauthorized transactions, and report the domain to platforms such as Google Safe Browsing, PhishTank, or the impersonated brand's official security channels for further action.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-302.invalid', port=80): Max retries exceeded with url: / (Caused by New
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Nov 30, 2024 —Expires Nov 30, 2025
Time to First Unavailability199 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
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 observationUnknownProbe Inconclusive20%2026-10-11 01:28:24 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:18:17 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.
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-302.invalid detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Apr 23, 2026
Time to First Unavailability
4775 hours elapsed from detection to the first unavailable observation.
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.
4 evidence signal groups linked0 reports recordedContent unavailable
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 →
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.
(US)
