Ir para o relatório de segurança
Painel de análises
Domain security report
dapp.ocaccess.blog favicon

dapp.ocaccess.blog

“OC.AGENT — AI Prediction Market Infrastructure”

Veredicto de ameaça
CríticoRecurso de domínio
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilidade Não verificado A acessibilidade atual não foi verificada Observado · HTTP probe
Sinais de risco
Detecções do VirusTotal: 1/92 Correspondências da lista de bloqueio armazenada: 1 Automated brand label: MetaMask
17/10/2026 MetaMask CDN
API
Registrador
Dynadot
Resolved IP
188.114.97.3
Registered
14/09/2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Fonte
Primary capture
Collected · UTC
Open capture
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 1. Listas de bloqueio públicas relatando uma correspondência: 1. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
Resumo do relatório

dapp.ocaccess.blog — Não verificado. Representação da marca: MetaMask; Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 1/92 (CRDF); URLScan capture; 1 external blocklist match (ScamSniffer); PhishDestroy score 71/100. Registrador: Dynadot.

The evidence summary below uses retained observations. Each source keeps its own collection date.

Additional indicators at a glance

VirusTotal
VirusTotal
1 det.
URLScan
URLScan
Denunciar ↗
Certificado TLS
Hostname mismatch
Google Trust Services / WE1 · Certificate hostname mismatch
Idade
1 mo New
PhishDestroy
DestroyList
Listado

Source evidence

6 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

1 / 92

Denunciar
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

1 external matches

Detalhes
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Denunciar
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

relatório armazenado

View stored capture ↗
Denunciar
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Resumo das evidências

Crítico
VirusTotal
1/92
URLScan
Stored capture

Evidence-based analysis Generated from the observations retained in this report. No stored AI narrative is available for this record. Each source retains its own collection date.

dapp.ocaccess.blog is a subdomain of ocaccess.blog. PhishDestroy first observed the hostname on Oct 17, 2026. Stored content metadata identifies MetaMask as the apparent target. The captured page title is “OC.AGENT — AI Prediction Market Infrastructure”. Page analysis recorded additional brand references to Orca and Trust Wallet. Stored page analysis classifies the content as impersonation. Current evidence score: 71/100 (critical).

Positive findings are stored from 2 sources: VirusTotal and ScamSniffer. VirusTotal recorded 1 detections among 92 engines: CRDF on Oct 17, 2026 at 19:06 UTC. ScamSniffer listed the hostname in the separate external-blocklist snapshot on Oct 17, 2026 at 18:20 UTC. Additional recorded evidence: URLScan captured the page on Oct 17, 2026 at 11:34 UTC.

The collector marked the hostname reachable on Oct 17, 2026 at 11:34 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 17, 2026 at 09:34 UTC. Registration records for the registrable domain ocaccess.blog list Dynadot LLC as the registrar and Sep 13, 2026 as the creation date. At collection time, the hostname resolved to 188.114.97.3 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Oct 17, 2026 at 14:20 UTC returned 71/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Google Trust Services / WE1 as the certificate issuer with validity through Dec 13, 2026; checked Oct 17, 2026 at 13:02 UTC.

The content indicators and 2 positive source findings support the current MetaMask-themed impersonation classification.

Data coverage & collection

19 · datasets with records / 12 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
1 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
1 · external matches
Cloudflare Radar
limpoCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Dynadot LLCCollection time not recorded
Network & DNS
188.114.97.3 · 2 · nameserversCollection time not recorded
Certificado TLS
Google Trust Services / WE1
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
3 · automated brand labels
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
60/100 · mobile performance
Availability history
1 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Not recorded in this report 12

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Observed indicators
  • Detection & evasion
  • Response records
  • Recorded subdomains
  • Denúncias da comunidade
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

1 · external source matches

Status da lista de bloqueios pública

Domain, network & archive

Dynadot LLC · 188.114.97.3 · DNS, TLS and retained responses

Domain details

Domínio
IP Context Cloudflare shared edge origin IP hidden A reputação do Edge-IP não é atribuída a este domínio.
Registrar (base domain) Dynadot US(US)
Contato para abusos["info@dynadot.com"]
Registro da ICANNICANN Lookup (RDAP) →
Pesquisa WHOISRDAP da ICANN para ocaccess.blog →
Registration (base domain)ocaccess.blog · Criado 14/09/2026 (33d · New) — Expires 14/09/2027
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez17/10/2026
DOM Analysisanalyzed 17/10/2026score 71/1003 brand signals
Submitted URLhttp://dapp.ocaccess.blog/
Favicon Hash
ICANN OVERSIGHT Registration: ocaccess.blog

Credenciamento e contexto RAA
Registrar accreditation and DNS abuse obligations

For the registrable domain ocaccess.blog behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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.

O credenciamento é um contrato, não um selo de segurança. Verificar as taxas da ICANN Ler o RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nada é enviado automaticamente.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

