Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
claim-project.com favicon

claim-project.com

“CLAIM — find out what actually happened”

Bureau d’enregistrement
Name.com
Resolved IP
216.198.79.65
Registered
22/09/2026
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 10/92 Correspondances de la liste de blocage stockée : 2 Libellé de marque automatique : MetaMask Domaine jeune : 27 jours
25/09/2026 1 Report Sent CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 10. Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
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@name.com. The latest stored availability evidence still shows the domain reachable; 25 days 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
25 days
Reports sent
1
Latest case ID
PD-20260925-02DCCB
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
Page captures
open gallery
Domain age
Reports sent
view timeline
Résumé du rapport

Usurpation de MetaMask: claim-project.com — Dernier actif connu (HTTP 200). Résumé des preuves: VirusTotal 10/92 (alphaMountain.ai, BitDefender, CRDF…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 10 / 92 6 sources

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

Analysis

Critique
VirusTotal
10 / 92
Page captures
3

PhishDestroy threat report

Overview

claim-project.com is an impersonation phishing page that presents itself under the heading "CLAIM — find out what actually happened." Its presence on the MetaMask and SEAL blocklists points to crypto wallet users as the intended audience. PhishDestroy first detected it on 2026-09-25. As of 2026-10-19 the site was still online and serving its content. The page title reads like an informational or investigative page, while we classify the site as impersonation phishing.

How the scam works

The name and headline combine two common hooks: a "claim" of something owed and an offer to explain an event the visitor may be worried about. Impersonation pages of this kind borrow the look or name of a trusted project to seem legitimate. They then steer visitors toward an action that hands over control, usually connecting a wallet, signing a transaction, or entering recovery details. Once that happens, the operators can move the victim's assets, and blockchain transfers cannot be reversed.

Evidence

On 2026-10-07, 10 of 92 VirusTotal engines flagged the domain. The vendors include Kaspersky, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is a minority of engines, but these vendors run independent detection pipelines, so their agreement carries weight. The listings by MetaMask and SEAL matter most for crypto users, because wallet-side protections draw directly on those lists.

Infrastructure

The domain was registered on 2026-09-22 through Name.com, Inc., only three days before PhishDestroy caught it. That short gap is typical of sites built for a quick campaign. It resolves to Amazon.com, Inc. infrastructure in the US, so it sits on mainstream cloud hosting rather than a niche provider.

What to do

Do not follow any "claim" process or answer prompts on this site. If you connected a wallet or signed anything there, use a token-approval checker to revoke permissions you granted. Move any remaining funds to a new wallet whose seed phrase has never been entered on a website. If you typed in a seed phrase or private key, treat that wallet as compromised and empty it immediately. Defenders should block the domain at DNS and proxy level, search logs for earlier visits, and report it to the registrar and hosting provider while the site remains live.

Extracted from stored page analysis

Observed indicators

0 wallet · 4 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/claim_care_botStored page reference
Telegram
https://t.me/claim_projectStored page reference
Telegram
https://t.me/claim_project_supportStored page reference
Telegram
https://t.me/kris_claimStored page reference

IoC extraction recorded 2026-09-26 04:00:19 UTC

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Répertorié View source
PhishDestroy PhishDestroy list View source
SEAL Répertorié View source

Last checked

Capture enregistrée · 3 captures

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Vercel shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
Bureau d’enregistrement Name.com US(US)
Contact anti-abusabuse@name.com, abuse@vercel.com
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 22/09/2026 (27d · Very New!) — Expires 22/09/2027
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection25/09/2026
DOM Analysisanalyzed 09/10/2026score 100/1001 brand signal
IoC Extractionscanned 26/09/20260 wallet · 4 Telegram IoCs
Submitted URLhttp://claim-project.com/
Favicon Hash
ID du dossier
Observed page title
CLAIM — find out what actually happened
Automated brand references
Telegram
Certificat TLS
Émis par Let's Encrypt / YR2 · stored validity ends in 62 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.198.79.65
Network ASN
AS16509
Organization
CYPRESS COMMUNICATIONS, LLC
Observed location
Cleveland, US
Server header
Vercel

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 2

  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-09-23 03:28:43
Valid until
2026-12-22 03:28:42
Validity
Within stored validity dates
Collection time
2026-10-11 04:03:41 UTC
Collection source
PhishDestroy collector
Certificate fingerprint4de59d4a92994dc300d721908fb02fdee8c4f75b8a5a21904188ce8e7fdc0d37

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:27:42 UTC

Primary outcome Contenu actif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenu actif Ordinary HTTP content served 90% 2026-10-19 22:27:42 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:35:30 UTC last content: 2026-10-19 22:27:42 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.claim-project.comDomain record

The original observation time is not recorded for these hostnames.

Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

10 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar
Sophos

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of claim-project.com · checked Sep 25, 2026

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

Availability observations

Last reachable observation
Last content 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.

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

    Inconnu→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

Earlier observations 13
  1. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  6. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  7. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  8. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  9. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  10. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  11. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  12. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  13. Availability monitor · First collection record

    Accessible

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    10/92 engine detections

    View source
  3. Abuse report sent

    PD-20260925-02DCCB

    abuse@name.com
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    claim-project.com

    View source

Domaines ressemblants

79 domaines ressemblants enregistrés

Tout afficher (67)
metasmask.io insertion Rapport interne metramask.io insertion Rapport interne mewtamask.io insertion Rapport interne mmetamask.io homoglyph Rapport interne mtamask.io omission Rapport interne mwetamask.io insertion Rapport interne nmetamask.io homoglyph Rapport interne metamark.io bitsquatting Rapport interne metamaskj.io addition Rapport interne metammask.io homoglyph Rapport interne metamnask.io homoglyph Rapport interne 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

Check for cloaking

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

claim-project.com

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260925-02DCCB Recipient: abuse@name.com
Page title stored with report: CLAIM — find out what actually happened
PDF notice generated Notice text archived (653 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (US):
18 U.S.C. § 1343 - Wire Fraud
18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA)
15 U.S.C. § 45 - FTC Act (Deceptive Practices)
Federal laws prohibit wire fraud, computer fraud, and deceptive business practices.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

5 evidence signal groups linked 1 stored notification records Dernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

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

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

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

Que dois-je faire tout de suite ?

Urgent

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

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du 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.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment claim-project.com)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

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?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

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

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
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

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/claim-project.com"
  title="PhishDestroy threat report for claim-project.com"
  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>