VirusTotal
4 / 92 engine detections
レポートを開く“Гайд по moriarti mega: где искать, что ожидать, как не”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@avenacloud.com.
The latest stored availability evidence still shows the domain reachable; 13 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
フィッシング: w01.aksakov-museum.ru — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 4/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 92 engine detections
レポートを開くDBL_SPAM
Scan report
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
w01.aksakov-museum.ru is an impersonation phishing page dressed up as a Russian-language guide to "moriarti mega". Its title translates roughly as "Guide to moriarti mega: where to look, what to expect, how not to…". It targets people hunting for working entry points to the Mega marketplace. PhishDestroy first flagged it on 2026-10-07. On 2026-10-19 the host still responded, but the page content was unreachable.
Pages like this use a helpful "guide" to win trust, then steer readers to supposed official mirrors or login links. Those links lead to lookalike sign-in pages that capture usernames, passwords and one-time codes, or prompt crypto top-ups into balances the operator controls. Anyone who follows the links risks losing their account to a takeover and any funds deposited through the fake site. The museum-themed parent domain has nothing to do with the marketplace content shown in the page title.
On 2026-10-16, four of 92 VirusTotal engines flagged the site: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. That is a low count, so most security tools will not block this address yet. Spamhaus lists the domain in its DBL as spam, which separately confirms abusive use. PhishDestroy is currently the only blocklist carrying it.
The parent domain was registered through RU-CENTER-RU on 2026-07-08, about three months before PhishDestroy detected the page. The site runs on AS201670 (S.C. INFOTECH-GRUP S.R.L.) in Moldova, at 132.243.165.86. The "w01" subdomain fits the numbered-mirror naming common to link-farm pages built around this brand.
If you entered a username or password through links from this page, change that password everywhere you reused it and turn on app-based 2FA. Treat any one-time code you typed there as compromised. Do not send crypto to any balance or "deposit" address reached from this guide, because such transfers cannot be reversed. Defenders should block w01.aksakov-museum.ru and watch for sibling subdomains under the same parent. They should also add 132.243.165.86 to monitoring and report the page to the registrar and hosting provider.
amanda.ns.cloudflare.comclay.ns.cloudflare.comLocation describes the IP network.
8e8325e3005f29af137e4b23729cc7a8fe2b188cb04b11c58b826590153b4aa0Saved 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 w01.aksakov-museum.ru · checked Oct 7, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://xn--80acmtf7cj.xn--p1ai/; server=nginx
w01.aksakov-museum.ru
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
1→2
不明→live_content
content_served
0→1
No threat flag
View source4/92 engine detections
View sourcePD-20261007-CE2CFC
Page captured
View sourcew01.aksakov-museum.ru
View source保存された類似ドメイン:114 件
114 件中 100 件を表示
PD-20261007-CE2CFC Recipient: abuse@avenacloud.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
w01.aksakov-museum.ru)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.