A reputação do Edge-IP não é atribuída a este domínio.

Servidores de nomes 2
  • darl.ns.cloudflare.com
  • dell.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Google Trust Services / WE1
Valid from
2026-09-14 01:35:50
Valid until
2026-12-13 02:33:27
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-17 13:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte35ddb341f262fe5cab9b8faa50debb7e1ee1659e221231dd9684fb3f6d862df
Certificate names · 1 SANs
  • ocaccess.blog

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-10-17 11:34:34 UTC

Primary outcome Desconhecido reason: Probe Inconclusive 20% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Desconhecido Probe Inconclusive 20% 2026-10-17 11:34:34 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-17 11:34:34 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Tecnologias · 8 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

1 / Os fornecedores de segurança 92 sinalizaram este domínio
View on VT
Last analyzed Previous stored snapshot: 1 detection
CRDF
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of dapp.ocaccess.blog · checked Oct 17, 2026

60
Needs Work
Performance
FCP
1.95s
First Contentful Paint
LCP
10.81s
Largest Contentful Paint
CLS
0.179
Cumulative Layout Shift
TBT
161ms
Total Blocking Time
SI
4.91s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://dapp.ocaccess.blog/
Final URL: https://dapp.ocaccess.blog/home
OC.AGENT — AI Prediction Market Infrastructure
World's 1st AI Prediction Market Infrastructure
Resposta
HTTP 200
HTML body
22.5 KB
Compressed
5.0 KB
Links
0 internal · 0 external
Detected technologies
cloudflarereact
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
X-Powered-By: Next.js
Cache-Control: public, max-age=0, s-maxage=600, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 20
alt-svc
h3=":443"; ma=86400
Cache-Control
public, max-age=0, s-maxage=600, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a4bef98f6fa10cf2-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 17 Oct 2026 11:31:04 GMT
Link
; rel=preload; as="style", ; rel=preload; as="style", ; rel=preload; as="style", ; rel=preload; as="style"
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Permissions-Policy
geolocation=(), microphone=(), camera=(self)
Referrer-Policy
strict-origin-when-cross-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=UKZgtzh1Nxc2Z1wSxc8RTJOdXgKsvk%2FQ2d%2B0xuOP5BHs7uC71gEL5H%2FuWS9ZZRcXgf0ZuK3qYQrMRzV380DmDYUSyOGOM8NKxdKdzUGFSXZISTanx1kGaRvU42SYPCNde5%2B%2BD
Server
cloudflare
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
x-powered-by
Next.js

Values retained by the collector; long values may be shortened during collection.

Archived
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-17 11:31:04 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-17 11:31:04 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-17 11:31:04 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Análise de detecção e evasão

Verificação de cloaking e distribuição de tráfego

Ainda não foi digitalizado Ainda não foi registrada nenhuma diferença entre o rastreador e o navegador

Observações armazenadas comparando o rastreador com o navegador para este host, além de uma verificação em tempo real da assinatura digital para sistemas de distribuição de tráfego do tipo Keitaro.

Sinalizador de camuflagem armazenado
Ainda não foi digitalizado
Roteamento de captura
Local arquivado em 2026-10-17 11:31:04 UTC
Verificação de impressão digital “TDS” em tempo real
Sete indicadores do Keitaro e uma comparação entre navegador e rastreador. Uma nova análise começa somente ao pressionar o botão.
Sob demanda

Nenhum resultado desta verificação foi salvo.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-10-17 11:30:44 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Desconhecido

    stale_current_evidence

  2. Availability monitor · First collection record

    Acessível

Pipeline de resposta a ameaças

Descoberta
Analysis
Monitoring

9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Ameaça detectada
dapp.ocaccess.blog detectados e colocados na fila para análise completa
17/10/2026
URLScan.io Capture
Armazenado URLScan report with capture artifacts
17/10/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
1/92 recorded on VirusTotal
17/10/2026
Detecção de lista de bloqueio
Encontrado em 1 blocklist: ScamSniffer
17/10/2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
17/10/2026
Technical Analysis Recorded
O relatório contém tecnologia armazenada ou resultados de análises forenses.
17/10/2026
Lista de Destruição Publicada
Listed in the public PhishDestroy/DestroyList repository
17/10/2026
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecAvaliação do site AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Domínios semelhantes

79 domínios semelhantes armazenados

etamask.io omission Relatório interno meetamask.io repetition Relatório interno megamask.io replacement Relatório interno metam.ask.io subdomain Relatório interno metamaak.io replacement Relatório interno metamadk.io replacement Relatório interno metamaks.io transposition Relatório interno metamassk.io insertion Relatório interno metamsask.io insertion Relatório interno metamssk.io replacement Relatório interno metanask.io homoglyph Relatório interno metanmask.io homoglyph Relatório interno
Mostrar tudo (67)
metasmask.io insertion Relatório interno metramask.io insertion Relatório interno mewtamask.io insertion Relatório interno mmetamask.io homoglyph Relatório interno mtamask.io omission Relatório interno mwetamask.io insertion Relatório interno nmetamask.io homoglyph Relatório interno metamark.io bitsquatting Relatório interno metamaskj.io addition Relatório interno metammask.io homoglyph Relatório interno metamnask.io homoglyph Relatório interno emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidências e relatórios externos

