VirusTotal
17 / 89 engine detections
レポートを開く“ShareP0int”
フィッシング: sharepoint.process.o9219dsdk.passkeypoint052skljj43auth04.phnia.com — コンテンツが利用できません. 証拠の概要: VirusTotal 17/89 (alphaMountain.ai, BitDefender, CRDF…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 89 engine detections
レポートを開く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
This hostname impersonated Microsoft SharePoint to harvest the sign-in details of people who expected a shared document. Its page title, "ShareP0int", swaps the letter o for a zero, a common trick for slipping past simple brand-keyword filters. PhishDestroy first flagged it on 2026-09-11. The site went offline on 2026-09-12, and its DNS was still inactive at the last check on 2026-10-19.
SharePoint lures usually arrive as an email or chat message saying a file has been shared with you. The link opens a page styled like a Microsoft document portal that asks you to sign in before you can view the file. Whatever you type there goes straight to the operator. The long subdomain stacks words like "sharepoint", "process", "passkey" and "auth" in front of the real registered domain, phnia.com, so a quick glance at the address bar looks like a legitimate authentication flow. A stolen work account can expose mailboxes, internal files and further phishing sent from a trusted address.
On 2026-09-11, the day PhishDestroy flagged it, 17 of 89 VirusTotal engines marked the site as malicious. That is a solid consensus for a page only a day from going dark. The flagging vendors included alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. The hostname is also on the PhishDestroy blocklist.
phnia.com was registered through NAMECHEAP INC on 2026-08-14, 28 days before the phishing page was detected. That gap fits a domain bought ahead of time and then given a disposable, randomized subdomain for the campaign. The page was hosted in Germany on the Ultahost, Inc. network at 79.133.56.155. It used a free Let's Encrypt certificate, so the padlock in the browser said nothing about whether the site was genuine.
If you entered a Microsoft password on this page, change it immediately and make sure the new one is not reused anywhere else. Then sign out all active sessions and review your MFA methods for any devices or phone numbers you did not add. Check your mailbox for new forwarding or inbox rules, and look for unfamiliar app consents in your account settings. Report the incident to your IT or security team, even though the site is now down. Defenders should block phnia.com and all of its subdomains, search mail and proxy logs for hits between 2026-08-14 and 2026-09-12, and reset credentials for any users who reached the page.
Location describes the IP network.
39cf32fdb6a4e50ee591cfb9acf4de0cca3717ce1e9bf9d69eda3586ea98d9d2Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
sharepoint.process.o9219dsdk.passkeypoint052skljj43auth04.phnia.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
No threat flag
View source17/89 engine detections
View sourcesharepoint.process.o9219dsdk.passkeypoint052skljj43auth04.phnia.com
View sourceListed 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 ↗
sharepoint.process.o9219dsdk.passkeypoint052skljj43auth04.phnia.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.