Ir para o relatório de segurança
Segurança de domínio e inteligência contra ameaças
phantom-app.services favicon

phantom-app.services

“403 Forbidden”

Registrador
Dynadot
Resolved IP
172.67.179.233
Registered
01/09/2026
PhishDestroy assessment Crítico
Disponibilidade Acessível · acesso restrito Resposta alcançável; o conteúdo da página não foi verificado Observado · HTTP probe
Detecções do VirusTotal: 15/89 Spamhaus DBL: DBL_PHISH Correspondências da lista de bloqueio armazenada: 2 Rótulo automático de marca: Phantom Último ativo conhecido
OTX: 4 refs 02/09/2026 1 Report Sent CDN
API
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 15. Listas de bloqueio públicas relatando uma correspondência: 2. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@dynadot.com. The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260902-4FDACD
Current status
HTTP 403 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Resumo do relatório

Drainer de carteiras cripto: phantom-app.services — Acessível · acesso restrito (HTTP 403). Resumo das evidências: VirusTotal 15/89 (alphaMountain.ai…

A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.

Source evidenceVirusTotal 15 / 89 · OTX 4 references 8 sources

Spamhaus DBL

DBL_PHISH

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Crítico
VirusTotal
15 / 89
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

phantom-app.services is a crypto drainer site built to impersonate Phantom, the widely used Solana wallet application, with the goal of stealing cryptocurrency from Solana users who believe they are interacting with a legitimate service. PhishDestroy first identified it on 2026-09-02, just one day after the domain was registered, indicating it was flagged almost immediately upon deployment. As of 2026-10-18 the site remains alive and reachable, meaning it is still an active threat to anyone who encounters it.

How the scam works

The site deploys a Solana Drainer kit, a category of malicious tooling that prompts visitors to connect their Solana wallet under the pretense of accessing a legitimate Phantom feature or service. Once a wallet is connected, the kit requests transaction approvals or signing permissions that silently authorize the transfer of tokens and NFTs out of the victim's wallet to attacker-controlled addresses. The victim can lose their entire Solana holdings, including SPL tokens and NFTs, in a matter of seconds. The page currently returns a 403 Forbidden title, which conflicts with the active drainer classification; the site is nonetheless confirmed reachable and malicious by multiple independent sources.

Evidence

Fifteen of 89 engines on VirusTotal flagged this domain as malicious as of 2026-09-12, with detections from BitDefender, ESET, Emsisoft, Fortinet, G-Data, Gridinsoft, CRDF, and alphaMountain.ai among others. urlscan.io returned a malicious verdict and associated the domain with generic crypto brand abuse. Spamhaus lists it under DBL_PHISH, its dedicated phishing category. The domain also appears on the PhishDestroy, MetaMask, and SEAL blocklists, and has accumulated four threat pulses on OTX.

Infrastructure

The domain was registered on 2026-09-01 through Dynadot Inc and was weaponized within 24 hours. It is hosted on Cloudflare's network, with the hosting node geolocated to Canada. The TLS certificate was issued by Google Trust Services under the WE1 intermediate, giving the site a padlock that lends it a superficial appearance of legitimacy.

What to do

If you visited this site and connected a Solana wallet, immediately revoke all token approvals and spending permissions granted to unknown programs using a Solana approval-management tool. Move remaining funds to a fresh wallet address that has never interacted with this site. If you signed any transactions, assume those assets are lost and report the incident to your wallet provider. Security teams and defenders should ensure phantom-app.services is blocked at the DNS and proxy layer and add it to internal threat-intelligence feeds.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listado View source
PhishDestroy PhishDestroy list View source
SEAL Listado View source

Last checked

Captura armazenada · 3 captures

Observed page title
403 Forbidden
Automated brand references
Phantom
Certificado TLS
Emitido por Google Trust Services · stored validity ends in 89 days

Domain details

Domínio
URLScan verdict Malicioso score 100 Phishing report ↗
IP Context Cloudflare shared edge origin IP hidden A reputação do Edge-IP não é atribuída a este domínio.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomíniosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Dynadot (Unknown)
Contato para abusosabuse@dynadot.com
Registro da ICANNICANN Lookup (RDAP) →
RegistroCriado 01/09/2026 (48d · New) — Expires 01/09/2027
Status HTTP403 Forbidden
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez02/09/2026
DOM Analysisanalyzed 09/10/2026score 100/1001 brand signal
Submitted URLhttp://phantom-app.services/
Favicon Hash
ID do caso
ICANN OVERSIGHT

Credenciamento e contexto RAA

Registrar accreditation and DNS abuse obligations

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.

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.

Accountability draft Nada é enviado automaticamente.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.179.233
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

  • dalary.ns.cloudflare.com
  • steven.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Google Trust Services
Valid from
2026-09-01 16:25:57
Valid until
2026-11-30 17:24:44
Validity
Within stored validity dates
Collection time
2026-10-10 22:03:00 UTC
Collection source
PhishDestroy collector
Certificate fingerprint265412019eefb992f699120cc7776bf0a739a51990dff2cbec20f8a1369d9969

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

Latest Classified Outcome 2026-10-19 22:18:29 UTC

Primary outcome Reachable but protected reason: HTTP access restricted 65% confidence
Attribution Cloudflare mechanism: Access Restriction source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected HTTP access restricted Cloudflare Access Restriction 65% 2026-10-19 22:18:29 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-19 22:18:29 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.
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

15 / Os fornecedores de segurança 89 sinalizaram este domínio
View on VT
Last analyzed First positive detection Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Netcraft
SOCRadar
Sophos
Webroot

Evidências arquivadas

Wayback Machine Snapshot
Um instantâneo histórico está disponível para revisão de evidências
View Archive
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of phantom-app.services · checked Sep 2, 2026

95
Good
Performance
FCP
2.22s
First Contentful Paint
LCP
2.55s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.22s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

phantom-app.services
Resultado salvo
Cloaked / Filtered
Stored observation history18

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→protected

    http_access_restricted · Cloudflare · access_restriction

  2. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  3. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  4. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  5. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

Earlier observations 13
  1. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  2. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  3. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  4. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  5. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  6. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  7. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  8. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  9. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  10. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  11. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  12. Availability monitor · Recorded state

    Desconhecido→protected

    http_access_restricted · Cloudflare · access_restriction

  13. Availability monitor · First collection record

    Acessível

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    15/89 engine detections

    View source
  4. Abuse report sent

    PD-20260902-4FDACD

    abuse@dynadot.com
  5. Added to PhishDestroy

    phantom-app.services

    View source
  6. URLScan

    Page captured

    View source

Domínios semelhantes

3 domínios semelhantes armazenados

phantom-app.com various phantomapp.com various phantomx.app addition

Evidências e relatórios externos

Instantâneo das evidências enviadas
Sent: Ledger records: 1 Case ID: PD-20260902-4FDACD Recipient: abuse@dynadot.com
Page title stored with report: phantom-app.services/
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Análise aprofundada
Denunciar
Help & reporting

Você foi afetado por este site?

7 evidence signal groups linked 1 stored notification records Acessível · acesso restrito
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se você interagiu com este domínio, inseriu informações pessoais ou conectou uma carteira de criptomoeda, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Official reporting routes

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. Nenhum serviço legítimo pode garantir a recuperação de criptografia roubada. 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.

Estima-se que $51 billion foram transferidos para carteiras de criptomoedas ilícitas em 2024 (source). Se você interagiu com phantom-app.services — aja agora.

Wallet-specific steps below apply if you connected a wallet, signed a transaction, or exposed a wallet secret.

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.

  • Revogar aprovações de tokens — use revoke.cash para revogar o acesso concedido a contratos inteligentes maliciosos
  • Transferir os fundos restantes para uma carteira totalmente nova. A carteira comprometida não é mais segura
  • 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

De acordo com o FBI, os detalhes mais importantes são os dados das transações:

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Endereços de criptomoedas — carteira do golpista (por exemplo, 0x5856...35985)
  • Valor e tipo de criptomoeda — valor exato (por exemplo, 1,02345 ETH, 0,5 BTC, 500 USDT)
  • ID da transação (hash) — o identificador único da transação na blockchain
  • 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 phantom-app.services)
  • 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)
  • Chainabuse — identificar carteiras suspeitas em bolsas e plataformas
  • Sua corretora de criptomoedas — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
  • 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.

Como os golpes envolvendo criptomoedas costumam funcionar?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Aprovações mal-intencionadas — Solicitações do tipo “conectar carteira” que permitem aos invasores gastar tokens sem limites
  • 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
  • Anúncios falsos e airdrops — Anúncios do Google e nas redes sociais, além de ofertas de “tokens grátis”, que acabam esvaziando a carteira
  • 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?

  • Use uma carteira de hardware (Ledger, Trezor). Nunca armazene grandes quantias em carteiras de navegador
  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Leia todas as aprovações — verifique as permissões antes de assinar. Rejeite aprovações ilimitadas
  • 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

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
About this reportSources, observation dates and corrections

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.

Embed this reportA 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/phantom-app.services"
  title="PhishDestroy threat report for phantom-app.services"
  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>