Aller au rapport de sécurité
Tableau de bord analytique
Domain security report
pumpz.top favicon

pumpz.top

“Pump”

Verdict de menace
CritiqueRecours en matière de nom de domaine
Assessment sources

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

Disponibilité Contenu indisponible Le contenu n'était pas disponible dans la dernière observation Observé · HTTP probe
Signaux de risque
Détections VirusTotal : 8/89 Correspondances de la liste de blocage stockée : 3 URLQuery threat systems: 1 alert Automated brand label: Blast
OTX: 4 refs 07/09/2026 Blast 1 Report Sent CDN
API
Bureau d’enregistrement
NameSilo
Resolved IP
172.67.223.78
Registered
04/09/2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 8. Listes de blocage publiques signalant une correspondance : 3. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
Résumé du rapport

pumpz.top — Contenu indisponible. Usurpation de l'identité de la marque : Blast; Type d'arnaque : Crypto Drainer. Résumé des preuves: VirusTotal 8/89 (alphaMountain.ai, CRDF, Emsisoft, Fortinet, Gridinsoft); URLQuery 1 alert; URLScan malicious verdict; 3 external blocklist matches (MetaMask, ScamSniffer, SEAL); PhishDestroy score 100/100. Bureau d’enregistrement: NameSilo.

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

Additional indicators at a glance

VirusTotal
VirusTotal
8 det.
URLQuery
URLQuery
1 threat alert
OTX references
4 community refs
URLScan
URLScan
Signaler ↗
Certificat TLS
Expired or unverified dates
Google Trust Services / WE1 · Hostname coverage not recorded
Âge
1 mo New
Statut observé
Contenu indisponible
PhishDestroy
DestroyList
Répertorié
Reports Sent
1

Source evidence

8 · 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

8 / 89

Signaler
Interpretation & limits

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

URLQuery

1 threat-system alert

Signaler
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

URLScan verdict

malicious

Signaler
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Public blocklists

3 external matches

Détails
Interpretation & limits

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

OTX

4 community references

Signaler
Interpretation & limits

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

CF Radar

provider verdict: clean

Observation time not recorded
Signaler
Interpretation & limits

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

URLScan capture

rapport stocké

View stored capture ↗
Signaler
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

Signaler
Interpretation & limits

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

Renseignements sur la sécurité réseau Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
DNS4EU pumpz.top malicious Sinkholed
Stored URLQuery scan evidence · Sep 7, 2026 00:46 UTC Open source report
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer:

Résumé des preuves

Critique
VirusTotal
8/89
OTX
4 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

Stored evidence for pumpz.top: VirusTotal recorded 8 detections among 89 scanners on 2026-09-07. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for pumpz.top. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence

VirusTotal records 8 detections among 89 scanners in the stored snapshot dated 2026-09-07. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-07 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

MetaMask and SEAL are recorded as named external blocklist observations for pumpz.top in the snapshot dated 2026-09-07. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains pumpz.top as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed pumpz.top on 2026-09-07. The MetaMask and SEAL blocklist snapshot is dated 2026-09-07 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-04. A URLScan reference was stored on 2026-09-07 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

For pumpz.top, the registrar field records NameSilo, LLC; this is kept as an exact source value. The source stores 172.67.223.78 as the observed address in this record. The registration date for pumpz.top is recorded as 2026-09-04. The SSL issuer is recorded as Google Trust Services / WE1 in the snapshot dated 2026-09-07. The stored ASN observation records AS13335 and CLOUDFLARENET - Cloudflare, Inc., US in this record. The observed server header is recorded as cloudflare in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The pumpz.top record states that VirusTotal recorded 8 detections among 89 scanners on 2026-09-07. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-07. PhishDestroy remains a separate publisher catalogue entry in the stored record. For pumpz.top, the registrar field records NameSilo, LLC; this remains separate from the other source fields. The observed address field in this record contains 172.67.223.78. The supported conclusion is bounded to the exact stored observations for pumpz.top. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to pumpz.top during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain pumpz.top as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to pumpz.top. The stored record does not justify extending that rule to 172.67.223.78 or to other infrastructure records.

Data coverage & collection

20 · datasets with records / 11 · 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
8 / 89 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
2 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
3 · external matches
Cloudflare Radar
sainCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
NameSilo, LLCCollection time not recorded
Network & DNS
172.67.223.78 · 2 · nameserversCollection time not recorded
Certificat TLS
Google Trust Services / WE1
Page captures
3 · retained captures
Page analysis
11 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
78/100 · mobile performance
Response records
1 · outgoing report records
Availability history
15 · stored state changes
Source observation history
7 · stored source events
IP reputation
Network-level observations
Not recorded in this report 11

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

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Lookalike relationships
  • Signalements communautaires
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