Análise de Segurança
URLScan Stored capture VirusTotal 1 det. ChainPatrol URLQuery SSL Laboratórios Certificate hostname mismatch CF Radar Abrir relatório WOT ScamAdviser Verificador de lista negra URLVoid Sucuri SiteCheck Observatório MDN
OSINT e Inteligência
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificados WHOIS Wayback
DNS e Rede
nslookup.io DNS bgp.tools ASN /Rota
SEO e domínio
SpyFu Moz DA/PA Ahrefs Links de retorno
Análise aprofundada
Análise aprofundada

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Você foi afetado por este site?

3 evidence signal groups linked 0 stored notification records Não verificado

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Não é um relatório de aplicação da lei
Recurso de domínio
Solicite uma revisão se você possui este domínio e acredita que a listagem está incorreta
Cuidado com os golpistas que prometem recuperação! Os criminosos podem entrar em contato novamente com as vítimas fingindo ser investigadores, advogados ou agentes de recuperação. Não pague taxas antecipadas nem compartilhe credenciais. Saiba mais sobre fraudes relacionadas à recuperação →
Notifique as autoridades locais

Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.

Diretório de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Rascunho assistido por IA – os detalhes do incidente são processados pelo provedor de IA · Revise e envie você mesmo
After a phishing incident

Recomendações e orientações para as vítimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

O que devo fazer agora mesmo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alterar todas as senhas — e-mail, contas do Exchange, qualquer coisa que use a mesma senha
  • Ativar a autenticação de dois fatores usando um aplicativo autenticador (não por SMS). Desative a recuperação por SMS
  • Cartões de congelamento se você inseriu dados bancários no site de phishing

Que informações devo coletar para o meu relatório?

Diretrizes do FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Datas e horários exatos — de cada transação e do primeiro contato com o golpista
  • Capturas de tela — sites fraudulentos, mensagens de bate-papo, e-mails, transações em carteiras digitais, redes sociais
  • Todas as URLs e domínios utilizado pelo golpista (incluindo dapp.ocaccess.blog)
  • Comunicações — e-mails, mensagens de texto, números de telefone e nomes de usuário que o golpista utilizou

Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.

A quem devo denunciar o golpe?

  • FBI IC3 — Centro de Denúncias de Crimes na Internet (sistema federal de denúncias dos EUA)
  • Europol — Relatórios sobre crimes cibernéticos na Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polícia local — cria um registro oficial, mesmo que não possam agir imediatamente

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Abate de suínos — confiança construída ao longo de semanas pelo Telegram, WhatsApp e aplicativos de namoro; em seguida, o dinheiro foi roubado
  • Golpes relacionados à recuperação — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Golpes baseados em IA — deepfakes, phishing automatizado e sites gerados por IA, o que torna a fraude mais difícil de detectar

Como posso me proteger no futuro?

  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Verificar domínios — verificar PhishDestroy antes de interagir. Verifique se o site usa HTTPS, a ortografia e a idade do domínio
  • "Bom demais para ser verdade" = golpe — retornos garantidos, endossos de celebridades, prazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Verificar qualquer domínio

Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública

Digitalize agora

Denunciar phishing

Envie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade

Denunciar

Feed de ameaças em tempo real

Relatórios recentes de phishing e alterações de disponibilidade observadas

Monitorar

Mantenha-se informado, mantenha-se seguro

Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo

Feed de ameaças em tempo real Recorrer deste anúncio
Read the evidence in context

Sobre este relatório: dapp.ocaccess.blog

Este relatório apresenta as últimas evidências armazenadas disponíveis para PhishDestroy. Os carimbos de data/hora de origem são mostrados quando disponíveis; a disponibilidade e os veredictos do fornecedor podem mudar após a coleta.

O site capturado exibia o título da página “OC.AGENT — AI Prediction Market Infrastructure” e pode estar se passando por MetaMask.

A partir de 2026-10-17 19:06:47 UTC, dapp.ocaccess.blog tinha detecções de mecanismos de segurança 1.

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Se você acredita que esta listagem é imprecisa, enviar um recurso. Para conhecer nossa metodologia, acesse o Página de perguntas frequentes.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Incorporar este relatório

Compartilhe essas informações sobre ameaças em seu site ou blog

embed.html 
<iframe
  src="https://phishdestroy.io/pt-br/embed/domain/dapp.ocaccess.blog"
  title="PhishDestroy threat report for dapp.ocaccess.blog"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>