Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
The domain ccreator.io hosts a site that mimics legitimate cryptocurrency services and is aimed at crypto‑wallet owners. PhishDestroy first recorded the domain on 2026-10-19. The site is still reachable and reported as alive on that date. No legitimate brand is confirmed, but the naming suggests an attempt to appear as a creator or wallet tool.
How the scam works
Typical of crypto‑phishing, the page likely prompts visitors to connect a wallet, enter private keys, or approve transactions that transfer funds to an attacker‑controlled address. Victims who comply can lose the entire balance of the connected wallet or have their credentials harvested for further fraud. The risk is financial loss and subsequent account takeover.
Evidence
VirusTotal scanned the site on 2026-10-19 and returned zero detections from 92 scanning engines, indicating that mainstream scanners have not yet flagged the content. PhishDestroy has added ccreator.io to its blocklist, providing the primary detection. No other public blocklists or Google Safe Browsing alerts were reported at the time of review.
Infrastructure
The domain was registered on 2024-05-16 through GoDaddy.com, LLC, giving it a two‑year window before PhishDestroy’s first sighting. Hosting resolves to IP address 172.67.172.159, a range commonly associated with a large content‑delivery network, suggesting the operators are using a reputable hosting provider to obscure their location. The registration and hosting details are otherwise standard and do not themselves indicate abuse.
What to do
Anyone who visited ccreator.io should immediately revoke any wallet approvals granted to unknown applications, change passwords on associated accounts, and enable two‑factor authentication where possible. Monitor wallet activity for unauthorized transfers and consider moving funds to a new address. Security teams should block the domain at the network perimeter, add it to internal threat intel feeds, and monitor DNS logs for any look‑ups. Continuous vigilance for similar impersonation attempts is advised.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
api.ccreator.ioDomain record
app.ccreator.ioDomain record
docs.ccreator.ioDomain record
The original observation time is not recorded for these hostnames.
2 evidence signal groups linked0 stored notification recordsUnverified
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
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.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
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 ccreator.io)
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
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.
(US)
