VirusTotal
2 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Split Wallet - Solana Expense Splitting”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
2 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 det.
Alerts refer to the preserved scan. They do not describe the current state of the site.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Evidence-based analysis Generated from the observations retained in this report. No stored AI narrative is available for this record. Each source retains its own collection date.
PhishDestroy first observed yearofslu.com on Oct 17, 2026. Stored content metadata identifies Phantom as the apparent target. The captured page title is “Split Wallet - Solana Expense Splitting”. Page analysis recorded additional brand references to Solana. Stored page analysis classifies the content as seed phrase theft. Current evidence score: 88/100 (critical).
Positive findings are stored from 4 sources: VirusTotal, MetaMask, SEAL, and URLQuery. VirusTotal recorded 2 detections among 92 engines: alphaMountain.ai, CRDF on Oct 18, 2026 at 02:28 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 18, 2026 at 02:20 UTC. URLQuery recorded 3 detections; no observation timestamp was retained. Additional recorded evidence: AlienVault OTX listed 4 community pulse references (not vendor detections) on Oct 18, 2026 at 02:29 UTC. URLScan captured the page on Oct 17, 2026 at 11:36 UTC.
HTTP 301 was recorded on Oct 17, 2026 at 23:02 UTC. Latest classified outcome: redirect observed; cause http redirect on Oct 17, 2026 at 21:02 UTC. Registration records for the domain list ENOM, INC. as the registrar and Jan 21, 2026 as the creation date. At collection time, the hostname resolved to 18.168.91.127 on AS16509 (Amazon.com, Inc.). The recorded endpoint location is London, GB. The stored server header is AmazonS3. DOM analysis on Oct 17, 2026 at 14:20 UTC returned 88/100. The evidence archive retains 3 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / YR1 as the certificate issuer with validity through Jan 14, 2027; checked Oct 17, 2026 at 13:02 UTC.
The content indicators and 4 positive source findings support the current Phantom-themed seed phrase theft classification.
22 · datasets with records / 9 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
2 · external source matches
ENOM, INC. · 18.168.91.127 · DNS, TLS and retained responses
dns1.name-services.comdns2.name-services.comdns3.name-services.comdns4.name-services.comdns5.name-services.comLocation describes the IP network.
91c01249e3fa8deda3b4a428b08d44e1955f17600e2af34c7feb31bdb68be801Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of yearofslu.com · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://yearofslu.com/https://www.yearofslu.com/Content-Type: text/html; charset=utf-8Server: AmazonS3Content-Encoding: gzip81823391eba94109dceb69d89b807381af8c5ad27efe32992a3ae5c044c9e01233522keep-alivegziptext/html; charset=utf-8Sat, 17 Oct 2026 02:11:38 GMTW/"90b3607b0511857382caabf7d71fee65"Sat, 17 Oct 2026 02:06:59 GMTAmazonS3chunkedAccept-Encoding1.1 5510ba86e3df44d161d0304fbdee228c.cloudfront.net (CloudFront)cjhYtOInDwQQCld8nJm-jXao5o5LWRlNjMUbNpN1a6nQ8-Q1Qwt1ZA==FRA60-P128gPwns9HVyaQAVD.wj6Z87Y7am9hgruXHit from cloudfrontValues retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy scan recorded a successful response. The file contents were not retained.
/sitemap.xml
A legacy scan recorded a successful response. The file contents were not retained.
/.well-known/security.txt
A legacy scan recorded a successful response. The file contents were not retained.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Local archived 2026-10-17 11:30:20 UTCScanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://www.yearofslu.com/
No live-check result has been retained.
1 · outbound report records
18.168.91.127.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
1→2
Reachable
Unknown
probe_inconclusive
12 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Shared hosting, registrar records and related domains
3 stored lookalike domains
Original reports, independent checks and evidence links
PD-20261017-318E09 Recipient: abuse@enom.com AUP & Terms of Service Violations: Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices. Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension. Applicable Legal Framework (GB): Computer Misuse Act 1990 Fraud Act 2006 Communications Act 2003 - Section 127 UK law criminalizes unauthorized computer access, fraud, and malicious communications. Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
Recovery steps, reporting contacts and complaint drafts
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
yearofslu.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “Split Wallet - Solana Expense Splitting”. Apparent target: Phantom.
VirusTotal detections for yearofslu.com: 2 (2026-10-18 02:28:46 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.