VirusTotal
19 / 92 engine detections
レポートを開く“System Login”
認証情報フィッシング: rovexa32.pro — コンテンツが利用できません. 証拠の概要: VirusTotal 19/92 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); CF Radar malicious…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
19 / 92 engine detections
レポートを開く悪意あり
レポートを開くScan report
レポートを開く4 community references
レポートを開く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
rovexa32.pro hosted a credential phishing page titled "System Login". It was a bare sign-in screen that named no brand and was built to collect whatever account details a visitor typed in. PhishDestroy first saw it on 2026-09-25. The site is now dead and its content unreachable, and it has been offline since 2026-10-19.
Pages like this rely on a neutral, official-sounding title such as "System Login". Victims arriving from a link in an email, chat or ad assume they are signing in to a work portal, webmail or some other service they already use. Anything entered into the form goes straight to the operators rather than to a real login system. The victim loses control of that account, and of every other account that shares the same password. Stolen credentials are often reused quickly for account takeover, resold, or tried against crypto exchanges and wallets linked to the same email address.
On 2026-10-07, 19 of 92 VirusTotal engines flagged the domain. They included alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet and G-Data. That is a meaningful spread of independent vendors agreeing on the verdict. The domain also appears on the PhishDestroy and PhishFeed blocklists. It is referenced in 4 AlienVault OTX pulses, which means other researchers tracked it as part of known threat activity.
The domain was registered on 2026-09-15 through TuringSign Inc. d/b/a Cosmotown, only ten days before PhishDestroy caught it. That short gap is typical of throwaway phishing domains set up for a brief campaign. The page was hosted in Chile on the ABGON COMUNICACIONES network. It used a free Let's Encrypt certificate, so the browser padlock appeared even though the page was fraudulent.
If you entered a username and password on this page, change that password immediately. Also change it on every other service where you used the same one. Turn on two-factor authentication, preferably app-based or a hardware key, and review recent sign-ins and active sessions so you can log out anything unfamiliar. If it was a work account, tell your IT or security team right away so they can check for misuse. Defenders should block the domain and its hosting IP, search mail and proxy logs for users who reached it, and force credential resets for anyone who did.
Stored page, network and scanner observations, grouped by source and observation time.
観測された: · Retrieved:
| Uuid | 01a0da3c-6e34-7485-b01e-d2c94da478f9 |
|---|---|
| Final url | https://rovexa32.pro/ |
| ステータス | 200 |
| リダイレクト | https-only |
| Redirects | [
{
"to": "https://rovexa32.pro/",
"from": "http://rovexa32.pro/",
"status": 307
},
{
"to": "http://rovexa32.pro/",
"from": "https://rovexa32.pro/",
"status": 307
},
{
"to": "https://rovexa32.pro/",
"from": "http://rovexa32.pro/",
"status": 301
}
] |
| Ip | 45.231.49.147 |
| Ptr | mail.rovexa32.pro |
| Contacted domains | [
"cdn.tailwindcss.com",
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.41.163",
"142.250.68.202",
"104.26.2.143",
"45.231.49.147"
] |
| Asns | [
"15169",
"13335",
"28098"
] |
| Countries | [
"US",
"CL"
] |
| Document hash | 1c27e8df8e5dca4dba86c3b4c638a9ba0ee293c22a41877eb494e29dbc858c79 |
| Globals | [
"requestResize",
"tailwind",
"/template.html",
"loginForm",
"submitButton",
"buttonSpan",
"originalButtonText",
"errorMessageDiv"
] |
| クッキー | [
"PHPSESSID"
] |
| Tls | {
"san": [
"mail.rovexa32.pro",
"rovexa32.pro",
"www.rovexa32.pro"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "rovexa32.pro",
"protocol": "TLS 1.3",
"valid_to": "2026-12-17T19:14:39Z",
"valid_from": "2026-09-18T19:14:40Z"
} |
| Domain age days | 9 |
| Apex age days | 9 |
| Tls age days | 7 |
| Tls valid days | 89 |
| Requests | 5 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "Apache/2.4.58 (Ubuntu)",
"content-type": "text/html; charset=UTF-8"
} |
観測された: · Retrieved:
| Uuid | cef9d353-8084-4777-b88b-050d787e6279 |
|---|---|
| Final url | https://rovexa32.pro/ |
| ステータス | 200 |
| History | [
{
"url": "https://rovexa32.pro/",
"status": 200
}
] |
| DOM structure hash | d5fd2beabb3eab7257fb7b77e70c5514faefb2926469711de0238c25e9515e55 |
| Document hash | 1c27e8df8e5dca4dba86c3b4c638a9ba0ee293c22a41877eb494e29dbc858c79 |
| Phishing v2 | [
"phishing"
] |
| Domain risks | [
"New Domains",
"Security Risks",
"Phishing",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "rovexa32.pro",
"type": "A",
"value": "45.231.49.147"
}
] |
| Dnssec valid | false |
| Ip | 45.231.49.147 |
| Verdict | {
"tags": [
"phishing"
],
"malicious": true,
"categories": [
"phishing"
]
} |
| Registration record | {
"registrar": "TuringSign Inc. d/b/a Cosmotown",
"created": "2026-09-15T05:09:37Z",
"updated": "2026-09-20T05:09:49Z",
"expires": "2027-09-15T05:09:37Z",
"nameservers": [
"ns2.rovexa32.pro",
"ns1.rovexa32.pro"
]
} |
ns1.rovexa32.prons2.rovexa32.promail.rovexa32.propriority 10Location describes the IP network.
90fef200085453335a1276dbd020386f3e95ace0cc9fbb58be7eaf620e241618mail.rovexa32.prowww.rovexa32.proSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
mail.rovexa32.proDomain recordwww.rovexa32.proDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of rovexa32.pro · checked Sep 25, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source19/92 engine detections
View source4 community references
View sourcePD-20260925-7D3C9C
rovexa32.pro
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
rovexa32.pro
PD-20260925-7D3C9C Recipient: op_ct@cosmotown.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 ↗
rovexa32.pro)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.