VirusTotal
5 / 92 engine detections
打开报告“Log In - AlJarhi Network Automation”
被列入黑名单的域名: dev.cyborgx.tech — 最后已知的活跃状态 (HTTP 302). 证据摘要: VirusTotal 5/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
5 / 92 engine detections
打开报告no community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
dev.cyborgx.tech is a suspicious domain on the PhishDestroy blocklist that presents itself as a sign-in page titled "Log In - AlJarhi Network Automation". The page references a network automation service, not a crypto wallet or exchange. PhishDestroy first flagged it on 2026-08-27. As of 2026-10-19 the site was still online and answering requests with a redirect.
The visible lure is a login form under the AlJarhi Network Automation name, hosted on a development-style subdomain. A page like this carries one main risk: whatever username, password or one-time code a visitor types can be captured by whoever runs the server. If those credentials are reused elsewhere, including on email or crypto accounts, they can be used to take over those accounts. The redirect means visitors may be passed on to another destination after the first request, so the address they arrive at may not be the one they clicked.
Independent detection is limited. On 2026-10-19, 5 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a minority verdict, but it comes from several unrelated vendors, which supports treating the site with caution. Among blocklists, only PhishDestroy currently lists it.
The domain was registered through NameCheap, Inc. on 2026-01-22, about seven months before PhishDestroy detected it. That gap suggests a domain that sat quietly or served other content before the login page drew attention. Traffic is fronted by Cloudflare, Inc., with the address geolocated to Canada, so the real origin server is hidden from view. The Let's Encrypt certificate gives the page a normal padlock, which says nothing about whether it is trustworthy.
If you entered a username or password on this page, change it right away. Change it everywhere else you used the same password too, and turn on app-based two-factor authentication. Check the affected accounts for unfamiliar sessions, forwarding rules or recovery-email changes, and sign out all other devices. If you only visited and typed nothing, close the tab and clear any saved autofill for the site. Defenders should block the domain and its redirect chain, search proxy and DNS logs for earlier visits, and alert staff that the AlJarhi Network Automation login screen is not a sanctioned portal.
For the registrable domain cyborgx.tech behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
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.
Edge-IP 声誉不属于此域。
vida.ns.cloudflare.comLocation describes the IP network.
957557575e6bb325a3d70fc07c0292b07e3ed417fcfc85d9fcc9b0f0becc3aa2cyborgx.techSaved 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 dev.cyborgx.tech · checked Sep 18, 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.
dev.cyborgx.tech
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
2→5
可访问
5/92 engine detections
View sourceNo threat flag
View sourcedev.cyborgx.tech
View source1 条社区报告
类别PHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-08-27T13:58:58.410Z.
Listed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
dev.cyborgx.tech)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.