VirusTotal
17 / 92 engine detections
보고서 열기“blopartartirtcloak.xyz | 522: Connection timed out”
kobravek.com — 마지막으로 알려진 활성 (HTTP 308). 증거 요약: VirusTotal 17/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); CF Radar malicious; PhishDestroy score 100/100. 등록기관: Dynadot.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
17 / 92 engine detections
보고서 열기악성
보고서 열기5 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.
AI-assisted evidence review
kobravek.com is on the PhishDestroy blocklist as a suspicious domain. No impersonated brand or scam kit has been identified on it so far. PhishDestroy first saw it on 2026-10-11. As of 2026-10-19 the site was still online and sending visitors onward through a redirect rather than serving its own content.
The page title points to a different domain, blopartartirtcloak.xyz, alongside a "522: Connection timed out" error, so visitors are not shown a recognisable brand. That title does not match the suspicious rating we gave the domain. The main risk is where the redirect leads. Domains like this often pass traffic to pages that collect passwords, ask for wallet connections or push downloads, and anyone who follows the chain could lose credentials or funds. Treat any page reached through kobravek.com as untrusted, whatever it looks like.
On 2026-10-12, 17 of 92 VirusTotal engines flagged the domain. The vendors include alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. That many unrelated security vendors agreeing on a domain registered only months earlier is a strong warning sign. The domain also appears in five AlienVault OTX threat pulses, so other researchers have linked it to malicious activity. PhishDestroy is the only blocklist in our set that lists it.
The domain was registered through Dynadot Inc on 2026-07-21, 82 days before PhishDestroy detected it. Domains are often held for a while like this before being put into use. It resolves to 168.100.11.18 on the BL Networks network in the Netherlands. The redirect was still active at the last check, so the domain remains usable.
If you landed on a page through kobravek.com and typed in a password, change it right away and turn on two-factor authentication for that account and any account that shares the password. If you downloaded or ran anything from it, disconnect the device and scan it with up-to-date security software. If you sent funds or shared payment details, contact your bank or exchange immediately and keep any transaction references. Defenders should block kobravek.com and 168.100.11.18 at DNS and proxy level and check logs for earlier visits. They should also watch for traffic to blopartartirtcloak.xyz, which appears in the page title.
urlscan.io scan and screenshot: https://urlscan.io/result/019fff08-a42c-7425-9a6b-afdad6447180/
VirusTotal report: https://www.virustotal.com/gui/domain/kobravek.com
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=kobravek.com
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
ns2.dyna-ns.netparkmail.dynadot.compriority 0Location describes the IP network.
82b730a90f855629e18cb6c0dbf7086a0dd1a496cd74fa185418bf8bbbcedd6dwww.kobravek.comSaved 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.kobravek.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.
redirect: raw=redirect_308; http=308; via=http_proxy; location=https://kobravek.com/; server=nginx/1.18.0 (Ubuntu)
kobravek.com
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
No threat flag
View source5 community references
View source17/92 engine detections
View sourcekobravek.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 ↗
kobravek.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
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.