VirusTotal
13 / 91 engine detections
보고서 열기“Rewards | Boros”
app-boros-pendle.finance — 연결 가능 · 액세스가 제한됨 (HTTP 403). 브랜드 사칭: Pendle; 사기 유형: Impersonation. 증거 요약: VirusTotal 13/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); Spamhaus DBL_PHISH; 3 external blocklist matches (MetaMask, ScamSniffer, SEAL); PhishDestroy score 100/100. 등록기관: NiceNIC.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
13 / 91 engine detections
보고서 열기DBL_PHISH
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.
AI-assisted evidence review
Analysis of app-boros-pendle.finance indicates that the domain was registered on July 24, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED and is currently hosted on the IP address 188.114.96.3. The authoritative name servers are kip.ns.cloudflare.com and meera.ns.cloudflare.com, both belonging to Cloudflare’s DNS network, which is frequently used by both legitimate services and malicious operators to obscure infrastructure. The domain remains active as of the report date and is listed on a single security blocklist. VirusTotal scanning shows that one out of ninety‑one anti‑malware engines flagged the domain, suggesting at least one vendor has identified malicious behavior associated with it. PhishDestroy also reports the domain as blocked, reinforcing the classification as a phishing vector.
The limited detection surface—only one blocklist entry and a single vendor flag—means that broader community awareness of the threat is still emerging. No additional intelligence such as Safe Browsing status, Open Threat Exchange reports, SSL certificate details, or HTTP response codes is available, leaving the full scope of the hosting environment and potential payload delivery mechanisms uncertain. The use of Cloudflare name servers does not, by itself, confirm malicious intent, but combined with the registrar information, the active status, and the existing blocklist entries, the risk profile aligns with a high‑confidence phishing indicator. Defenders should add app-boros-pendle.finance to URL filtering rules and blocklist it at perimeter and endpoint layers.
Network monitoring should include alerts for DNS queries to the two Cloudflare name servers that resolve to 188.114.96.3, and any outbound connections to that IP should be inspected or denied pending further investigation. Continuous re‑scanning on VirusTotal and other multi‑engine platforms is recommended to capture any escalation in detection counts.
Last checked
For this gTLD, 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 평판은 이 도메인에 귀속되지 않습니다.
kip.ns.cloudflare.commeera.ns.cloudflare.comLocation describes the IP network.
1cd5c6a8d90f4523adb6170a7e22b442c78cd7b147835da16bbfe8cf14e2d581Saved 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 app-boros-pendle.finance · checked Jul 24, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
app-boros-pendle.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
알 수 없음→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
이용 불가→접속 가능
접속 가능→이용 불가
13/91 engine detections
View sourceNo threat flag
View sourceapp-boros-pendle.finance
View sourcePage captured
View source저장된 유사 도메인 36개
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 ↗
app-boros-pendle.finance)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.