3 · external source matches

Statut de la liste de blocage publique

Domain, network & archive

NameSilo, LLC · 172.67.223.78 · DNS, TLS and retained responses

Domain details

Domaine
URLScan verdict Malveillant score 100 Phishing report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement NameSilo US(US) PhishDestroy Investigation
Contact anti-abusabuse@namesilo.com
Registre de l'ICANNICANN Lookup (RDAP) →
Recherche WHOISICANN RDAP pour pumpz.top →
EnregistrementCréé 04/09/2026 (41d · New) — Expires 04/09/2027
Délai avant la première indisponibilité 4 days
Ce que nous comptons Temps écoulé entre le premier rapport d'abus stocké et la première observation indiquant que le contenu n'était pas disponible. Cela n’établit pas la cause.
Ce que contient chaque rapport Les enregistrements de rapports sortants stockés peuvent faire référence à des preuves disponibles à ce moment-là, telles que les verdicts des fournisseurs, les données d'enregistrement, les détails d'hébergement, les classifications ou les captures d'écran. Cette page ne déduit pas la charge utile exacte livrée, la réception, l'accusé de réception ou l'action d'un destinataire.
Détails techniquesProvenance & timestamps
Première détection07/09/2026
DOM Analysisanalyzed 07/09/2026score 80/10011 brand signals
Submitted URLhttp://pumpz.top/
Favicon Hash
ID du dossier
ICANN OVERSIGHT

Contexte de l’accréditation et du 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.

Une accréditation est un contrat, pas un label de sécurité. Vérifier les frais de l’ICANN Lire le RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.223.78
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

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

Serveurs de noms 2
  • bailey.ns.cloudflare.com
  • piotr.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Google Trust Services / WE1
Valid from
2026-09-04 21:52:41
Valid until
2026-12-03 22:51:26
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-09-07 01:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb4ed227917067c71a4ba4c2546744bb72dd1f525123cbe2aa2768ebc5b3d29af

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

viewdns.info · 172.67.223.78rapiddns.io

Latest Classified Outcome 2026-10-15 20:22:19 UTC

Primary outcome DNS inactif reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Inconnu Probe Inconclusive 20% 2026-10-15 01:12:45 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-09-07 22:14:34 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-07 22:14:34 UTC → 2026-09-30 16:14:55 UTC · 546.01h midpoint estimate ≈ 2026-09-19 07:14:44 UTC · precision low · basis bounded
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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

8 / Les fournisseurs de sécurité 89 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
alphaMountain.ai
CRDF
Emsisoft
Fortinet
Gridinsoft
Kaspersky
Netcraft
SOCRadar
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of pumpz.top · checked Sep 7, 2026

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

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
546.01
Estimate basis
Bounded by observations
Estimate precision
Low

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

Analyse de la détection et de l'évasion

Vérification du cloaking et de la répartition du trafic

Pas encore numérisé Aucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée

Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.

Indicateur de camouflage enregistré
Pas encore numérisé
Dernier scan de camouflage

Note relative à la numérisation: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='pumpz.top', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOCK

Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro et une comparaison entre navigateur et robot. Une nouvelle analyse démarre uniquement en cliquant sur le bouton.
Résultat enregistré
Inaccessible

Timeline & response

1 · outbound report records

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. Domain Status Transition 2026-09-10 22:04:34 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. VirusTotal Detections Update 2026-09-07 13:40:12 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: Gridinsoft.
  3. VirusTotal Detections Update 2026-09-07 07:31:13 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: CRDF.
  4. VirusTotal Detections Update 2026-09-07 04:56:00 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: SOCRadar.
  5. VirusTotal Detections Update 2026-09-07 03:21:22 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: alphaMountain.ai.
  6. VirusTotal Detections Update 2026-09-07 01:16:16 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 0 to 4. Added scanner alerts: Emsisoft, Fortinet, Kaspersky, Netcraft.
  7. Threat First Observed 2026-09-07 00:43:18 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.223.78.
Stored observation history22

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

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  3. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  5. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

