This phishing domain has been taken down
Confirmed dead — kept on record for forensic reference and similar-pattern matching.

t-mobile.pbuof[.]cc

Domain Security & Threat Intelligence Report
12/12 VT Taken Down May 17, 2026 1 Blocklist 1 Report Sent Taken Down HTTP 530
REF B5B45D8B SCORE 73/100 ENGINE PD-4 Turbo Appeal listing
0 Risk Score
Data coverage VirusTotal 12 / 12 URLQuery no det. OTX no pulses CF Radar pending URLScan report ready DNS blocks none SSL invalid WHOIS 85d old Screenshot captured Redirect chain no redirect CDN bypass not suspended
VirusTotal
12 det.
URLQuery
no det.
OTX
no pulses
CF Radar
pending
URLScan
Report ↗
DNS Security
no dets
Gridinsoft
SSL
Age
85d
Status
Dead
DestroyList
Listed
Reports Sent
1
02

Forensic brief

auto-generated · PhishDestroy AI
PhishDestroy AI
probe: May 17, 2026
score: 73/100
vendors12/12
blocklists1
Analyst brief · auto-generated

PhishDestroy has identified t-mobile.pbuof.cc as an active phishing domain posing a significant threat to user security. This malicious site attempts to steal sensitive information by impersonating legitimate T-Mobile services, putting users at risk of credential theft and potential financial loss. Due to its deceptive nature, it is critical for users and organizations to remain vigilant against this threat. The domain t-mobile.pbuof.cc was registered recently on February 21, 2026, and currently resolves to the IP address 188.114.96.3. It has been flagged by 12 out of 95 security vendors on VirusTotal and appears on one security blocklist, indicating a recognized risk among cybersecurity communities. Despite these detections, the domain remains active, suggesting ongoing phishing campaigns that may be targeting unsuspecting victims. Users are strongly advised to avoid interacting with this domain or entering any personal information on associated websites. Employing robust email filtering, enabling multi-factor authentication, and verifying URLs before clicking are essential steps to mitigate exposure to this phishing threat. Organizations should update their blocklists to include t-mobile.pbuof.cc and educate employees about recognizing phishing attempts to reduce the chance of compromise.

Phishing
03

Threat response pipeline

May 17, 2026 · 1 report submitted
Discovery
Submission
Legal
Takedown
12/19
30+ Proprietary Parsers
Distributed scanning of Google Ads, SEO-manipulated results, Twitter/X, YouTube & Telegram campaigns.
Infrastructure Analysis
dnstwist & typosquatting detection.
Community Intelligence
Real-time ingestion via Telegram Bot & partner intelligence feeds.
Threat Ingested
t-mobile.pbuof.cc detected and queued for full analysis.
May 17, 2026
60+ Vendor Submissions
Threat data submitted to 60+ security vendors & threat-intel platforms. 12 flagged this domain.
VirusTotal
12 / 12 vendors flagged on VirusTotal.
Blocklist Detection
Found in 1 blocklists: PhishDestroy.
Forensic Evidence Collection
URLScan.io, URLQuery & Cloudflare Radar — DOM snapshots, HTTP transactions, DNS & certificate data.
Registrar & Hosting Notification
Abuse report sent to with forensic evidence (metadata, screenshots, PDF).
DestroyList Published
Added to PhishDestroy/DestroyList — open-source blocklist for wallets & extensions.
Abuse Reports Sent (1)
1 abuse reports filed; 0h elapsed since first report.
Open Threat Database
Real-time commits to GitHub repository & live monitoring at phishdestroy.io/live.
Social Broadcasting
Automated alerts on X, Telegram & Mastodon.
Confirmed dead
Domain confirmed taken down.
May 17, 2026
04

Evidence capture

urlscan snapshot · domain intelligence
08

Public blocklist status

cross-vendor confirmation
1
Listed in 1 public blocklist — confirmed by independent sources
Sources with no listing are omitted.
10

VirusTotal consensus

12 vendors · 3-col matrix
12/12
vendors flagging
Unanimous malicious verdict

Aggregated detection across 12 security vendors.

Per-vendor breakdown not available — view raw report on VirusTotal ↗
12

Evidence & external reports

cross-reference this domain
14

Were you affected by this site?

immediate response · authorities

Were You Affected?

You are not alone and there is nothing to be ashamed of. Reporting is the most powerful weapon against fraud — your report can prevent others from becoming victims.
Beware of recovery scammers! No legitimate service will ask for upfront payment to recover stolen crypto. Learn more about recovery fraud →

Recommendations & Advice for Victims

  1. Do not pay anything else. Recovery agents demanding upfront fees are a second-stage scam.
  2. Disconnect compromised wallets. Move remaining funds to a fresh seed phrase generated offline.
  3. Preserve evidence. Screenshot transactions, save URLs, archive emails — chain-of-custody matters for prosecution.
  4. Report to authorities (see section 15 below) — even small reports help build case patterns.
  5. Notify your bank/exchange. Some chargebacks may still be possible within 24-72h.
ICANN RAA §3.18 DMCA §512 GDPR Art.17 FBI guidelines SEAL-ISAC
15

Report to your local authorities

geo-aware · authorities · AI complaint
Your country (auto-detected)
United States

  Email template — registrar abuse

To: abuse@ Case: PD-
Open in mail client Appeal (if false-positive)
16

Embed this report

iframe · sizer · CC-BY

Embed this report

Drop a live, self-updating risk widget anywhere — blog, DAO forum, Discord webhook, X post. Free, no API key, CC-BY.

t-mobile[.]pbuof[.]cc 73/100 TAKEN DOWN · 12/12 VT · 0h View full report ↗
Live preview at 100% width
Canonical: https://phishdestroy.io/domain/t-mobile.pbuof.cc/ JSON API llm.txt
17

About this report

methodology · appeals · API

About this report: t-mobile.pbuof.cc

This domain security report is maintained by PhishDestroy's automated threat-intelligence pipeline. Our system continuously monitors this domain across 12 security vendors on VirusTotal and 1 public blocklists.

t-mobile.pbuof.cc has been flagged by 12 security vendors as of May 17, 2026.

If you believe this listing is inaccurate, you can submit an appeal. For more information about our methodology, visit our FAQ page.