PhishDestroy first recorded t-prokg.com on 2026-09-04. Stored VirusTotal result: 9/92 engines flagged. Malicious: 7. Suspicious: 2. Analysis time (as stored): 2026-10-11 22:07 UTC. Retrieved (as stored): 2026-10-23 03:51 UTC. Listed by external blocklists: MetaMask, SEAL.
Page title: “T-Pro”
More about the sources
Recorded security signals
Stored VirusTotal result: 9/92 engines flagged. Malicious: 7. Suspicious: 2. Analysis time (as stored): 2026-10-11 22:07 UTC. Retrieved (as stored): 2026-10-23 03:51 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded t-prokg.com on 2026-09-04. Stored VirusTotal result: 9/92 engines flagged. Malicious: 7. Suspicious: 2. Analysis time (as stored): 2026-10-11 22:07 UTC. Retrieved (as stored): 2026-10-23 03:51 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 100/100). Registrar: Realtime. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
t-prokg.com ran a phishing page under the title "T-Pro", posing as a legitimate service to win the trust of crypto users. PhishDestroy first saw it on 2026-09-04 and classified it as impersonation. The site went offline on 2026-09-11. When we last checked on 2026-10-19, its DNS no longer resolved, so the domain was not reachable.
How the scam works
An impersonation page copies the name and look of a service the victim already uses, here presented as "T-Pro", so the visitor believes they are on the real site. It then asks for account credentials, recovery details or a wallet connection. Whatever is entered goes straight to the operators. Stolen logins let them take over accounts. A seed phrase or a signed wallet request can let them empty the wallet outright, and blockchain transfers cannot be reversed.
Evidence
VirusTotal returned 9 detections out of 90 engines on 2026-09-06, two days after our first sighting. The flagging vendors included BitDefender, Kaspersky, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai, CRDF and SOCRadar. That count is modest, but several major vendors reached the same verdict independently and quickly. MetaMask's and SEAL's crypto-focused blocklists also list the domain alongside PhishDestroy, and it appears in 3 AlienVault OTX threat pulses.
Infrastructure
The domain was registered on 2026-07-20 through Realtime Register B.V., roughly six weeks before PhishDestroy detected it. That gap is consistent with a domain set up in advance and then put into use. Traffic went through Cloudflare, Inc. (IP 188.114.96.3, located in CA), which hides the server actually hosting the content. The site stayed live for only about a week after detection before it went dark.
What to do
If you typed a password or email into this site, change that password on the genuine service and anywhere else you reused it. Then enable app-based 2FA. If you entered a seed phrase, treat that wallet as compromised and move any remaining funds to a new wallet created with a fresh phrase. If you connected a wallet or signed anything, review and revoke token approvals with a trusted approval-checking tool. Defenders should block t-prokg.com at DNS and proxy level and search logs for any visits to it after 2026-07-20.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
t-prokg.com — T-Pro Impersonation Phishing
AI description
t-prokg.com was an impersonation phishing site titled "T-Pro" that copied a trusted brand to steal logins and crypto from wallet users who trusted it.
AI summary
Overview t-prokg.com ran a phishing page under the title "T-Pro", posing as a legitimate service to win the trust of crypto users. PhishDestroy first saw it on 2026-09-04 and classified it as impersonation. The site went offline on 2026-09-11. When we last checked on 2026-10-19, its DNS no longer resolved, so the domain was not reachable. How the scam works An impersonation page copies the name and look of a service the victim already uses, here presented as "T-Pro", so the visitor believes they are on the real site. It then asks for account credentials, recovery details or a wallet connection. Whatever is entered goes straight to the operators. Stolen logins let them take over accounts. A seed phrase or a signed wallet request can let them empty the wallet outright, and blockchain transfers cannot be reversed. Evidence VirusTotal returned 9 detections out of 90 engines on 2026-09-06, two days after our first sighting. The flagging vendors included BitDefender, Kaspersky, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai, CRDF and SOCRadar. That count is modest, but several major vendors reached the same verdict independently and quickly. MetaMask's and SEAL's crypto-focused blocklists also list the domain alongside PhishDestroy, and it appears in 3 AlienVault OTX threat pulses. Infrastructure The domain was registered on 2026-07-20 through Realtime Register B.V., roughly six weeks before PhishDestroy detected it. That gap is consistent with a domain set up in advance and then put into use. Traffic went through Cloudflare, Inc. (IP 188.114.96.3, located in CA), which hides the server actually hosting the content. The site stayed live for only about a week after detection before it went dark. What to do If you typed a password or email into this site, change that password on the genuine service and anywhere else you reused it. Then enable app-based 2FA. If you entered a seed phrase, treat that wallet as compromised and move any remaining funds to a new wallet created with a fresh phrase. If you connected a wallet or signed anything, review and revoke token approvals with a trusted approval-checking tool. Defenders should block t-prokg.com at DNS and proxy level and search logs for any visits to it after 2026-07-20. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a06d2c-12f5-726d-a5c7-54524850196e/ VirusTotal report: https://www.virustotal.com/gui/domain/t-prokg.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=t-prokg.com Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
Every stored field, with its source and date
Questions about t-prokg.com
Is t-prokg.com legit?
PhishDestroy rates t-prokg.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-09-04. Stored VirusTotal result: 9/92 engines flagged. Malicious: 7. Suspicious: 2. Analysis time (as stored): 2026-10-11 22:07 UTC. Retrieved (as stored): 2026-10-23 03:51 UTC. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is t-prokg.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on t-prokg.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used t-prokg.com?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-09-04
Submitted URLhttp://t-prokg.com/
Favicon Hash
Case ID
Observed page title
T-Pro
Automated brand references
MetaMask
TLS Certificate
Issued by Google Trust Services· stored validity ends in 43 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Certificate fingerprint196d61bd6de0b4ea2e2cb2d30e5772cd14d4410bb6289b410c2950cc3ea685ddCertificate names · 2 SANs
t-prokg.com
*.t-prokg.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAIN
RDAP registration
Observed timelinelast reachable: 2026-09-07 22:14 UTCcurrent episode first observed: 2026-09-30 16:14 UTCobserved RIP window: 2026-09-07 22:14 UTC → 2026-09-30 16:14 UTC · 546.00hmidpoint estimate ≈ 2026-09-19 07:14 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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 02:53 UTC.
Recorded events: 16. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Time to First Unavailability
Hours from detection to the first unavailable observation: 149
Recorded activity
6 entries
Lifecycle
Domain registered
Added to PhishDestroy+45 d 22 h
First abuse report sent+18 min
VirusTotal analysis with detections+37 d 5 h
Reported 45 d 23 h after registration
VirusTotal
9/92 engine detections
+37 d 5 h
Realtime Register
Asked for a report through its web form
same minute
Abuse report sent
PD-20260904-A2C846 · Receipt 65453
rtr-security-threats@realtimeregister.com
+16 min
AlienVault OTX
3 community references
+1 min
Added to PhishDestroy
t-prokg.com
same minute
URLScan
Page captured
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
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
Report all
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including t-prokg.com)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
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.