The domain rewards-injective.network is associated with a generic phishing scam, posing an elevated risk to users. The site impersonates no specific brand and utilizes no known drainer kit. As of the latest assessment, the domain has been taken offline, reducing immediate risk. However, previous visitors should remain vigilant for any signs of compromise and take appropriate security measures.
rewards-injective.network has been flagged by 2 of 95 VirusTotal vendors, including Ermes and Gridinsoft, and appears on 4 security blocklists, namely PhishDestroy, Polkadot, Enkrypt, and Codeesura. The domain was registered through HOSTINGER operations, UAB, on September 01, 2025. It resolves to the IP address 172.67.165.147, which is located in the US under AS13335 Cloudflare, Inc. The SSL certificate is issued by WE1. The page title observed on the site is 'Injective | The Blockchain Built for Finance & Web3 Innovation'.
Users who have visited rewards-injective.network should take several steps to ensure their safety. For those involved in cryptocurrency, it is crucial to revoke any unauthorized token approvals and move funds to a new, secure wallet. For credential or login phishing, users should change their passwords, enable two-factor authentication, and monitor their accounts for any unusual activity. Any suspicious activity should be reported to the relevant security authorities and the service provider. To prevent future incidents, users should exercise caution when clicking on links or entering sensitive information on unfamiliar websites.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='rewards-injective.network', port=80): Max retries exceeded with url: / (Caused by NewConne
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:11:01 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-05-26 10:12:47 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-26 10:12:47 UTC → 2026-09-30 16:14:55 UTC · 3,054.04hmidpoint estimate ≈ 2026-07-29 01:13:51 UTC · precision very low · basis bounded
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.
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.
(LT)
