VirusTotal
5 / 91 engine detections
PhishDestroy first recorded merionpay.com on 2026-10-03. Stored VirusTotal result: 5/91 engines flagged. Analysis time (as stored): 2026-10-04 22:40:53. Retrieved (as stored): 2026-10-05 22:55:17.
Stored VirusTotal result: 5/91 engines flagged. Analysis time (as stored): 2026-10-04 22:40:53. Retrieved (as stored): 2026-10-05 22:55:17. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
PhishDestroy analysis, earlier unreviewed version
merionpay.com is an impersonation phishing site built around a payment-style name and flagged by urlscan.io as imitating a generic banking brand. It targets people who expect to log in to a bank or payment account. PhishDestroy first saw it on 2026-10-03. As of 2026-10-19 the domain no longer resolves to active content.
Generic banking phishing uses a convincing but unbranded login portal, usually reached through texts, emails or ads warning of a blocked payment or an account check. The victim types a username, password and often card details or one-time codes, and these go straight to the operator, who uses them to take over the account or move money. When last loaded, the page returned only a "403 Forbidden" title, which differs from the impersonation content we classified.
On VirusTotal, 5 of 91 engines flagged the domain as of 2026-10-06: alphaMountain.ai, CRDF, Netcraft, SOCRadar and URLQuery. Netcraft and CRDF both run dedicated phishing feeds, so their agreement is meaningful even at a low overall count. urlscan.io returned a malicious verdict and matched the page to a banking template. The domain also appears in 2 AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-08-01 through Realtime Register B.V., about two months before PhishDestroy detected it. That gap fits a domain registered in advance and activated for a campaign later. It was hosted on the Aquiryn LLC network in the US. It used a free Let's Encrypt certificate, so the browser padlock showed only an encrypted connection and did not show that the site was legitimate.
If you entered a banking or payment login here, change that password right away from your provider's official app or website. Change it anywhere else you reused it, and reset or re-enroll two-factor authentication. If you typed card numbers or one-time codes, call your bank to block the card, dispute unfamiliar charges and watch statements closely for the next few weeks. Treat any message that pointed you to this site as fraudulent and delete it. Defenders should block merionpay.com at DNS and the web proxy and search mail and SMS logs for links to it. They should also warn customers that real banks do not send them to unfamiliar payment-branded domains to verify accounts.
5 / 91 engine detections
2 det.
Open report50/100
Trust score, lower = worse
Open reportMalicious
SHA-256 cd4b1b89…570b013
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
3 community references
Open reportScan report
Open report83 / 100 · heuristic score · 1 brand reference · 1 classification
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy rates merionpay.com as critical risk (evidence score 85/100) from the recorded evidence; it was first recorded on 2026-10-03. Stored VirusTotal result: 5/91 engines flagged. Analysis time (as stored): 2026-10-04 22:40:53. Retrieved (as stored): 2026-10-05 22:55:17. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on merionpay.com. A confirmed blockchain transaction cannot be reversed.
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.
ns8.asurahosting.commerionpay.compriority 0Location describes the IP network.
34ccb15d7f0715dc9d7401c95b75836c54d6cd500ad6f050a2dc67b3e23532b4deltaexpresstransit.onlineintere-wallet.orglantrustworlds.orgquantumncap.orgwww.copy.intere-wallet.orgwww.deltaexpresstransit.online.intere-wallet.orgwww.emeraltyinvestmentinnovation.org.intere-wallet.orgwww.lantrustfinance.com.intere-wallet.orgwww.lantrustworlds.org.intere-wallet.orgwww.merionpay.com.intere-wallet.orgwww.quantumncap.org.intere-wallet.orgwww.stellarmetaportal.online.intere-wallet.orgwww.stellarpayportal.online.intere-wallet.orgwww.test.intere-wallet.orgSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The domain no longer resolves in DNS.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.merionpay.comDomain recordGoogle PageSpeed Insights — mobile performance audit of merionpay.com ·
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 39 SHA-256 hashes: 39 URLScan scan:
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 02:26 UTC.
Open this scan on URLScan 01a096ce-9a94-713c-b960-a182ec976cb9 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
merionpay.com Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
merionpay.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
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.