VirusTotal
16 / 92 engine detections
レポートを開く“Ficohsa”
フィッシング: ficofacil.com — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 16/92 (alphaMountain.ai, BitDefender, CRDF, DNS8, ESET); CF Radar malicious; PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 92 engine detections
レポートを開く悪意あり
レポートを開く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
ficofacil.com serves a page titled simply "Ficohsa", the name of a Central American banking brand, on a domain that is not that brand's own name. PhishDestroy added it to its blocklist on 2026-10-10. The domain has no confirmed scheme classification yet, but the borrowed bank name and independent vendor detections make it a site to avoid. It was still online with live content when checked on 2026-10-19.
A page that carries a bank's name on an unrelated, friendly-sounding domain like "ficofacil" is the classic setup for harvesting banking logins, card details or personal information from people who believe they are dealing with the real institution. We have not confirmed which of these the page collects. Anything typed into it, such as usernames, passwords, one-time codes, card numbers or identity details, should be treated as exposed.
On 2026-10-10, 16 of 92 VirusTotal engines flagged the domain, among them BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CRDF and DNS8. That is a meaningful minority of engines, and it includes several mainstream vendors rather than only niche feeds. The domain also appears in 4 AlienVault OTX threat pulses, so other researchers have tied it to malicious activity independently. Among the blocklists we track, only PhishDestroy currently lists it.
The domain was registered on 2019-07-30 through Cloudflare, Inc., more than seven years before PhishDestroy flagged it. An older domain can slip past filters that distrust new registrations, and it may have changed purpose over time. Traffic runs through Cloudflare's network (AS13335, US), which places the real origin server behind a proxy and out of public view.
If you entered banking credentials on this site, change your online banking password immediately, using the bank's official app or a number from your card, and reset any account that shares that password. Contact your bank to review recent transactions, freeze or reissue any card you typed in, and ask about the security of your one-time codes. Be wary of follow-up calls or messages that claim to be from Ficohsa and ask for codes. Defenders should block ficofacil.com at DNS and the web proxy, search mail and proxy logs for visits, and report it to Ficohsa's security team and to Cloudflare's abuse channel.
Edge-IP の評判はこのドメインに起因しません。
jacob.ns.cloudflare.comteagan.ns.cloudflare.comLocation describes the IP network.
e35d5ff6ac1cb57f6b4970fe7d26eb68277a220a746f12f9fd9aa76ca881cc9eSaved 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.
link.ficofacil.comDomain recordwww.ficofacil.comDomain recordThe original observation time is not recorded for these hostnames.
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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_direct; server=cloudflare; provider_error=cloudflare_phishing_interstitial
ficofacil.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
live_content→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
不明→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 sourcePage captured
View source4 community references
View source16/92 engine detections
View sourceficofacil.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 ↗
ficofacil.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.