VirusTotal
6 / 91 engine detections
レポートを開く“intCC Login form | UniCC new domain 2025”
認証情報フィッシング: intcc.cc — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 91 engine detections
レポートを開く4 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
intcc.cc presents itself as the official new address of UniCC. Its page title reads "intCC Login form | UniCC new domain 2025" and it serves a login form aimed at anyone hunting for a working UniCC mirror. PhishDestroy classifies it as credential phishing and first flagged it on 2026-09-28. As of 2026-10-19 the site was still online and serving its login content.
Lookalike "new domain" pages depend on people expecting a brand to move addresses, so a fresh domain promising continuity feels plausible. The visitor enters a username and password into what looks like the familiar UniCC sign-in form, and those credentials go straight to whoever runs the page. The stolen logins can be used to take over the account, drain any balance tied to it, or try the same password on other services. Some clones of this kind also ask for a deposit or "account top-up" after login, and that money is lost.
VirusTotal shows 6 of 91 engines flagging the domain as of 2026-10-03: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and URLQuery. That count is low, so many browsers and filters may still load the page without a warning. Four AlienVault OTX pulses reference the domain, which means other researchers are tracking it independently. Among the blocklists we checked, only PhishDestroy currently lists it.
The domain was registered through Namecheap on 2026-03-24, about six months before PhishDestroy detected it. The page still advertises itself as a "2025" domain even though the registration dates from 2026. It is hosted on Hostinger International Limited's network in Lithuania at 2.57.91.90. Its Let's Encrypt certificate gives it a browser padlock, but that only means the connection is encrypted and says nothing about whether the site is legitimate.
If you typed a password into intcc.cc, treat it as compromised. Change it on the genuine service and on any other site where you reused it, and turn on two-factor authentication wherever it is offered. Do not send any deposit or top-up payment the site requests, and check linked accounts for logins or transactions you did not make. Defenders should block the domain at DNS and proxy level and alert on traffic to it. Blocking the IP should be done with care, because shared hosting may serve unrelated sites from the same address.
ns1.dns-parking.comns2.dns-parking.commx1.hostinger.compriority 5mx2.hostinger.compriority 10Location describes the IP network.
3a124e862f7fb70d2d10c0707bae4a8f9f5852051594c81df42a5ffad6c23ae2www.intcc.ccSaved 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.
www.intcc.ccDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of intcc.cc · checked Sep 28, 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
不明→live_content
content_served
不明→live_content
content_served
4→5
3→4
0→3
到達可能
No threat flag
View source6/91 engine detections
View source4 community references
View sourcePage captured
View sourceintcc.cc
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
intcc.cc
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 ↗
intcc.cc)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.