Earlier observations 17
  1. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  2. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  4. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Inconnu

    origin_unreachable · http_5xx

  6. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    dns_inactive→Inconnu

    origin_unreachable · http_5xx

  8. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    dns_inactive→Inconnu

    origin_unreachable · http_5xx

  10. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    Accessible→Indisponible

  12. VirusTotal · Detection count

    7→8

  13. VirusTotal · Detection count

    6→7

  14. VirusTotal · Detection count

    5→6

  15. VirusTotal · Detection count

    4→5

  16. VirusTotal · Detection count

    0→4

  17. Availability monitor · First collection record

    Accessible

Processus de réponse aux menaces Pipeline

Découverte
Analysis
Notifications
Monitoring

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

Menace détectée
pumpz.top détectés et mis en file d'attente en vue d'une analyse complète
07/09/2026
URLScan.io Capture
Enregistré URLScan report with capture artifacts
07/09/2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
07/09/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
8/89 recorded on VirusTotal
07/09/2026
Détection des listes noires
Trouvé dans 3 blocklists: MetaMask, ScamSniffer, SEAL
16/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
07/09/2026
Registrar Context: NameSilo
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Brand Impersonation
Impersonation of Blast
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
07/09/2026
Technical Analysis Recorded
Le rapport contient des résultats de technologie ou d’analyse médico-légale stockés.
16/10/2026
Content Observed Unavailable
La surveillance a enregistré une réponse indisponible ; la cause n’a pas été établie de manière indépendante.
11/09/2026
VT Detection +1
+1 new detection (7 → 8): Gridinsoft
07/09/2026
VT Detection +1
+1 new detection (6 → 7): CRDF
07/09/2026
VT Detection +1
+1 new detection (5 → 6): SOCRadar
07/09/2026
VT Detection +1
+1 new detection (4 → 5): alphaMountain.ai
07/09/2026
VT Detection +4
+4 new detections (0 → 4): Emsisoft, Fortinet, Kaspersky, Netcraft
07/09/2026
Sent Report Recorded
Stored outgoing record associated with registrar NameSilo, LLC, 1 abuse contact
abuse@namesilo.com
07/09/2026
DestroyList publié
Listed in the public PhishDestroy/DestroyList repository
07/09/2026
Content Observed Unavailable
Les dernières vérifications stockées indiquent que le contenu signalé n'est pas disponible ; cela n’établit pas qui ou quoi a causé le changement.
11/09/2026
Délai avant la première indisponibilité
93 heures se sont écoulées entre la détection et la première observation indisponible.
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 SymantecÉvaluation du 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

Evidence & investigation tools

Original reports, independent checks and evidence links

Données factuelles et rapports externes

Analyse de sécurité
URLScan Malveillant VirusTotal 8 det. ChainPatrol URLQuery 1 threat alert SSL Laboratoires Hostname coverage not recorded CF Radar Ouvrir le rapport OTX 4 refs WOT ScamAdviser Vérificateur de liste noire URL nulle Sucuri SiteCheck Observatoire MDN
Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260907-788367 Recipient: abuse@nic.top
Page title stored with report: Pump
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.
OSINT et renseignement
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificats WHOIS Wayback
DNS et réseau
nslookup.io DNS bgp.tools ASN /Itinéraire
Référencement naturel et nom de domaine
SpyFu Moz DA/PA Ahrefs Liens entrants
Analyse approfondie
Analyse approfondie

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Ce site vous a-t-il affecté ?

6 evidence signal groups linked 1 stored notification records Contenu indisponible
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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Pas un rapport des forces de l'ordre
Recours en matière de nom de domaine
Demandez un examen si vous possédez ce domaine et pensez que la liste est incorrecte
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 pumpz.top)
  • 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

Vérifier n'importe quel domaine

Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique

Scanner maintenant

Signaler une tentative d'hameçonnage

Signalez les domaines suspects à notre base de données des menaces — protégez la communauté

Signaler

Flux d'alertes en temps réel

Rapports de phishing récents et changements de disponibilité observés

Surveiller

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
Read the evidence in context

À propos de ce rapport : pumpz.top

Ce rapport présente les dernières preuves stockées disponibles pour PhishDestroy. Les horodatages sources sont affichés lorsqu'ils sont disponibles ; la disponibilité et les verdicts des fournisseurs peuvent changer après la collecte.

Le site capturé affichait le titre de la page “Pump” et usurpait peut-être l'identité de Blast.

Depuis 2026-09-07 14:44:03 UTC, pumpz.top avait des détections provenant des moteurs de sécurité 8.

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.

Si vous pensez que cette liste est inexacte, déposer un recours. Pour en savoir plus sur notre méthodologie, visitez le Page FAQ.

Embed this report

A 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/pumpz.top"
  title="PhishDestroy threat report for pumpz.top"
  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>