MALICIOUS — CRITICAL
mobapay[.]best
11 of 91 security engines flagged the domain; 1 public blocklist listed it (OpenPhish).
- VirusTotal
- 11/91
- Blocklists
- 1 · OpenPhish
- Availability
- Unverified
Do not enter credentials, seed phrases, payment details, or personal information on this domain.
Jump to section
Evidence Digest
mobapay.best is classified critical with an evidence score of 93/100. 11 of 91 security engines flagged the domain; 1 public blocklist listed it (OpenPhish). Registered 9 Jul 2026 via Dynadot Inc, hosted on 37.140.192.242 (RU). 1 outgoing abuse report is recorded, most recently on 9 Aug 2026.
Stored generated summary (templated)reviewed-openai · Aug 9, 2026
Retained for the record. This text repeats stored detection facts and is not presented as authored analysis.
Assessment Stored evidence for mobapay.best: VirusTotal recorded 11 detections among 91 scanners on 2026-08-09. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for mobapay.best. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence VirusTotal records 11 detections among 91 scanners in the stored snapshot dated 2026-08-09. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-09 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context OpenPhish are recorded as named external blocklist observations for mobapay.best in the snapshot dated 2026-08-09. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains mobapay.best as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline The record first observed mobapay.best on 2026-08-09. The OpenPhish blocklist snapshot is dated 2026-08-09 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-07-09. A URLScan reference was stored on 2026-08-09 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure The record lists Dynadot Inc as the registrar for mobapay.best. The source stores 37.140.192.242 as the observed address for mobapay.best. The registration date for mobapay.best is recorded as 2026-07-09. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion The mobapay.best record states that VirusTotal recorded 11 detections among 91 scanners on 2026-08-09. OpenPhish remain named blocklist observations from the snapshot dated 2026-08-09. PhishDestroy remains a separate publisher catalogue entry in the stored record. Dynadot Inc is presented only as the recorded registrar, while 37.140.192.242 is presented only as the observed address. The supported conclusion is bounded to the exact stored observations for mobapay.best. Any statement beyond those source values would require additional dated material.
Recommended Actions Use a known service address obtained separately from this report and avoid submitting sensitive information to mobapay.best during review. Defenders can retain the exact mobapay.best hostname as an indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to mobapay.best; the stored record does not justify extending that rule to 37.140.192.242 or the Dynadot Inc registrar record.
Data coverage12 recorded checks
Network Security Intelligence
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | mobapay.best |
malicious | Sinkholed |
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Technologies · 1 identified
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
nginx.org 100% confidenceVirusTotal Analysis
Archived Evidence
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of mobapay.best · checked Aug 9, 2026
Site Configuration Analysis
Evidence & External ReportsIndependent lookups and source reports
PD-20260809-5FD10D Recipient: abuse@reg.ru Victim safety and official reportingImmediate actions and verified reporting channels
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 →.